MidCOM 1.3.2 released
Posted on 2004-07-20 11:09:42 CEST.
GUENZBURG, 2004-07-20 -- The Midgard Project has released version 1.3.2 of the Midgard Components Framework (MidCOM). MidCOM provides a framework for creating reusable and configurable components for web applications using the Midgard Content Management Framework. This is primarily a Bugfix release.
MidCOM development was started by Linksystem Muenchen in March 2002, and it has since evolved into a stable and production-proven platform. Its continuing development is now too sponsred bei Nemein Oy. MidCOM is available under GNU LGPL.
This is a maintanance release, there were no API changes, everything has been done to prevent any compatibility issues when upgrading from 1.3.1 to 1.3.2.
This update is recommended for everybody using UTF-8 on-site, it fixes several bugs in this respect. UTF-8 should now work seamlessly with MidCOM. The Mulitbyte String aliases are supported with this release too.
Bugfixes since MidCOM 1.3.1:
- Replaced htmlentities with htmlspecialchars throughout the package and the main components for UTF-8 compatibility, this mostly fiexes #34, some infrequently used components are still missing this fix.
- Core
- MidCOM error pages all had HTTP Response status code 200, this has been fixed.
- Datamanager
- Fixed the handling of readonly and hidden fields within the form processing code. This prevents accidential overwrites of the data, which could happen while in create mode when using preset fields.
- Made the handling of schema snippets more robust against //-style comments in the last line.
- Fix for #69 (Image datatype: Do not scale images upwards.)
- Content Manager
- Show only MidgardGroups from the current sitegroup in the Topic edit and create dialogs, fixes Bug #67.
- Caching Engine
- Fixed critical bug when UTF-8 with the mb_string function overloads where used. The DBM-cache generated too small numbers for the Content-Length header, which lead into truncated files on delivery.
- Component de.linkm.taviewer
- The NAP code tries to finde a suitable name to display an article in mor cases now, to avoid the infamous edit/123 links we often see in AIS, fixes Bug #13.
MidCOM requires working PHP 4.1 or later with the iconv extension and Midgard 1.4.4 or later. In addition, Aegir 1.0.1 is recommended for using the MidCOM Site Template package.
Download Page: http://www.midgard-project.org/projects/midcom/download/
Installation instructions: http://www.midgard-project.org/documentation/installation/midcom
Getting started guide: http://www.midgard-project.org/documentation/getting-started/
Project Bugtracker:
http://midcom.tigris.org/servlets/ProjectIssues
Torben Nehmer, MidCOM Lead Developer