I uninstalled the patches to then upgrade to the latest JMS 1.2.38 patches.

1. If I understand correctly, after uninstalling the patches, but before uploading the new version, JMS temporaritly reverts back to the ORIGINAL config.php file set-up on the original master site. Is that correct?

2. Are those original files found in the RESTORE folder consisting of the files:

configuration.php
configuration.php_pathissue

If not, where are those files?

3. If you have since migrated your master/slaves to a new hosting environment, and are in the temporary reverted state, your sites will try to connect the ORIGINAL config file set-up on the original master site and as such no longer connect the databases. Is that correct?

4. Finally, what is the difference between uninstalling the patches and the extension? What happens when uninstalling the patches? Is that a roll-back? Does it go back to the prior or first version of JMS 1.2? How about when uninstalling the extension? Is that the same? Is it safer to completely uninstall the extension and re-install it?

AND SO...

I have spent all afternoon on this upgrade. After reconfiguring my master config files to connect properly to the correct databases, I now am having chmod permission issues to upload JMS 1.2.38, and have yet to upgrade.

Presently all our JMS sites are off-line. I cant go forward and install the patches because I cant upload the version 1.2.38; I cant go back because all hell breaks loose.

Do I have a back-up? Yes, but if this is a paid extension - it should work flawlessly.

You write "it is advised to uninstall" the JMS patches. I would prefer you instruct us either to do it or NOT. I uninstalled them, and it's been a long day.

Any help would be much appreciated.

This extension is NOT for the faint of heart. Just thinking of upgrading to Joomla 1.6 gives me heartburn.

The errors I have on the Patch update are seen in the enclosed.

... won't let me upload a png.

.... it's a long list.

Well Edwin, eight hours after upgrading to JMS 1.2.38, I was successful in fixing our sites.

And yes, it was a permission / ftp layer / tmp route issue.

Not fun.

When you uninstall the patches, JMS Multsiites restore ALL the files that were backup when the patches were installed.
The list is the one display in the "check patches" and the "configuration.php" file of the master website is part of the list.
So YES this is normal that it restores the file present in the backup directory located in JMS multisites and for which the path is displayed when you install the JMS Multisites.
So YES, this is normal that when you move from one server to another server you restore the "old" server info and potentially path location that could be present in the old "configuration.php" file.

Sometime, you can perform an update of Joomla without having to un-install the patches but this may sometime lock your environment when Joomla update some files that are patches and not all files. This may result in inconsistency. This is the reason why we recommend to uninstall the JMS Multisites patches before to update Joomla.

Personnally, when we have to proceed with an update, we start to clone our production environment and we test locally the behavior of the update of joomla without having to uninstall the JMS patches. If this is OK, we retry in production and sometime it works. Till today, between Joomla 1.5.3 until 1.5.20 we just encounter the "lock" problem twice and we tried to reduce the risk with some JMS Multisites update.

Well, I am looking to upgrade Joomla from 1.5.18 to 1.5.20.

Just made the file/data back-ups.

It gives me a sick feeling to have to go through this again.

I've decide to upgrade without uninstalling the patches to avoid the frustration of two weeks ago.

I will advise.

It worked.... can you feel the relief?