We currently run Uwamp 2.2.1.
Versiojn 3.1.0 is available. What i9s best practice when upgrading. i.e. how do do it? We are new to Uwamp, bit we successfully run an internal website based on mysql.
Thank you
I think the best practice when you do such a change of version (2.2.1->3.1.0) is :
1- Save your website (to a zip for example)
2- Save your MySQL database (in phpMyAdmin of the old UwAmp with the export option...)
3- Install the new version of UwAmp 3.1.0
4- Import your saves (database and website) in the new version of UwAmp.
Tell me if you want more detail...
Related
I am a newbie in this arena. Due to project demand, I had to install the newest version of Confluence. So, I have taken the backup and install confluence 6.12 on top of 6.6. After completing the installation when I hit the URL I have got the following error message.
Roll back the instance by restoring the backup you made prior to attempting the upgrade. Do this by creating a fresh Confluence install (I would recommend using the same version of Confluence that you used to create your XML backup). Restore the XML backup to this.
Get that site working normally first.
Then connect to a supported database.
Proceed with the upgrade.
I want to update a module on my running WildFly10.0.0.CR4 Server with the help of a cli file on Windows.
For example I would need this to update the Infinispan plugin from version 8.0.1.Final to version 8.0.2
According to a book I am referrencing to, this could be something like
jboss-cli.bat --file=myupdate.cli
where the myupdate.cli file contains the code telling the server what to do (In this case, update Infinispan). I just need to know what to enter into that file - Best would be an example with Infinispan and a documentation on how to write such a file for other plugins by myself.
Thank you in advance!
EDIT:
It may also just delete the old version and install a completely new one, if this is easier.
You don't really want to just update random libraries/modules. Some of them, such as Infinispan, are tightly coupled to the server.
For final releases you can use patching to update an existing server. You just need to download the patch for the container you want to update.
I am upgrading magento version 1.5 store to magento version 1.7. Current store has more than 1000 products, more than 100 categories, more than 20 attribute sets, more than 500 customers,more than 500 orders and Database size is more than 600MB.
Above details are mentioned in order to have the idea of store size. Furthermore, I am trying it on local machine with wamp server installed.
Here are the steps involved to upgrade:
Export Current Database (Imported it in gzipped format with option "Disable foreign key checks" checked). As I was unable to export it in normal sql formate due to large size of database.
Created new database and imported the Database exported.
Downloaded fresh 1.7 stable version from magentocommerce.com
Tried to install this fresh magento 1.7 in newly created Database, in which exported database was recently imported.
Next steps were to install theme, copy extensions and copy media folders.
But when I tried to install magento 1.7, it always give me this error :
"This webpage has a redirect loop
The webpage at http://localhost/magento17/index.php/install/ has resulted in too many redirects. "
Here is the link to which I was following:
Link I followed
Note that my main focus is upgrading from 1.5 to 1.7, so much focus must be on that rather then resolving this issue if it is not the right way to do.
And If there is any better and proven way to upgrade to 1.7 from 1.5, kindly share it.
If you want to upgrade you dont need to install and move DB and theme.
Refer this link.
http://www.magentocommerce.com/wiki/1_-_installation_and_configuration/upgrading_magento
Note: If you followed best practices in Magento and didn't modify core code then upgrade should run smoothly.
Expected issues are that your Local and Community folder modules might need some fixes.
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.
Am looking to upgrade Mangeto from version 1.1.8 to version 1.5.
This is a quite a leap I am taking I know, but and I have tried the following already (as some one else had suggested on another site):
dump v1.1.8 database, restore it in a new database.
install magento 1.5 pointing on the restored v1.1.8 database
let the upgrader run
add the old theme files
test that it all works.
When doing that, the upgrader kept saying some tables already existed.
Can anyone help me out?
Thanks
It's fine now, basically make sure you're using the same server environment.