Legal Case Management (LCM) release: version 0.7.1 |
This release improves client search and the "internal requests" feature. It fixes the self-registration functions, MySQL 5.0-related bugs which were caused by lazy SQL, bugs affecting import of databases of older LCM versions, and bugs related to the case "period" filters. Follow-ups are now shown in the "general" tab instead of their own tab (to facilitate printing, less clicking, etc.).
Warning: development release! This release is for site administrators who would like to test and to contribute to the development of the software. It is not suitable for most production environments, since this release has known bugs and core features may quickly change between versions.
See also: Freshmeat announcement
The software can be freely downloaded from our Source Forge project page:
Development version (0.7.1)
Stable version (0.6.4b)
For more information, consult the quickstart notes.
To upgrade from a previous version, overwrite the files then login as administrator. This will trigger the upgrade of the database structure (if necessary).
Background: The Legal Case Management system is a free software initiative of the Internet Rights Bulgaria Foundation (IRBF). The project was initiated on August 1st 2004 in collaboration of several Bulgarian not-for-profit organisations. Today, with the help of user contributions, the software is available in seven languages and continues to be actively developed. We also offer commercial support, trainings. For more information: legalcase-core@lists.sf.net
Import/Export: Fixed invalid path for import of db files, when using the LcmDataDir apache environment variable. (ML)
Import/Export: Allow import of a MySQL 4.x database into MySQL 5.x database (which is more strict). Needs more testing! (ML)
UI: Creating a new keyword in a group automatically suggests a unique ’name’ based on the keyword group name. (ML)
UI: Client search improved to allow searching with full name, just just first or last. (ML)
Core: lcm_panic() now reports more information about the site configuration. (ML)
UI: Fixed window size of login screens popups (lost password, register). (ML)
Registration: Fixed many bugs which made self-registration of new users impossible when using PHP5. (ML)
Upgrade: New keywords were not automatically added after upgrade, was often causing "panic" message. (ML)
UI: Added "Internal requests" tab to "cases", so that it is possible to link requests with a specific case. (ML)
UI: Case follow-ups are now shown in the "general" tab, instead of being shown in their own tab — experimental. (ML)
Core: Many bugs fixed in "internal requests", including filters, list of requests didn’t show requests without comments, etc. (ML)
Core: Debug logs for SQL are now in "sql.log", not "mysql.log" or "pgsql.log" for MySQL and PostgreSQL respectively. (ML)
Core: In the "followups" tab of the "user details", the "total time" did not apply the filters (period start/end) and always shows the total time for all follow-ups. (AG)
UI: Time filters with invalid dates gave mixed results. For example, date-end = February 31 2006 would be accepted, but the list would be empty if using mysql 5.0, but valid in mysql 4.x. Stronger validation was added so that, for example, february 31 2006 returns february 28 2006. (ML)
UI: The "case period" date filters for the list of cases was not working correctly, returning wrong intervals. Bug introduced in 0.7.0, does not affect 0.6.4a and previous (ML)
Upgrade: Fixed "panic" message showed when importing a 0.6.4 database in an already installed 0.7.0 structure. (reported by MH, fixed by ML)
UI: Fixed "Value for case period not permitted" message showed when changing the period filter for the list of cases (ML)