I was trying to upgrade moodle 3.5 to moodle3.10. After upgrading the website has lost the theme completely. Even the basic design is not visible and displaying like plain text
I updated version details in version.php as below
$version = 2020110901.00;
$release = '3.10.1 (Build: 20210118)';
$branch = '310';
$maturity = MATURITY_STABLE;
and I completed the upgrade from the admin panel and it displayed as successful. But the website has lost its design of both front end and the admin panel.
Kindly help me to resolve this.
Related
I'm new to wix/wixsharp and bootstrapper. I created an installer and providing ProductID, UpgradeCode and version. Installer is working fine but when I'm creating new installer and giving different version it is simply allowing user to install the another version of application and bot can be seen in program files.
If I use the same file that was used earlier to install, it gives option to uninstall as expected but when I use the upgraded file it does not give upgrade or repair option.
Can anybody help me with this. Here is the code I'm using
project.UpgradeCode = new Guid("9fa9fcf6-e807-404d-a67a-d66f1a60ca53");
project.ProductId = new Guid("0b2d7210-32ce-4095-9c46-aaccb1bf0733");
project.Version= new Version("1.0.209.10040");
project.MajorUpgrade = new MajorUpgrade
{
Schedule = UpgradeSchedule.afterInstallInitialize,
DowngradeErrorMessage = "A later version of [ProductName] is already installed. Setup will now exit."
};
In 2nd build I'm just changing Version("1.1.209.10040") keeping everything else same.
Please let me know if any other part of code is required as I'm really new I'm not sure I shared all the necessary information.
If you're trying to do a major upgrade you will need to change the ProductCode. Whenever you're building an upgrade you should refer to the Windows installer Upgrade page that MS publishes. I don't know if there is a specific one for WiX but the same concepts still apply.
This worked for me. I changed ProductId and then I am able to auto-upgrade my Product based on version# (first three parts).
project.ProductId = Guid.NewGuid();
Recently I've moved one of my development sites into production.
The following steps were taken.
Complete backup of both versions (4.5 & 8.7)
Removal of old version
Uploading new TYPO3 developed version
Updating database connection in the LocalConfiguration file
After doing all this and enabling the install tool I am able to login to my install tool but not into the backed. Both the install tool and the backend are giving the following error.
Uncaught SyntaxError: Invalid or unexpected token on Jquery. Various other errors also appear because of this. Included below is a screenshot for completion.
No file transfers failed and I am unable to login to the backend. I haven't done anyhthing to the database apart from setting it up
It's possible that file-compression was activated for JS- and CSS files which doesn't match the settings on the new server.
If you click in the browser-console on a file-link you get some output like this:
You can adjust the compression-level in install-tool but can see the value in the file typo3conf/localconf.php (for TYPO3 4.x) or typo3conf/LocalConfiguration.php (for TYPO3 8).
It might currently look like this:
$TYPO3_CONF_VARS['BE']['compressionLevel'] = '9';
and you can adjust it just to 0:
$TYPO3_CONF_VARS['BE']['compressionLevel'] = '0';
In the install-tool of TYPO3 4.5 the option looks like this:
The problems comes from the setup.ts or config file. Comment / uncomment these lines until it will work. Is usually the compression of js that is the problem:
#config.concatenateCss = 1
#config.compressCss = 1
#config.concatenateJs = 1
#config.compressJs =1
I am install magento latest version and it install successfully but my problem is when i am try to open the dashboard then no one error but not show login panel like images https://imgur.com/7bTHEVd it show blank like image
Are you on Magento 2.3.0, this happened to me the other day ?
It looks like it's a bug with:
#/vendor/magento/framework/View/Element/Template/File/Validator.php:138
Change line 138 from: $realPath = $this->fileDriver->getRealPath($path);
to:
$realPath = str_replace('\\', '/', $this->fileDriver->getRealPath($path));
Please Note
- This is just a temporary fix to make it work on your local Windows machine, don't commit or push any of this code to production as it is editing the core files (not recommended)
I developed my TYPO3-Project using a local Vagrant-Machine. Now I bought some Webspace and wanted to migrate it there but I keep getting Errors.
Whenever I try to call the URL, TYPO3 is giving me the "Ops, an error occurred!".
I can, however go to the back-end and install tool and everything looks fine there! All the pages with all their content are editable.
Now for the weird part:
Whenever I try to open a Sub-Page from the Backend, It wants to load it with the base-url of my Dev-Server. I migrated the Database correctly and Installed the TYPO3-Installation accordingly.
So basically this is whats going on:
My development enviroment has its own Database and is working perfectly fine
I exported the Database via terminal and imported it via PHPMyAdmin to the new Hoster
I set up my TYPO3 Project and Changed the Localconfiguration.php
I added the new URL to the TYPO3 Project
--> Everytime I open a link I either geht the Blank Page with the "Oops, an error occurred! Code: 20171002194119799d9c1b" or it tries to open the wrong URL.
I used:
Homestead as my Vagrant Box
Composer to install TYPO3 and the extensions
Realurl (latest Version)
TYPO3 8.7.7
My RealUrl setup in my page.config looks like this:
absRefPrefix = /
tx_realurl_enable = 0
linkVars = L(0-3)
index_enable = 1
index_externals = 1
Thanks in advance! I know this is quite something to read but I've struggled for the last 5 hours with this problem and I don't know where to ask but here.
Did you changed the domainrecord?
Open the rootpage in list mode and modify (or add) the domain record to match the current domain.
I have created a custom plugin(version 1.0) which is already installed in the site.
Now, If i have developed its next version i.e. 1.1.
So, How can I display notification like 'There is a new version of custom-plugin available. View version 1.1 details or update now.', at plugin page in wordpress admin panel.
Would anyone please help me on this?
Thanks in advance !
First of all you have to upload your plugin to the https://wordpress.org/plugins/ using (SVN), You can read about
Subversion.
When you're ready to release a new version of the Plugin:
Make sure everything is committed and the new version actually works.
Pay attention to all WordPress versions your Plugin supports and try to test it with all of them. Don't just test the new features; also make sure you didn't accidentally break some older functionality of the Plugin.
Change the version number in the header comment of the main PHP file to the new version number (in the trunk folder).
Change the version number in the 'Stable tag' field of the readme.txt file (in the trunk folder).
Add a new sub-section in the 'changelog' section of the readme.txt file, briefly describing what changed compared to the last release. This will be listed on the 'Changelog' tab of the Plugin page.
Commit these changes.
Create a new SVN tag as a copy of trunk, following This Guide
Give the system a couple of minutes to work, and then check the wordpress.org Plugin page and a WordPress installation with your Plugin to see if everything updated correctly and the WordPress installation shows an update for your Plugin (the update checks might be cached, so this could take some time -- try visiting the 'available updates' page in your WordPress installation).
The other answer is only correct if you are a major shop. You do not have to use the wordpress repos for your plugins, in fact, if you're not a major shop, DON'T as it pollutes the ecosystem with unmaintained plugins as solos move on.
I use this to ensure that my plugin dependencies are met or show a warning using the update notice.
if ( !defined('MY_MAIN_PLUGIN_IS_ACTIVE') ) {
$file = basename( __FILE__ );
$folder = basename( dirname( __FILE__ ) );
$hook = "in_plugin_update_message-$folder/$file";
add_action( $hook,
function ( $plugin_data, $r ){
echo 'Must activate Main Plugin to use this plugin';
},
10,
2
);
return;
};