Version 1.2.27 : Add compatibilty with Joomla 1.5.16, PHP 5.3

This Jms Multi Sites version add:

• Bundled with the Joomla 1.5.16 installation and orginal files.
• the PHP 5.3 compatibility and remove all the deprecated functions like ereg and split.
• a fix on a minor problem when computing the "TLD" (Top Level Domain) when shared extension and that may happon on some PHP environment.

Bundled with Patch Definition 1.2.33.

That include the fix concerning the bug introduced by Joomla in the version 1.5.16 and that does not allow to login.
The behavior is that Joomla 1.5.16 loop on the login when called from a "localhost". Some side effect were also noticed in live site.
The fix consists in applying the patches that Joomla has published with (medium/high level) and that will be probably released in Joomla 1.5.17.
With Jms multisites, you can already benefit of this fix that had the sided effect to prevent any login.
See the joomla bug tracker published at
http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=20221

Also add several cross-check on joomla patches installed to improve consistency when joomla restore or replace existing files that remove Jms multisites patches.
A side effect detected is an infinite loop when installing the joomla patches from version 1.5.15 to 1.5.16.
The infinite loop is due to the fact that the installation directory exists (restored by JMS) and when updating 1.5.15 to 1.5.16 some Jms multisites patches are partially removed that create a "ping pong" between the administrator/index.php and the installation/index.php

Add JMS Tools (install) definitions for :

• Job Grok Application,
• Kuneri Mobile Joomla,
• ninjaXplorer
• Quick Jump Extended,
• WEBO Site SpeedUp,
• aiContactSafe,
• Rentalot

Add sharing definition for:

• Job Grok Application

We strongly recommend to install the Jms multisites patches 1.2.33 or better install Jms multisites 1.2.27 before installing the Joomla 1.5.16.

To get the latest version, see the FAQ http://www.jms2win.com/faq#sec-122