Just a quick question involving upgrading Magento. I currently have version 1.4.1 and would like to update to the newest version. I tried upgrading through the Magento Connect and can not get that to work. And my host will not give me SSH access so I can't do it that way.
It's very frusterating, what are my other options? Can I just download the new set of files and replace those, but keep the old database? Will that work?
Not sure the best way to approach this. Thank you.
search SO to get similar answers:
disable all 3rd party extensions
disable custom themes
upgrade (you can do version by version also)
turn on your theme
turn on extensions one by one and debug
Related
I'm following the official tutorial to update a theme from 7.0 to 7.2 https://help.liferay.com/hc/es/articles/360029316831-Running-the-Upgrade-Task-for-7-0-Themes, the process is successful but I need to update to liferay 7.4 and I can't find official documentation or information on how to continue from here, I try to deploy the war on my local server with 7.4 but it says which is not compatible with this version of Liferay. Can someone guide me?
There are 5 years between Liferay 7.0 and 7.4 - and a lot has changed in the frontend world. I'd suggest you either just create a new theme, or (better) check if just using a stylebook with a stock theme is sufficient. A stylebook should be a lot easier to migrate to future versions than a full theme.
I believe that it's technically possible to upgrade a theme, but wouldn't bother doing so. As you have an existing theme, it should be relatively quick to get to where you need to be - plus you'll have the opportunity to make those little adjustments that you likely had an eye on for the past couple of years.
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
I have a Magento store running on 1.3.2.4 and the client wants to give the site a facelift. Would it be better to stay with the current version and just modify the current version or should I migrate to a newer version?
Additionally, is it possible to backup the existing store on ver. 1.3.2.4 and just do a fresh install of a newer version and restore?
Upgrading from 1.3.x to 1.6.x will not be as straight forward as you may think.
My suggestion is to setup a copy of your existing site, and attempt the upgrade BEFORE a redesign. Unless your client is okay with staying with the same version of Magento.
You can also create a copy of the database and upload the latest version of Magento, you'll then need to copy over your app/etc/local.xml file from your installation and modify it to use your duplicate database.
More reading:
http://www.nicksays.co.uk/2010/03/fool-proof-magento-upgrades/
http://magentoexpert.com/upgrading-magento-from-1-3-2-4-to-1-5-or-1-6/
http://www.magentocommerce.com/boards/viewthread/263068/#t355374
Would it be better to stay with the current version and just modify the current version or should I migrate to a newer version?
Modify the current version unless your client can pay you to perform the upgrade.
Additionally, is it possible to backup the existing store on ver. 1.3.2.4 and just do a fresh install of a newer version and restore?
Of course.
A bunch of stuff changed in 1.4 with regards to the layout/design system. We had to change several things to get the update right so I'd suggest you upgrade first.
My company is creating a cheaper version of our product that will only upgrade from an older version. To accomplish this, I would like to create an installation that will ONLY upgrade from a previous version. It will not install the full product.
Is there a straightforward way to do this? I have considered:
1) Creating a custom action that checks the registry for the old version first;
2) Creating a patch/hotfix installation
Is there a better method to do this? If not, are there any large pitfalls and drawbacks to these methods? Method #2 seems like the easier method, but this is a pretty big upgrade (though not a "major upgrade," from a technical standpoint). I don't like the appearance of a hotfix when the upgrade is no such thing.
By the way, I am writing the installer in WiX.
This really boils down to one question: does the upgrade move or remove files?
If it does, you need a major upgrade. In this case just make sure that your new version uses the same Upgrade Code as the old one. Windows Installer will take care of the old version removal.
To prevent the package from performing a standalone installation you can use an upgrade rule. You can define a rule which detects older versions and saves them in an installer property. This property can then be used as a launch condition.
If the upgrade doesn't need to remove files, you can use a patch. In this case you don't need to worry about standalone installations.