How to upgrade Imagevue
Upgrading your Imagevue installation with updates is normally quite easy. However, sometimes we need to re-arrange the internal structure of Imagevue to open up for improvements and new features. When you upgrade your Imagevue installation, you want to keep all your images and content of course, as well as any specific settings you have. Below is a guide for a few upgrade scenarios:
Upgrading to Imagevue X2.5+ from earlier versions
Important! Imagevue X2.5+ requires PHP 5.1.3 – Read more
With Imagevue X2.5, we made a few changes to the folders in Imagevue. Mainly, the changes were made to support renaming of the main imagevue/ folder which was used to access the admin. Now, this folder has been split into two folders: iv-admin/ and iv-includes/. iv-admin/ is used to access the admin (and can be renamed), while iv-includes/ stores all the Imagevue scripts and modules (and can NOT be renamed).
- Log in to your FTP, and download/backup the folder imagevue/config/
- Download/backup any custom theme(s) you have created in imagevue/themes/*
- Delete the entire imagevue/ folder
- Upload all files and folders from Imagevue X2.5+, except the content/ folder
- Upload the content of your “config” folder into iv-config/
- Upload the your custom theme(s) in iv-includes/themes/ (it is recommend to not overwrite Imagevue-native themes. Instead you should create copies of your themes with different names)
Clear your browser cache, and check your gallery! Remember that you now have to access your admin from your {gallerypath}/iv-admin/ – However, now you can simply rename this folder to anything you like!
Clean upgrade ›
If you do not need to keep any specific settings, or if you wish to redo them, the upgrade is easier. Simply delete the imagevue/ folder, and then upload all files and folders from Imagevue X2.5 except the content/ folder. Clear your browser-cache, and check your gallery!
General Upgrading
If you are upgrading from an existing Imagevue X2.5 installation (for example from beta release to final release), the steps are pretty basic:
- Simply upload all files and folders from your downloaded Imagevue archive, except the content/ folder. By doing this, you will be overwriting your gallery with new files, yet retaining your content/ folder with your images, files and settings.
How are my settings and custom themes stored?
When upgrading, you do not need to worry about your custom settings and themes. All changes you make, are uniquely stored in separate files in the iv-config/ folder, and will not get overwritten when you upgrade.
Important!
If you are editing any files directly without using the Imagevue admin, there is chance that these changes will be overwritten when you upgrade. Therefore, we don’t normally recommend editing files from outside the admin.
When i follow the instructions about a General Upgrade from 2.5x (Simply upload all files and folders from your downloaded Imagevue archive, except the content/ folder.) then i have overwriten the iv-includes folder, is it not?
So you’re next remark: “When upgrading, you do not need to worry about your custom settings and themes. All changes you make, are uniquely stored in separate files in the iv-includes/config/ folder, and will not get overwritten when you upgrade.” isn’t right?
This way i just did lose my settings… :-(
Well, I don’t know how you are upgrading but you are somehow DELETING folder content when upgrading. When uploading a folder, either on FTP or locally, it overwrites all files YES, and this is correct. However, it does NOT overwrite files that don’t exist in the Imagevue installation. For example, your config is stored like this:
http://imagevuex.com/demo/x2/iv-includes/config/configUser.xml
If you check in the Imagevue files, this file does NOT exist so it can’t be overwritten. This is what we mean by config- and theme files being stored in UNIQUE files that don’t get overwritten in normal procedures. What FTP application are you using? It is deleting your folders instead of merging them which is normal when uploading or copying a folder.
I used a really clunky cpanel interface to upgrade – which meant I uploaded every folder and file individually. I believe I did not miss anything. And I definitely made a copy of my config and themes folder, although I made the mistake of putting the content into one folder called “copy” so do not know what files are supposed to end up in “config” and what in “themes.” But dialogs popped up for files saying there was a problem, so I moved them until the dialogs stopped. But then in the end my site won’t work. All I get is this
Fatal error: Call to a member function getConfig() on a non-object in /home/pauline/public_html/iv-includes/controllers/IndexController.php on line 35.
What can I do?
I believe this was answered by e-mail?
I have a question….maybe the folder name are now different but what is the folder in “Delete the entire imagevue/ folder”?
Is this folder my Portfolio folder? So I have to delate all except the content folder?
- imagevue/config/ = iv-config
- imagevue/themes/ = iv-includes/themes
Sorry but it’s my first upgrade
Thanks in advance
Yes, some locations change for the greater benefit, as you have correctly noticed. It is NOT your portfolio folder though – It is basically the Imagevue script files, that need to be upgraded!
Basically the “imagevue” folder is replaced, and strictly speaking, you do not need to delete it, but it will not be used any more after upgrade of course …
I just want to request an important an crucial feature for upcoming(future) imagevuex releases.
Currently I’m running imagevuex 2.7.5.1, you should seriously consider an automatic upgrade thru the web interface to latest imagevuex release, without having to risk your current projects. As a system engineer I’m obviously perfectly capable to do it, but what about the regular iliterate customers. what about the slightest possibility to screwed your current project just because a flaw(or mistake) on the updating process. We need automated tools for the back-end process.
Agree, it would be cool … Just a lot of “unknown” factors as to what needs to be upgraded, and depending on any customizations and what version they are running … We definitely have it noted.
YES, i agree with you. each time i upgrade, i have to do a lot of work.
Hi
after upgrade from 2.5b to 2.7.6 I got the following error
Migrating /iv-includes/config to /iv-config:
Cannot copy iv-includes/config/configUser.xml to iv-config/config.xml. Are permissions ok?
The Permission are set to 777
Fortunately I have a backup
something is going wrong but what?
I need help
Gennaro
This shouldn’t be a problem, just move all the files manually from /iv-includes/config to /iv-config. Then delete the old folder. Keep in mind you will have to rename configUser.xml to config.xml. Are you sure you have 777 permissions on iv-config folder?
Sorry for the inconvenience, you will have to do it only once.
Hi Nick
I tried again and again an at last I called my provider. It was even though a permission problem.
I did the upgrade and all runs fine.
Thx
If you want http://www.frontera.ch
I think the steps are simple. I don’t know PHP and HTML and CSS and still it’s working for me.
So:
1. FTP Client [Filezila for example] > log in the account
2. Copy the entire website into your computer [I unually make myself a back up folder that contains different stages of my website]
3. Copy All the files from the “kit” folder of Imagevue into the server
4. Copy the “content” Folder [overwrite] on the server
5. Copy “iv-config” Folder [overwrite] on the server
6. Copy theme from iv-includes/themes/ YOUR THEME
And that should be all