Hi,

i just upgraded jms to 1.1.19 on my master site, which i use as a template to clone new sites from.

The upgrade went fine, and the master / template master is fine as well (all checks are ok). However when I create a new slave site from the template and log in to the backend on the new slave, I get a patch error on the JMS modules It says not all patches are installed, but when I click install to fix the configuration.php I cannot log in into the backend anymore, the frontend is fine.

Some patches are not installed.
Please check patches and proceed with patch installation to allow mutlisites working properly.

configuration.php Not OK
•The routing wrapper is not present in this MASTER configuration file.
Actions:
◦Add 16 lines containing the routing wrapper to the slave site.

I do think it is strange that I gives me this error on newly created slaves from the template. making a new template did not help either. am afraid there is something not right in the master anymore or something..

thx,
stefan

i tried uninstalling the patches, but that seemed to have made things worse for a while. the master site went back into "installation" mode and I had to rename the installation folder to get it working again.

is there any way this can be fixed without starting all over again? I was nearly finished with my sites and now they are giving this configuration.php client wrapper patch error.

copying the configuration.php from the master site that passes all checks did not help either, still a blank administatrator GUI.

[edit]

check all permissions, but they are fine that cannot be it either.

thanks,
stefan

Dear Stefan,

When you have a problem on the master configuration.php file this probably means that the files have be modified or replaced from the outside.
When the patches are correctly installed, the Global Configuration update the appropriate configuration.php file. If the patch is missing, this mean that the standard Joomla master configuration file layout is used (the wrapper is not present).

When you have tried to un-install the patches, normally the "installation" directory is renamed (not deleted).
As you seem that you had to remove or rename it to restore the access, this is effectively abnormal and probably the symptom of another problem.

When the installation of patches does not work, JMS try restoring the original files that was present when you have installed JMS on your server the first time.
This may also explain why the configuration.php files has no wrapper present.

hi,

thanks for the reply but I am unsure about what to do now.

On 1.1.17 everything was working perfectly, all slaves were ok and creating an new slave as well. Then I upgraded the master to 1.1.19, this worked ok. All checks are fine now on 1.1.19 an patches 1.8. Just when I create a new slave now or go to an excisiting slave I get the configuration.php error, which it cannot patch.

I have no special extensions installed and the two i had (phoca and chronoforms) are working fine. Just when I tried uninstalling on the slave did the installation folder return. Nothing else was changed but upgrading JMS since i was near ready to release the slaves.

Is there any way to restore/reinstall/recreate the configuration.php so that it will work again on the slaves?

could you please give me pointers as how to proceed now? And what does it mean the slave wrapper? the slaves-frontend seem to be working still.

thanks for the quick reply.
stefan

You can have a detailled description on the change between JMS 1.1.17 and 1.1.19 in the FAQ www.jms2win.com/faq/change-history-v11x

I don't see why you have a patch to perform on the slave configuration.php file.
Normally, there is not patch for the slave and only for the master configuration.php file.
In addition, the patch was already required in JMS 1.1.17 and I don't see particular changes on this part between JMS 1.1.17 and 1.1.19.

The slave configuration.php files are stored in the /multisites/xxx directory or in the deployed directory.

Concerning the master "configuration.php" files, there are backup at the installation time in the administrator\components\com_multisites\backup_on_install and backup
In those directory, you will find the backup of all the files before the patches.

ok, it is becoming more clear as to how it works now, thank you for your patient explanations.

I am unsure though as how to proceed from here on. What would be the best way to continue? uninstall/reinstall JMS on the master? replace a configuration.php and roll out the pachtes again? The master thinks itself okay, it is just the slaves that say configuration.php is not patched, can I repatch or put a clean file somewhere to make it work from here on?

the frontends seem to be working still, even as multisites from the same master DB with their prefixes, so I don't know what is broken now exactly or how to fix it,

thanks for a super extension and your help,
stefan