Patches definition history V1.1.x

The JEvent 1.4.3 using the Joomla legacy mode has the particularity to save it configuration in a file on the disk.

This patch allows having specific configuration file for each slave site.

This patch is not required for JEvent 1.5.0 rc that is a native Joomla 1.5.x component that also save its configuration into the DB instead of in a file on the disk.

The current patch definition add the possibilty to have specific configuration file for each slave site to the extension AlphaContent and SH404SEF.

Without this patch, the configuration is common to all the websites because it is saved on the disk.

SH404SEF re-installation procedure on a fresh slave site

Concerning SH404SEF, there is still limitations and manual work arround is required to re-install the SH404SEF on a fresh slave site.

To re-installing SH404SEF on a fresh slave site, it is required to remove or rename a system plugin preivously installed by the master website. If you don't remove the plugin, you will have an error during the installation on the slave site.
This is due to the fact that sh404sef does not allow to overwrite the plugin. There is a specific test inside the sh404sef that reject the installation when the following files are present:

•  /plugins/system/shsef.php
•  /plugins/system/shsef.xml

Before trying to re-install the sh404sef, you have to delete or rename manually those files to allow the sh404sef proceed to a complete installation and also install the plugin on the slave site.

Becarefull that each time you re-install the sh404sef on a slave site, this overwrite the existing "administrator/component/com_sh404sef/config/config.sef.php" file that contain the master SH404SEF configuration.

To work correctly, it is required to install the JMS patch and also to go in the master SH404SEF master website configuration to at least edit and save the configuration. By default the sh404sef has no config.sef.php data (empty) and JMS requires that a configuration data is present to install its redirection to the slave site.
Once it is saved on the master website, the sh404sef on the slave site can have its own configuration.

SH404SEF configuration limitation

All the sh404sef configration is not completly specific to each slave site.
There is still common parameters.
The common parameters concern the security parameters

• white list
• black list
• user agent white list
• user agent black list

With the older Community Builder 1.2 RC2 version, one patch was not necessary and the installation of the patches always failled because JMS was not able to find the peace of code to patch.

The result was that it was not possible to install all the JMS patches because JMS has detected its error and roolback the installation of the patches.

This new patche definition detect this specific CB 1.2 RC2 to ignore the patch of one file.

This patch definition also contain some patches required by JACLPlus.
The patch allow to create slave site when JACLPlus is present.
It also allow to login as administrator of the slave site event when the JACLPlus is not yet re-isntalled.
The problem identified with JACLPlus was that it patches a lot of Joomla files to check the permission in DB.
Unfortunatelly, it also do that during the installation of a new slave site that is by definition does not yet contain any user permission definition as the DB is not yet created.
A similar problem was also detected when trying to login as administrator as the JACLPlus table does not exists yet in DB because the JACLPlus extension has not been re-installed.
The patches has consisted to detect those two cases an enhance JACLPlus patches to avoid this side effect.