To access your license downloads, log in on our website and then go to the Client Area.
If you can't access the client area after log-in and instead you see a message saying you are already logged in you can try using a different browser or use this alternate link to log in.
In the Client Area click the View Your Licenses link on the left menu and then click the View & Download button:
On the next page you will see your license details and available downloads:
You will be able to download the latest version as long as you have a valid upgrades package. You get 12 months of free upgrades. After expiration you need to renew the upgrades if you want to download the most recent version.
There is no download link for JReviews Add-ons, they can be installed directly from JReviews administration!
JReviews is compatible with:
Required PHP version is 5.2.x or higher.
Required PHP Extensions: json, mbstring, curl, bcmatch (most servers have them installed by default).
PHP Configuration:
IonCube loader needs to be installed and enabled on your server. On some hosting packages it is enabled by default.
If ionCube is not enabled on your server, you can ask your host to install it for you, or you can do that yourself:
Download loaders package from ionCube website.
Upload ioncube_loader_lin_5.3.so file (if your server uses PHP 5.3) or ioncube_loader_lin_5.4.so file (if your server uses PHP 5.4) anywhere in your joomla folder.
Create the /administrator/php.ini file and add this line (use the correct path to the ioncube file where you uploaded it):
zend_extension=/path/to/ioncube/folder/ioncube_loader_lin_5.3.so
Note: If you are having troubles installing ioncube, download loader-wizard.zip file, extract the zip and place the loader-wizard.php file into the root of your site. Run that file and it will guide you through the installation process.
Watch a "How to check JReviews pre-install requirements" video tutorial on YouTube
First extract the JReviews package that you downloaded from the Client Area (package_jreviews_2.4.x_unzip_first.zip).
This is the folder structure of the package:
JReviews modules and plugins will be installed automatically.
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.
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 inside /components/com_jreviews/ 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.
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.
Since this is a major version upgrade it won't be possible to upgrade remotely from earlier JReviews versions. Once you install JReviews 2.4 you'll be able to continue using the remote updater.
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