Difference between revisions of "How to upgrade JReviews"
| Line 29: | Line 29: | ||
# Clear the browser cache! Otherwise you may end up with non-working links. | # Clear the browser cache! Otherwise you may end up with non-working links. | ||
| − | == Upgrading to JReviews 2. | + | == Upgrading to JReviews 2.7 from earlier versions == |
| − | + | Read [[Upgrading to JReviews 2.7]] | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | Read [[Upgrading to JReviews 2. | + | |
== Troubleshooting a broken upgrade == | == Troubleshooting a broken upgrade == | ||
Revision as of 21:00, 15 July 2016
Contents
What happens to my existing listings, reviews and customizations when I upgrade
Upgrading JReviews does not remove your configuration settings, or any of your existing data such as listings and reviews. These are stored in the database and the upgrades affect mostly the file system. If an upgrade requires database changes, then this is automatically taken care of by JReviews. If you've made any theme or code changes, you should make a backup of your modified files before proceeding with the upgrade.
Remote Upgrade
You can do a one-click remote upgrade by using the Install & Update menu in the JReviews administration under the Maintenance header on the left column. Always upgrade the s2framework first and JReviews second.
Remember to backup any files you've customized because they will be replaced during the upgrade. You can use the JReviews Code Overrides to move the files outside the core folders to prevent them from being overwritten.
We recommend that you use a development server to test the upgrade first and that you rename the jreviews_overrides folder to something else and clear the file registry before you upgrade.
The upgrade doesn't work, what now?
Enable FTP Layer in Joomla Global Configuration and try again. If that doesn't help, use your ftp client to temporarily modify the permissions of the Joomla /tmp folder to 777 and do the same with the components' administrator and frontend folders. For example /administrator/components/com_jreviews and /components/com_jreviews.
You can also use the regular upgrade method described below.
Manual upgrade
- If you are upgrading your production server it's always a good idea to perform a full backup of your site, including database and files, in case you need to revert the upgrade. A useful Joomla extension for this is Akeeba Backup.
- Backup your JReviews theme and other files if you made changes to them. It is not necessary to do this if you are using JReviews Code Overrides feature to put modified files outside the /components/com_jreviews folder.
- Go to the Joomla Extensions Manager and uninstall both S2Framework and JReviews components.
- Install new versions of S2 Framework and JReviews Component.
- Re-upload your modified JReviews theme files (only if you are upgrading from a minor release, otherwise your old theme files might not be up to date).
- Clear the browser cache! Otherwise you may end up with non-working links.
Upgrading to JReviews 2.7 from earlier versions
Read Upgrading to JReviews 2.7
Troubleshooting a broken upgrade
The most important thing to do when an upgrade presents broken functionality is to test the same function without any theme or code changes. If you use the code overrides functionality, you should rename the jreviews_overrides folder and clear the file registry. If the issue is solved, it means you need to update your modified files to bring them up to date with their most recent versions.
If you have made any theme or code changes read What happens with modified files when JReviews is upgraded