This is a non-exhaustive (but still near complete) changelog for Joomla Multi Sites version 1.1.x
|
|
Version 1.1.24: Fx the verification of Symbolic Link that may return error with some hosting providers |
|
Tuesday, 28 July 2009 14:32 |
- Joomla Multi Sites verifies the Symbolic Link when some of them are present in a deploy directory.
With some hosting provide, it may happen that this verification fail.
This new version adds an additional check to ensure that a Symbolic Link is wrong or correct.
The new implementation consists in verifying that the symbolic link information is really not available when using a relative path.
It adds the same processing with a full path computed based on current directory.
It seems that PHP 5.2.8 or specific hosting provider may not return the symbolic link information when using a relative path.
The verification consists in repeating the operation with a full path.
- Add several "index.html" files into all the JMS directories to hide the directory structure.
Also add an "index.html" files into the "/multisites" directory to hide the list of slave sites.
- This JMS version 1.1.24 is also bundled with Joomla 1.5.13 original files.
|
|
|
Version 1.1.23: Contain the patch for hot property |
|
Sunday, 07 June 2009 14:19 |
|
This version is just packaged with the "patch definition version 1.1.11" that contain the patch for the "hot property" component. The patch make the "hot property" configuration file specific for each slave site. |
|
Version 1.1.22: Just bundle with Joomla 1.5.11 installation |
|
Wednesday, 03 June 2009 17:23 |
|
When installing the Joomla multisite patches, one of the patches consists in restoring the installation directory. This new Joomla multisite version just include the new Joomla installation directory 1.5.11. No other changes in Joomla multisite functionality are present except its packaging with original joomla 1.5.11 files. The update of Joomla 1.5.10 to 1.5.11 can also be done directly with previous joomla multisite version.
When we have experimented to joomla 1.5.11 with JMS 1.5.21 (previous one), joomla multisite has detect one patch to re-install due to a fix provided by the Joomla team.
The patch is applied to the Joomla 1.5.11 to benefit of the joomla fix. Even with previous Joomla MultiSite versions. |
|
Version 1.1.21: Add the recognition of keyword {site_id} in the "template" domain list |
|
Tuesday, 21 April 2009 09:37 |
|
The recognition of the {site_id} keyword in the "website template" domain name field now allows to create a generic domain that will use the back-end site ID. This extend the same functionality added in JMS version 1.1.20 concerning the processing of the {site_id} in the "manage site" domain names. |
|
Version 1.1.20: Add keyword {site_id} in domain and additional parameters filtering |
|
Monday, 20 April 2009 08:43 |
|
This version include the JMS patches definition 1.1.9 that contains the patches for the SH404SEF and Alpha Content components. Is also contains additional {site_id} keyword processing in the "domain name" list.
When there are keywords present in the "domain name" list, the "manage site" now display and use the appropriate link in the "go to site" tool tips of the site. This make the redirection easier. We have also fixed a problem in the "website template" and the "Folders / Files" panel when the master website contain a apostrophe ( ' ) in the directory or file name.
In the previous version that has corrupted the "template" configuration files that has resulted by an empty list of website templates.
This new version save correctly the apostrophe when present in a folder or file name. When replicating a website, the "from site" configuration.php is replicated to produce the new slave "configuration.php" file in which some fields are modified with the parameters provided in the slave site definition (table prefix, site title, ...)
Normally, the "live_site" field in the "configuration.php" must be empty.
When it is not empty, it provides the URL that must be used by the website.
In this version, we have cleared the field in the replicated "configuration.php" to avoid using a possible value that could be present in the "from site" configuration.php file. This avoid to redirect the new slave site to another URL |
|
|
|
|
|
|
Page 1 of 5 |
FAQ/Change History