video1 wrote:
Is this the very end of this thread or is there any hope JReviews and JMS will get together for a happy end :-?

This are such bad news... my site y jreviews based and I was really counting on this... I hope someday...

Try to update the following JReview source with the following code
Source : components/com_jreviews/jreviews/controllers/components/config.php

Search for statement
$cache_file = 'jreviews_config_'.md5(cmsFramework::getConfig('secret'));

and try replace it with

// If slave site, use the Site ID
if ( defined( 'MULTISITES_ID')) { $cache_file = 'jreviews_config_'.md5( MULTISITES_ID); }
// If master, keep the original code
else { $cache_file = 'jreviews_config_'.md5(cmsFramework::getConfig('secret')); }

We can not guarantee that it will work in all cases and we don't know where is located the configuration on the disk and how to check if the "master" configuration exists to use the master one when the slave does not exists.

Only JReviews teams can implement the correct code as they have all the sources.
The peace of code that we provide you is just an experimental one that may help you.

Hello there,
Just wanting to know if someone has implemented with success the code proposed by edwin?
Thanks for any feedback!