LOGman 1.0 RC5 released
We are happy to announce the 5th release candidate (RC) for LOGman 1.0. This release completes the 1.0 feature set brings and Joomla 3 support. Together with DOCman 2 and FILEman, LOGman is now fully compatible with Joomla! 3.
And that’s not all. We have also prepared a couple of surprises we are sure some of you will be most happy about.
1. Joomla 3 compatibility
Joomla 3 is fully supported. The user interface has been improved to make full use of Twitter Bootstrap and blend in nicely with Isis, the default Joomla 3 administrator template. LOGman now looks great on all Joomla! versions (1,5, 2.5 and 3.x).
2. Export to CSV
Users with administrator LOGman access can now export activity records to CSV format. We have build it in such a way that you can export very large datasets without having to worry about server timeouts or memory problems of any kind. We tested it with more than 1 million activities and it just works!.
The export feature also plays well with the set of filters that were selected prior export, meaning that you can get exactly what you are looking for. Basically, what you see is what you get, nothing more, nothing less. Exporting data could not be easier.
Note : The exported data format follows a simplified representation of the activity stream standard
3. Module filtering
On previous versions, the activity stream module listed activities from all users. This is not always ideal. Site administrators can now change this behavior in the module settings.
By setting the “Logged in user only” parameter to On (Off by default) in the module settings, only activities from the currently logged user will be listed by the module.
At the same time it is now possible to visualize the activity stream provided by the module even if the current logged user does not have admin access to the component.
Combine this with the “logged in user only” setting, and you can now create activity modules that show the activity stream of the current logged user regardless of the their LOGman’s access permissions. Very handy as a personal audit trail.
We are slowly getting ready for the stable release of LOGman 1.0. Final steps we need to complete are, the provisioning of language packs for LOGman.
As mentioned in the RC4 release announcement, we are also working on an API for easy integration of LOGman with other extensions. Most of this feature’s work has already been done, we are now doing final code reviews and working on initial documentation.