LCM ChangeLog for 0.2.0 to 0.6.4a

New features between releases. Archives for releases 0.6.4a to 0.2.0. The ChangeLog for newer releases are available here.

Stable branch: Changes between 0.6.4 and 0.6.4a (Released 2006/02/17)

- Core: debug_tr=2 now returns translation string key. (ML)
- Core: moved "my_options.php" to "inc/config/" directory (instead of only "inc"). Backwards compatibility kept for now. (ML)
- Core: fixed mktime() PHP 5.1 warnings, uses locale timezone, but may fallback on UCT. If you have incorrect time, check your date.timezone setting. (ML)
- Core: fixed translation of "activity type" keyword, e.g. was showing keyword code (ex: app05) instead of its translation (ML)
- Core: fixed MySQL 5.x panic in "activity details" (Reported by JA, fixed by ML)
- Core: upgrade problems in MySQL 4.x — fix in progress (Reported by MH, )

Stable branch: Changes between 0.6.3 and 0.6.4 (Released 2006/02/14->http://freshmeat.net/releases/219864/])

- Core: Keywords for cases/clients/org are now validated, e.g. if keyword is mandatory (by kwg policy), then the software will generate an error. Also, upon other errors after submitting form (ex: missing fields), keywords values are no longer lost. (ML)
- Core: Keyword with text value (ex: case court archive ID) is no longer added to case if it has no text value. Because of this, the court archive ID keyword would always be attached to a case. (ML)
- UI: XHTML fixes for abbr elements and the div element around the help icon. (ML)

PR1 released

- UI: In user details, the "report" tab now shows the ID of the case, not just the title. (ML)
- Core: Case search in listcases cleans the spaces in the strings in order to avoid silly errors. (Reported by SG, fixed by ML)
- Core: Fixed PHP warnings in inc_filters. (ML)
- Core: In case details, the "report" tab now allows to show the sum of follow-up times/fees by follow-up type. (ML)
- UI: If a date has no time, do not show it at all, instead of 00h00. Ex. date assignment in general case details. (ML)
- UI: Fixes to CSS so that printing "case/client/org" info does not show UI buttons or other not-for-printing items. (ML)
- UI: The case number is now included in the page title (before the case name) so that the case ID is always visible when printing a page (particularly important for the case follow-ups). (ML)
- UI: The "general" section for case, client and organisations now more readable and accessible. (Requested by KC, implemented by ML)
- UI: Added option to toggle between full/partial text of follow-up descriptions. Useful for printing the case activities. (Requested by KC, implemented by ML)
- Core: Fixed bug with client "income", "civil_status" and "gender" fields. When activated from site-config, it would cause the "client details" form to show a "panic" message. (Reported by Kenneth Canfield, fixed by ML)
- Install: Fixed warning "failed to open lcm.log" if "log" directory not yet writable — this was a problem in lcm_log(). (ML)
- Trad-ES: UK translation was using Spanish instead of English (!). (CB)
- Core: Fixed lcm_cookie.php which was still using hardcoded path to inc_connect. Because of this, the language setting of the user would not be saved in the database. Affects only installations using the Apache variables to specify an alternative path to inc_connect. (ML)

Stable branch: Changes between 0.6.2 and 0.6.3 (Released 2005/10/17)

- Trad-ES: New Spanish translation. (RLG)
- Debian: Package finally fixed. Available from SourceForge. (ML)
- Core: Now possible to configure directory for logs, data and conf, using (example) "SetEnv LcmLogDir /var/log/legalcase/", "SetEnv LcmDataDir /var/lib/legalcase/data/", "SetEnv LcmConfigDir /var/lib/legalcase/config/". Make sure that the directories exist, and have correct permissions. (ML)
- Reports: Fixed report "row = users (name), col = stage (count)". Useful when combined with "stage -> date conclusion in (...)" in order to count the number of cases closed for a given period. (ML)
- Reports: (experimental) for reports involving lists of cases and a keyword, it is now possible to click on a report value in order to list the exact occurences of the value. For example, if there are 5 cases by Author Foo, with the case keyword "ABC", then it is possible to click on the "5" in order to list the cases. (ML)
- Reports: Improved translation of fields, previously not translatable at all. (ML, CH)
- Help: Added section of help above sub-section title, in order to provide better context of content — altough far from perfect. (ML)
- Core: Fixed display of case stage context information in follow-up details screen. (ML)
- Core: Fixed access permission for button "edit follow-up" in the "view follow-up" form. (Reported by SG, fixed by ML)
- Core: New installations using MySQL >= 4.1 will now use correct character set (utf8), which is important for case-insensitive searchs. Import after export will try to create new UTF8 tables also. This is currently the only way to fix character encoding problem at the moment — alter table too dangerous (because we were storing utf8 in iso1 labeled tables, so alter table makes a big mess.. (ML)
- Reports: Fixed a few non-translated strings. (ML, CH)
- Reports: Fixed possibility to report "concluded cases, for each users, for each case-stage". (Row = user (name), Column = case-stage (stage), Filter = date-conclusion in (...). (Reported by SG, fixed by ML)
- Reports: Added a debug variable "&debug=1" in the URL of the "run_rep.php" to help us debug reports that do not execute well. (ML)
- Core: "New/Edit case" no longer allows to select hidden keywords for "case stage". (Reported by SG, fixed by ML)
- Help: Added section for "archives", re-structured a few sections, fixed typos. (ML)
- Core: Fixed "edit case" bug for PHP5. (ML)
- Core: Many many bugfixes related to installation (including one critical error in PHP5). (ML)
- New on-line help sections (in English, translated from Bulgarian) available, as well as a few structural fixes. (CH)
- Install: Another bugfix for the keyword panic problem, as well as a few PHP5 compatibilty problems fixed. (ML)

Stable branch: Changes between 0.6.1 and 0.6.2 (Released 2005/06/24)

- Install: Rewrote segment related to database connection so that it is easier to use — and less tolerant to missing loging/password. (ML)
- Trad-BG: Translation updated (incl. archive panel). (CH)
- Core: Added case stage info in follow-up details (fu_det.php) because after a stage change, it was hard to understand to which stage was a given follow-up. (ML)
- Core: Case search now searches case-keywords, such as court archive values, if any. (ML)
- Core: Added possibilitity to delete a follow-up, from the "edit follow-up" form. Deleting only hides, and it is possible to undelete in the same way. Deleting removes the follow-up from reports. (ML)
- Login: Fixed warning message related to inc_session. (reported by SG, fixed by ML)
- Trad-BG: Fixed string which showed "december" instead of "september". (reported by SG)

Note: 0.6.2pr2 released on 2005/08/04

- Core: Searching case name is now case-insensitive for non-latin alphabets, but it is not very efficient. (reported by SG, fixed by ML)
- Core: (to confirm) Fixed login problems on some PHP installations (reported by DW; fixed by ML)
- Install: Creation/update of admin user did not correctly set date_creation and date_update (reported by DW; fixed by ML)

Note: 0.6.2pr1 released on 2005/07/29

- Core: Problems of misquoted strings should be fixed, e.g. backslashes would sometimes be added to strings in non-appropriate places. (ML)
- Install: (not confirmed) "panic" problem when creating the admin account (e-mail keyword missing) should be fixed. Please confirm if you were affected by this bug. (reported by DW, JMG; fixed by ML)
- Install: When creating the admin account, e-mail is now (again) optional. (ML)
- Debug: Added OS/DB versions and more environment information in lcm_panic() messages. (ML)
- Bugfix: Login page after installation would complain of already defined "magic_unquote()". Seen on RH7.1 running PHP4.1.x. (Reported by DW, fixed by ML)
- Archiving: More functional archiving (import/export of database). Now supports automatic compressing or files for download, which can later be uploaded using the web interface (previously required FTP/SSH). (ML)

Stable branch: Changes between 0.6.0 and 0.6.1 (Released 2005/06/24)

- Install bugfix: Some "report fields" were missing, but this was mostly caused by lack of sync with inc_repfields_default.php — replaced with central upgrade_database_conf(). (ML)
- Reports: Added more possibilities for the crossing of various tables, including "case keywords" with lcm_stage, so that it’s possible to generate a report such as "depending on case type, show the distribution by case ending for a given period of time". (ML)
- Core: Added new lcm_stage table that keeps track of case creation/ending and the conclusion for the various cases. For existing installations, the table is populated based on the information stored in the case follow-ups (incl. case status/stage changes). This allows to easily generate more reports. (ML)
- Bufix: On case creation, ’date of assignment’ was not respected and always set to ’now()’. (ML)
- Bufix: After editing a follow-up, the user is sent to "view follow-up details" (instead of "view case details") — this is more logical, and also fixes a few problems with strange redirections if the form had errors and had to be revalidated. (ML)
- Bugfix: "lost data" after entering a new follow-up with an error — ex: invalid start/end date would show error message and loose the follow-up description text. (ML)
- Security fix: Added .htaccess file to the log directory, which could otherwise allow people on the same network to see confidential information — affects LCM installations on public Internet websites. (ML)
- Bugfix: value of "court archive ID" was lost on creation of a new case. (ML)
- Trad-BG: A few strange strings were fixed. (CH)
- The "case" field "id_court_archive" was hidden from many screens from the 0.6.0 release, this release converts the field into a case keywords. Affects only users who were using the id_court_archive in 0.4.x releases. (ML)
- Various fixes for the "print view" in "narrow screen" mode. (ML)
- Added ’case stage’ and ’case status’ to the list of available fields and filters in the reports — important to filter out the deleted cases from reports. (ML)
- Fixed important problem affecting MySQL 4.1.x on W32 OS, where some report types using sub-queries (such as listing activity types for all users) would cause an SQL error because the query would be cut at 256 characters. (ML)
- Fixed many issues with translation of keywords (such as follow-up types, list of stages, etc.). (ML)
- Fixed ’case deletion’ which was not working well and causing "lcm_panics" in the list of follow-ups. (ML)
- Added meta config options to hide the ’clients’ and ’organisations’ menu items and search boxes. There is no interface for this at the moment, it must be done by adding an entry in lcm_meta (client_hide_all, ’yes’) and (org_hide_all, ’yes’). (ML)
- Added config option to de-activate the case ’legal reason’ field. (ML)
- Added more types of "reports" in the report tab of a user. (ML)
- Bugfix in "edit follow-up": after an error (ex: bad fu length format), there would be an SQL error because of missing id_case. (ML)
- Added date filters in "author details" tabs for "cases", "reports" and "agenda". (ML)

Minor release: Changes between 0.4.5 and 0.6.0 (Released 2005/06/01)

- New help sections for ’reporting’ and ’keywords’ — in English.
- Fixed ’disabled edit form’ when creating a new appointment from the calendar view + a few other related minor access control problems. (ML, reported by KD)
- Trad-RU: New Russian language translation. (Sergey Salnikov / Сергей Сальников)
- Fixed quote bug in user’s first/middle/last) name. (ML)
- Fixed quote bug in "edit contacts". (ML, reported by KD)
- On-line help: Fixed typography of opening-closing quotes in English. (ML)
- Core: More work on facilitating the creation of reports. (ML)

Minor release: Changes between 0.4.4 and 0.4.5 (Released 2005/05/17)

- Core: "Report" function usability was greatly improved — altough more documentation on the issue would help. (ML)
- Trad-BG: Translation updated. (AS)
- Core: Added suggested units to sentences (months, currency, etc.). (ML, reported by MG)
- On-line help: Changed the help generation system from Spip to latex2html, and added new sections for Bulgarian. (KD, KH, ML)
- Core: Fixed bug with overload of custom translations. It is now possible to customize some terms using inc/lang/perso.php or inc/lang/perso_XX.php, using the similar structure as lcm_XX.php. The advantage of this method is to avoid loosing your custom strings between upgrades. (ML)
- UI: Added conclusion information on general section of case when it is closed. (ML)
- Core: Added possibility to un-assign a user from a case + many ’edit access rights’ changes. (ML)
- Core: Fixed missing ’date_creation’ for follow-ups of user assignments. (ML)
- Core: Added "export" function for cases, clients and organisations. (AG)
- Core: Bug fixed for old cases which caused "lcm_panic" when there was no "case stage" set for a follow-up. (ML)

Minor release: Changes between 0.4.3 and 0.4.4 (Released 2005/04/23)

- UI: "Date assignment" of case can now be edited (if site config/policy allows it, else it is set by default to ’date creation’). (ML)
- Core: Bug fixed in relation to appointments not correctly highlighted in the mini-calendar of future events. (AG)
- UI: Case court archive ID is no longer shown in the list of cases because of the stage keywords change (see next item). But we will try to compensate by having a better "search" function. (ML)
- Core: Cases can now have keywords attached to a specific stage + those keywords can have text values. Changing the case stage allows to change the keywords. For example: A case stage can now have ’court archive IDs’ which change according to the stage, as well as other user-defined fields. — experimental. (ML)
- Core: Changing case status/stage allows to enter a "conclusion" — experimental. (ML)
- Core: In "case details", it is now possible for case admins (owners) to remove clients or organisations associated with the case. (ML)
- Core: Follow-up description is now optional (was mandatory). (ML)
- Core: Fixed bug with translation of new keywords whose titles are not in the translation system. (ML)
- Core: Fixed bug which made it impossible to save user preferences. (AG)

Minor release: Changes between 0.4.2 and 0.4.3 (Released 2005/04/12)

- Core: Many many bugs fixed, in both PHP and XHTML. (ML, AG)
- UI: "My cases" has new filters (my cases, public cases, all cases + period of cases) and also shows new follow-ups related to those cases. (ML)
- Core: New "follow-up" form now allows to create a new agenda activity at the same time. (AG)
- UI: Added experimental short descriptions in some of the pages, to orient a new user. (KM)
- UI: Added tooltips of menu items (KM, ML)
- UI: The term "Author" was changed to "User" (based on feedback from CB, MG, CH, SO, AS)
- Core: Keywords can now be applied to cases, clients and organisations. This allows administrators to create new fields using multiple-choice fields. (ex: "where did the case come from", "from which region is the client", "type of case" (social problem/crime/etc.), etc.) (ML)
- UI: Client and organisation "contacts" are now shown in the "general" tab instead of in their own tab.
- Core: Added field ’notes’ to client/org/case, and added fields ’court registration’, ’tax number’, ’stat number’ to organisations. (ML)
- Core: Considering that an organisation typically has only a few new cases per day, lists of cases now show only date, not time. The full date/time is still visible in the case details page. (ML, AG)
- Core: Lists (of authors, clients, etc.) now all support search, multi-page navigation and alphabetical/numeric ordering. (ML)
- Core: In list of follow-ups, author initials now support unicode (tested with Bulgarian and Chinese names). (AG, ML)
- Calendar: Initial implementation of calendar (based on Spip), followed by many design fixes. (AG, ML, KM)
- Help: Added sub-menus + better styles. (KM)
- Core: Case details now shows total hours and money billed on case, seperated by author. (AG + ML)
- Installer: New look. (KM)
- Installer: Removed step 2 (connection confirmation) which caused confusion + clarified help. (ML + feedback from Chris Bailey)
- UI: From summary page, added button ’new client’ next to ’new case’ (since it’s a very common situation). (ML)
- UI: List of cases now shows ’creation date’ in list of fields and allows to change sorting order. (ML)
- UI: New case / edit case: enhanced UI of ’public’ read/write section + larger input boxes. (ML)

Minor release: Changes between 0.4.1 and 0.4.2 (Released 2005/03/08)

- Core: Improved keywords editing which allows to add or modify list of options in follow-ups, case stages, etc. (ML)
- Core: New agenda feature which allows to associate meetings or appointments to cases or clients — still a bit experimental. (AG)
- Core: Fix to method for entering dates in follow-ups + user configuration to choose how to enter dates. (AG)
- Core: Cases now have a „stage“ (by default: investigation, pre-trial, trial, appeal) which allows authors to see what activities are associated to which stage of the case. (AG)
- Install: New online help in English. (ML)
- UI: New print styles (lcm_print.css). Everything within LCM can now be printed (left and right columns removed in "print" mode); not fully functional yet, testing in progress. (KM)
- UI: Bug fixes for MSIE browser — "Buttons like" links in "hover" state the UI were broken in MSIE. (KM)
- UI: Icons on the menu heading (Main menu, Administration, Calendar, Agenda, Profile, Search, Font size) removed from the "inc_presentation.php" (IMG tag) and inserted in "lcm_basic_layout.css". It will be usefull to create a "non-graphical UI mode". (KM)
- UI: Many simplifications to the interface related to case stage, status and assignment to author. (AG, KM, ML)
- UI: New hover icons in navigation menu. (KM)
- UI: New “tabs” feature (for "Case details", "My preferences", "Site configuration", "Keywords", "Archives" and "Client details), which aims to make the interface easier to read. (KM)
- Trad-Br: Added Portuguese of Brazil, Português do Brasil (Luís André Beckhauser).
- Core: New import/export functions to backup the database (AG)

Minor release: Changes between 0.4.0 and 0.4.1 (Released 2005/01/26)

- UI: New login look. (KM)
- Install: Fixed bug in contact management which blocked the installation of LCM. (ML, reported by Kenneth N. Flaxman)
- Core: Follow-ups include the ID of the author, this is necessary for collaborative work. (AG)
- Core: Fixed management of "self-registration" meta which didn’t activate correctly the feature. (ML, reported by Alan Mihalic)
- Core: Minor but many fixes in the validation of the "site configuration" settings. (ML)
- Core: Language menu bug fixed, as well as a redirection bug in the "my preferences" after changing the language. (#1109722, ML, reported by Krasimir Makaveev)

Major release: Changes between 0.2 and 0.4 (Released 2005/01/24)

This release marks a first step in the stability and usability of the software, altough alot of important work is still ahead!

- UI: New dynamic support for changing font size. (KM)
- Core: Major changes in session handling code. (ML)
- Trad-BG: Major updates of the interface. (AS)
- Core: Many fixes on data validation of "edit author" page. (ML)
- Core: "Create new filter bug" fixed. (#1084230, AG)
- Core: Major improvements to how users/admins can change their passwords and status (admin/user/..). This interface was moved from "config author" (preferences) to "edit author" (personal info). Major improvements were also made to the authentication mecanism, which can now be extended to third-party systems (such as LDAP). (#1097097, ML)
- Core: Fixed bug: when a new languages was added to LCM, it did not appear in the language menu. (#1100848, ML)
- Core: In "edit author", email_main was not shown if no e-mail was present, but no way of adding it was available. (ML)

Minor release: Changes between 0.2.1 and 0.2.2 (Released 2004/12/14)

- Core: Major improvements to reporting, it is now possible to create custum reports. (AG)
- Core: Improvements to edit author, more flexible usage of contacts altough still not complete. (#1073598, ML)
- UI: Major changes to "case details" screen. (KM)
- Trad-BG: Many improvements of the Bulgarian translation for installation, lost passowrd/registration, system configuration, etc. (AS)
- UI: Added buttons/icons to "Add/Create/Attach" cases, follow-ups, etc. (KM)
- Core: Fixed bug on "edit author" by admins (#1069386, ML)
- Core: It is not possible to edit some system features, such as the types of follow-ups, type of contacts, etc. (doc, ML)
- UI: Added "wide/small" screen option, which shows the search and preferences either at the top/bottom or on a 3rd column, depending on the user’s personal settings. (KM)
- UI: Added a few "Jimmac" icons to the interface. (KM)

Minor release: Changes between 0.2.0 and 0.2.1 (Released 2004/11/10)

- Core: Improvements to author/user management. (AG)
- Core: Setting for saving user’s language setting is fixed. (ML)
- Core: All lists have a "page_rows" setting for each user. (AG)
- UI: Added CSS to make the interface more consistent + many CSS bug fixes. (KM)
- Core: Added "edit follow-up" form if user has "edit" access. (AG)
- Core: Added global "currency" setting for billing issues. (ML)
- Core: config_author.php now redirects to where the user was before changing the preferences. (AG)
- Core: Split config_site.php into 3 panels and added "policy" panel to configure optional fields for cases, clients and follow-ups. Policy configs not yet active through all the site. (ML)
- Core: Fixed problem with login of non-administrator users. (ML)
- UI: Removed CSS redundancy. Structure now in lcm_basic_layout.css and colors are in lcm_ui_*.css. Facilitates the creation of new themes. (#1053535 KM)

Major release: Changes between 0.0 and 0.2 (Released 2004/11/01)

This is a very quick overview, since it led to the initial release following 3 months of active development.

- Core: login: Fixed bug which sent passwords in clear-text to the server. If JavaScript is active, passwords now use MD5 challenges to login, using md5.js — based on Spip code (ML)
- UI: Progressive integration of date format input and output functions to have more human readable dates (#1053540 , #1056707 , #1051294 KM + AG)
- Core: Initial version of listauthors.php, edit_author.php, upd_author.php which allows LCM admins to create/edit authors (AG)
- Core: Initial version of lcm_pass.php: allows authors to self-register if the global site settings allow it, and allows authors to reset their password if lost with the help of a cookie sent by e-mail — based on Spip code (ML)
- Core: Initial version of inc/inc_db_upgrade.php and modifications to lcm_install.php to allow the administrators to upgrade the structure of the database between releases (AG + ML)
- Core: Initial version of config_author.php which allows users to chose which CSS theme and language they want to use (ML)
- UI: Each author (user) can chose which CSS theme to use for colors (KM)
- UI: LCM logo (KM)
- UI: Initial demo of look and feel of user interface in one color + fixes (KM)
- Core: Initial version of config_site.php (ML)
- Core: Initial version of add_auth.php, add_client.php, add_cli_org.php, add_org_cli.php, add_org.php, edit_client.php, edit_org.php, listclients.php, listorgs.php, org_det.php, sel_auth.php, sel_client.php, sel_cli_org.php, sel_org_cli.php, sel_org.php, upd_auth.php, upd_client.php, upd_org.php (AG)
- Core: Initial version of edit_fu.php (fu = follow-up), upd_fu.php (AG)
- Core: Initial version of listcase.php, edit_case.php, case_det.php, upd_case.php (AG)
- Core: Initial version of lcm_install.php, lcm_cookie.php, lcm_login.php, lcm_test_dirs.php (ML)
- Core: Initial version of inc/inc_version.php, inc/inc.php, inc/inc_session.php, etc. — Many based on code from Spip — Allows a multi-user environment with personalised settings (ML)

To send a message Private area xml ?