I've tried every method I can think of to update from 3.1.5 to 3.2.3 and each time it pretty much kills my site and leaves me with the error:
Fatal error: Call to undefined method JLoader::registerAlias() in /homepages/.../libraries/cms.php on line 61
At which point I just clobber the rest of the site and reinstall my backup (oh man you GOTTA LOVE Akeeba).
I've upgraded Joomla successfully and unsuccessfully about 100 times over the past few years on various sites and this is the first time I'm stumped as how to move forward.
One interesting piece of data is in the Admin Control Panel of the 3.1.5 is that the Joomla version says "Unknown" even though the System Information lists it as 3.1.5.
So, anyway, what is the ABSOLUTE, BLESSED method for moving from 3.1.5 to 3.2.3? If I should simply be able to install the 3.2.3 upgrade zip file then I guess I'm toast. In that case, what would happen if I left the database as is and cleared out all the files and then installed the 3.2.3 full stable package? Would that work?
Do you have Akeeba backup installed? You need to make sure it is updated first before updating joomla.
So if yo have a back up, restore that, update Akeeba, then update Joomla again.
http://www.rockettheme.com/forum/general-discussion/215394-pressing-the-joomla-update-button-killed-my-site
The solution was pretty easy, though unexpected. See here.
Related
I'm trying to get Magento 2.4 running using the production ready zip and I keep getting it to this point where I believe it's ready to start the setup process, but it's waiting for me to agree to the ToS. Unfortunately there's no agree button or instructions on if there's a file I need to edit. I just did a fresh install of XAMPP with PHP 7.4 and still have the same issue, and can't find a similar mention on google.
Is there supposed to be an agree button, do I need to edit a file?
Term & Agreement link leads here, still no agree button. Getting started link takes me to installation instructions for a Linux CLI
I saw I may still need to run the composer install command even on Windows, but I was under the impression the production ready zip already had the dependencies included. Where am I going wrong??
Update: I got composer running in windows terminal and it returns that there is nothing to install.
According to the official site docs, in a note at the top of the installation instructions for a CLI install of Magento 2.3:
"The Web Setup Wizard is being deprecated in Magento 2.3.6 and will be removed in Magento 2.4.0. After it is removed, you must use the command line to install or upgrade Magento."
So you cannot install Magento 2.4 without touching the command line.
I just upgrade my Joomla website from 3.1.1 to 3.3.6.
As found on https://github.com/joomla/joomla-cms/releases/tag/3.3.6 I downloaded Joomla_3.3.6-Stable-Update_Package.zip pack and uploaded all the files over my previous Joomla installation.
Unfortunately, I cannot login and the following error is displayed:
Fatal error: Call to a member function checkSession() on a non-object in /home/www/.../web/plugins/user/joomla/joomla.php on line 209
Line 209: $this->app->checkSession();
I did additional tests and it seems that all the "$this-app->..." command fail!
I opened the 3.1.1 joomla.php file and found another syntax:
$app = JFactory::getApplication();
$app->checkSession();
Replacing the 3.3.6 syntax with this one solved my problem, but I can see that similar "calls" are done when logout, so I would need to change them as well.
It looks like the new syntax ($this->app->) is not working in joomla.php after upgrade to 3.3.6 and now I'm afraid similar errors can occurs in other scripts.
Does someone already get similar errors, is that a known problem with Joomla upgrade, how to solve this issue correctely?
Thank you in advance for your help.
Joel
Why on earth would you do this? For a long time now Joomla has had a built-in updater that does several things beyond just copying the files to the correct location, like updating the table definitions, adding new tables, data migration and removing old files.
My guess is that your database schema is now out of sync with the PHP. You'll have to role back to your backup as there is no clear way to say if records have been damaged etc.
Once you've restored your backup, use one of the methods described in the Upgrading from an Existing Version FAQ on Joomla's Doc's site.
As this question is about Joomla management and implementation details, you may get a better answer if you, try asking on the Joomla Q&A StackExhange site in the future.
Migration or upgrade, whatever, I want to get rid of my 1.5 site. I read some articles, watched a few tutorials however I could not beat it.
First, I upgraded my 1.5.2 to latest 1.5.26. Then I installed jUpgrade 2.5.2 extension from admin panel, activated it but after clicking to upgrade: nothing happened. The big arrow is not clickable.
Then I downloaded redMigration. There were two distinct .zip files in it. "plg_redMIGRATOR_1.0.0_j15" and "com_redMIGRATOR_1.0.0_j25_j3". Former was installed as an extension and activated (also I did password operations) but there is nothing. No way to run it. When I tried to install "com_redMIGRATOR_1.0.0_j25_j3" from extensions, it says there is no XML file to install. So I am stucked! I've been trying it hard but I have nothing.
How can I fix these problems?
The not click-able issue is most likely down to the javascript not working.
When I've seen this before, it has been just that JUpgrade needs a newer version of Mootools.
Have you enabled the Mootools Upgrade Plugin?
See: http://docs.joomla.org/J2.5:Migrating_from_Joomla_1.5_to_Joomla_2.5#Enable_Mootools_Upgrade_Plugin
How i convert my current website of joomla1.5 to joomla2.5
please anyone help me
When i using jUploader it is only allow to convert joomla1.5.18 to 1.7 but i need joomla2.5
Thre is a lot of documentation out there on how to convert Joomla 1.5 sites to Joomla 2.5.
You need to use an extension such as JUpgrade to upgrade your site to 2.5.
Please bare in mine that this will update your database tables and core extensions such as com_content, mod_login etc. This will not upgrade 3rd party extensions that you have found from the Joomla Extensions Directory. You will need to go back to whereever you downloaded these extensions from and see if there is a Joomla 2.5 compatible version of them, and install them, else you'll need to look for an alternative.
Seeing as you have waited all the way till now, you might be best off upgrading again to Joomla 3.x. Even though this it eh short term release, it is the way forward, will save what could be another time consuming upgrade in the future.
Oh and as always recommended, please make sure you take a backup of your site before the upgrade.
Hope this helps
Error in file:
/usr/local/sites/client/magento_site/app/code/core/Mage/Customer/sql/customer_setup/mysql4-upgrade-1.4.0.0.7-1.4.0.0.8.php" - SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'customer_form_attribute' already exists
I tried upgrading this using this tutorial from turnkeye to go from 1.4.1 -> 1.4.2 and then to 1.6 but after all the mage upgrading was complete, when I hit the website to upgrade the database I get errors about database tables that already exist and it appears to be running a database upgrade script for a version of magento before 1.4.2. I know this error is extremely common and I have seen many blogs posts about it and read all that I have found -- I see no resolution besides starting a fresh install.
I've heard people say this can happen if a previous upgrade didn't complete successfully but I don't think that is the case here -- I think it was a fresh install at 1.4.1 (at least I don't believe I ever upgraded it). Anyone know why this is happening or how to fix it?
Note 1: I also tried the upgrade by overwriting the 1.4.1 files via SSH with successive version of magento -- always the same database errors though. If I remove the mysql-upgrade script that is failing, then another one fails in its place with a simliar 'table already exists' error.
Note 2: I also made sure I cleared /var/cache and /var/session and even tried reindexing. No success.
Looks like it is just complaining about a table already existing. Either install a fresh version of you database from before you tried to upgrade then clear cache and sessions and try again
Or
Just open the file referenced and temporarly comment out the part that is installing the table again. That should allow you to by pass the error.
Then you can download the magento Database Repair Tool to ensure that your tables are correct.