How to upgrade from 1.1 to 2.0

Archived Stas K. ● ago

If you want to use AutoUpdater option inside system, please use following instructions, as we had problems with our server scripts, so there are some things missing in order for you to perform smooth upgrade:

Take Upgrade.php from the attached archive and put it to application/modules/system/services/;
Take admin.js from the attached archive and put it to public/assets/modules/system/js;
Take application.js from the attached archive and put it public/assets/js;
Take upgrade_200.php from attached archive and put it upgrade/instructions;
Create /cache and application/sessions folders and make them writable (777 permissions or 755 of some environments for apache user to put files there);
Enter FTP credentials at Administration->Modules (make sure folder visibility is set correctly from the path where your ftp user logs in to the path where ur is installed), save and click on update;

Note: all backups of the system will be stored in work/upgrade or work/backups

For the Manual Update instructions or further automatic update please go to Administration Manual.

Files:

Replies (6)

Lev T. ●

Ok. Got a question about the manual update Useresponse.

1. As you can safely manually update from version 2.0 to 2.1?

What should be done for this. The site says quite sparingly by this manipulation.

2. To automatically update the need to specify the settings on the FTP server? Or rather put a zip file somewhere.

I would be grateful to any of the responses. Thank you!

Stas K. ●

Current topic is for upgrade from 1.1 to 2.0. But for as per your request:

Use Update instructions for manual update. No DB upgrade is required;
Once completed, make sure you have temp folder inside public/files. If not, please create it.
Follow instructions to add extra fix in DB that is incorporated in 2.3 release that should be live today later and won't require this fix
Clean cache folder

Lev T. ●

Stas, This manual migration 1.0 2.0 is not relevant for 2.0 -> 2.1?

Stas K. ●

Lev Tkach wrote:

Stas, This manual migration 1.0 2.0 is not relevant for 2.0 -> 2.1?

It's the same, just see above some details specific to mentioned item 2 and 3 in the list above.

Oleg S. ●

Stas,

After update v 2.0.1-> 2.3 If I click on anything the items Ideas, Problems, etc print message

how fix it?

Message: The given destination is not a directory or does not exist.

Stas K. ●

Oleg,

Please make sure you have all folders from the list writable:

/application/sessions
/cache
/pulic/static
/public/ with all folders inside

Also verify that you have public/files/temp folder