Hi Edwin,

I found that if I modify the codes of extensions/modules directly on the master site and then install those extensions on a slave site, the modified codes would be replaced by the re-installed codes.

To avoid those problems, I can modify the codes on the unintalled modules, unintall the modules and re-installed again with modified modules. But this is quite troublesome.

Would you suggest any good and easy approach to modify/update the extensions/modules?

Many thanks.

Seth

This is correct that when you re-install an extension in a slave site, this overwrite the existing files and folder present on the disk.
This is the reason why JMS check in a slave site that the extension name and version is identical.
The objective is to replace the existing file with exactly the same one.

Therefore, if you modify manually an extension already present, you have to rebuild it distribution files (tar.gz or zip) in aim that when you re-install it, you replace it with the identical content.

To avoid this overwriting processing, you can use the replication (website template) that is available when you create a new website.
As it replicates the DB content, this does not require to re-install the files.
Unfortunattelly, this does not work when a website has already been created because JMS is able create the new tables but will not able to update and add the required records in the existing tables and required to have the extension correctly recognized. This latest point could lead to unpredictable results