December 18th, 2013
This is a free Joomla component/plugin that implements a satellite (client) implementation of the Basic Meeting List Toolbox (BMLT).
Restarting the Changelist, because the server cuts off the text. For a complete version, check the Repository.
3.0.19 Adds French localization.
3.0.17 Configurable first day of week.
3.0.16 Added German localization.
3.0.15 Fixes a edit text box detection issue.
BMLT Satellite Base Class updated to 3.0.15 also.
3.0.14 AJAX URI invalid characters bug fix.
3.0.11 Google Maps API performance tweak.
3.0.10 Fixes a display bug related to Google Map API.
3.0.1 Updated to include the new base class that fixed a couple of WordPress issues. Also forgot to turn debug mode off in the base class (oops).
3.0 This is a major rewrite that implements the default ‘[[bmlt]]’ shortcode as an interactive, client-based Web app.
PLEASE NOTE THAT VERSION 3.0 REQUIRES ROOT SERVER 1.10.3 OR ABOVE (FOR THE [[BMLT]] SHORTCODE).
To read more about this, visit this blog post:
Please note that BMLT Extension Version 3.0 is not compatible with Joomla version 3.0.
2.2.3 Made it 2.5 and 1.5 native.
2.2.2 Fixed a nasty bug in the admin interface that could create multiple empty settings.
2.2.1 This adds an alert to the new map search that is displayed when no meetings were found. The original version of the plugin gave no feedback, so the user did not know there were no meetings in their desired search area.
2.2 This fixes some validation issues, and allows the use of the [[bmlt_mobile]] shortcode, as the comment version was being “scrubbed.” It also is the first release from the source’s new home on GitHub: https://github.com/MAGSHARE/bmlt-joomla
2.1.27 Fixes a couple of rather severe issues that appeared, as if by magic, sometime during the 1.6.x Joomla roadmap. Apparently, they changed the way the manifest files were being interpreted, and, quite suddenly, the component didn’t install a whole lot of critical files. Of course, this brings down the whole server. Also, since my test server was an earlier version of 1.6, I never saw these.
In any case, they are now fixed.