News
Analyzed 11 months
ago based on code collected 11 months ago.
|
Posted
over 43 years
ago
by
Piotr Pokora
Lodz, May 2nd 2006 -- The Midgard Project has released the second alpha release version for the upcoming 1.8 stable branch of the Midgard Open Source Content Management System.
Midgard's 1.8 branch focus on improved stability for Midgard2 ... [More] technology preview features introduced in 1.7 branch. This release is adressed for Midgard developers and users who already use configured Midgard development environments. Due to the initial support for Midgard CMS PEAR packages it's not recommended for initial setups. New branch provides metadata for all objects registered from schemas. Improved MgdSchema types managament includes features like automatic guid accessibility and ISO datetimes. Midgard-schema, new command line tool creates database's storage tables and performs tests on registered types before implementing application in production environment. PHP is no more the only one scripting language supported by Midgard. Due to MgdSchema technology Midgard provides better connectivity for Java developers. 1.8 branch is the last one Midgard branch with repligard. A new Java tool, Exorcist is available as a preview for general database replication, including Midgard and other CMS's databases. Midgard 1.8 for end users Unified Configuration New configuration file format allows users to reuse the same midgard configuration among many different applications and among many environments. New file format is in beta state in this release and will be provided as the only one recommended way to configure any applications in future Midgard releases. The main goal is to reuse configuration even with different binaries without any need to rebuild Midgard. Installation improvements Midgard CMS - MidCOM is installable and available as PEAR packages. New command line tool midgard-schema allows developers to create objects' database storage automatically. This tool is also able to perform basic object's operations ( like invoking real create or update methods ) before classes are registered in production environment. New file format is currently supported by: midgard-php used with php-cli midgard-schema midgard-query midgard-apache2 module Midgard 1.8 for developers Midgard metadata. New midgard_metadata class is new Midgard's internally initialized type which is integral part of every user defined class. midgard_metadata object is accessible as 'metadata' property for every newly created object instance. Informations like date of object's creation or last update, visibility or object's creator are available for all classes defined in schema files. This functionality also supports sheduling dates for registered classes. Even for attachments or persons. Midgard metadata in Query Builder As Midgard Query Builder is the default way to query objects from database, it also supports metadata constraints. Any object may be queried from database not only using its own properties but also using metadata property. ISO datetimes Following Midgard mRFC 0020 midgard_metadata properties with MGD_TYPE_TIMESTAMP represents dates as ISO datetimes. All dates are stored in UTC timezone in database. Improved support for GUIDs All midgard_metadata properties which are links to other types use only guids instead of ids. Additionaly every object in midgard database is represented by guid which is now stored in object's table and doesn't have to be retrieved by particular method. Database upgrade performed by datagard updates every record in database, so even records created or updated with old traditional Midgard API are converted and ready for new applications. Midgard Reflection Midgard Reflection is designed for developers who need to write "schema aware" applications without any knowledge about schema registered for application.Property's or type's attributes defined in schema files are easily accessible with Midgard Reflection objects. New datatypes for object's properties. With Midgard's Reflection one may retrieve property's type. Types like longtext or datetime defined in application's schema are easily accessible on any level wihout any need to redefine such data for application which create user's GUI based on used objects. Changes from 1.7 branch: Midgard-core Metadata for all MgdSchema objects Support for ISO metadata datetimes New Quota for MgdSchema objects Rewritten database SELECTs with performance in mind Metadata and joined objects supported by MidgardQueryBuilder Guids support for objects and metadata New midgard-schema command line tool for testing schemas and creating database tables Midgard-data repligard as part of midgard-data package exorcist , a new tool for database replication Changes from 1.8alpha1 release: Midgard-core Improved Midgard Query Builder Improved metadata object properties ability to create metadata table columns with midgard-schema Midgard Reflection Property Midgard-php Improved MgdSchema objects' constructor Experimental core's GObjects handler Core's warning and error messages populated as php error messages Extension is not built against MySQL or Apache Midgard-data PEAR packages installation and configuration support New unified configuration file support Database UTF-8 update support Planned for next releases Next 1.8beta1 release: May/June 2006 Automated database MgdSchema management and table initialization Deprecation of the classic functional Midgard API in favor of MgdSchema and Query Builder Deprecation of repligard and apache1 support. Integrated midgard-java package Download page for latest release: http://www.midgard-project.org/download/1.8.html Getting started with Midgard: http://www.midgard-project.org/documentation/ Bugs reporting: http://midgard.tigris.org/issues/reports.cgi User and developers support: Mailing list: user@midgard-project.org IRC: #midgard on irc.midgard-project.org About Midgard The Midgard Content Management Framework was initially released in May 1999, and has since gathered a sizable user and developer community. Midgard powers thousands of web sites ranging from simple organizational websites to major portals like New Zealand eGovernment site and Playbill. Midgard is being developed by an international team of professionals. Midgard's development team includes new media designers, system integrators and content management consultants. Midgard development is being supported by several commercial and governmental entities including the European Union. Piotr Pokora, Midgard release manager pp@infoglob.pl Henri Bergius, Midgard spokesman henri.bergius@iki.fi The Midgard Project http://www.midgard-project.org/ [Less] |
||||||
|
Posted
over 43 years
ago
by
Piotr Pokora
Midgard 1.8alpha2 version was
just released and BSD ports are already available before binary maintainers managed to build Midgard binary packages for all popular distros. BSD ports download page: ... [More] FreeBSD ports for Midgard CMS BSD documentation for Midgard: BSD installation guide Great thanks to Vasile VlÄdescu who is new BSD ports maintainer. [Less] |
||||||
|
Posted
over 43 years
ago
by
Piotr Pokora
This is the second midgard package released as standalone package and the second released as subrelease one.
Midgard-core 1.7.5.1 hotfix package is addressed for developers , users or administrators who use kerberos ... [More] authentication supported by new trusted auth mechanism. Download page http://www.midgard-project.org/download/1.7.html Installation manual http://www.midgard-project.org/documentation/installation-source/ [Less] |
||||||
|
Posted
over 43 years
ago
by
Piotr Pokora
Lodz, June 21st 2006 -- The Midgard Project has released stable
release version 1.7.6 of the Midgard Open Source Content Management System. 1.7.6 "Fotomodelo" provides new PAM configuration features for Midgard authentication ... [More] module. It also includes minor fixes for Midgard Quota and fixes which were included in 1.7.5.1 subreleases. Changes from 1.7.5 release: Midgard-core Fixed limit for defined type's record in midgard_quota class Disk usage size returned for every person Pam service filename configurable "Trusted" authentication type fix Midgard-apache New directive 'MidgardPamFile' for PAM authentication type Midgard-php Fixed Snippetdir copy function Midgard 1.7 for end users For the end users, Midgard 1.7 brings the mature MidCOM Content Management interface version 2.4, and the new Midgard Site Wizard for easy website creation. The new MidCOM has been developed with performance in mind, and has been moved from the Midgard database into the file system. MidCOM also includes a new output caching system. In addition to performance, MidCOM's new features include a full- fledged metadata management system and integrated content search using Apache Lucene. Midgard Site Wizard is the new default way of building Midgard powered websites. System administrator can use the easy web-based tool for setting up new organizations, websites and layout templates within the Midgard database. Be in control of your content On the applications front, Midgard includes several new tools, including a social bookmarks manager and an online order processing and shop system. Midgard 1.7 for developers For developers, Midgard 1.7 brings the first preview of the Midgard2 programming interfaces, including MgdSchema, Java support and the new Query Builder. The new programming interfaces ensure greater flexibility, and have already been tested in demanding environments. MgdSchema is the new object model for Midgard built on top of the GObject libraries. Define your own data structure in schema XML files, and get the full querying and extension mechanisms of Midgard available for them. Midgard's new Java support provides full Java Content Repository support for the Midgard Content Management System. This enables integration and content migration between Midgard and other enterprise systems. Midgard Query Builder is the new way to build database queries within the Midgard database. It supports grouped OR queries, and making queries from all properties of the MgdSchema objects. The MidCOM component framework bundled with Midgard 1.7 includes also several developer-friendly features. The new Component Base Classes make component development fast and easy, and the sessioning service enables writing of continuous applications. Changes from 1.6.0 releases: Midgard-core MgdSchema (Data structure abstraction layer) New internal types builded with GObjects and GType system XML based types definition Midgard-apache modules New MidgardSchema directive for pointing correct MgdSchema path. Page and style elements are handled by midgard internals data instead of Apache tables. Midgard-php4 Classes are defined in XML file New API methods for new MgdSchema objects Ability to run midgard-php from command line API changes: mgd_auth_midgard does not send cookie anymore http://www.midgard-project.org/documentation/reference/other/mgd_auth_midgard.html MidgardQueryBuilder class creates and executes SQL queries Midgard-data New file system based MidCOM 2.4 architecture Integrated full-text search using Apache Lucene Metadata management system Several new components including bookmarks management and online store New midcom-template package Site Creation Wizard for easy Midgard site building New style templates ready to use with the Site Wizard Datagard's 'update database' option is changed to make updates from previous Midgard installations PEAR packages installation supported by Datagard Planned for next releases Next scheduled 1.8alpha3 release: June 2006 Automated testing releases Automated database MgdSchema management and table initialization Deprecation of the classic functional Midgard API in favor of MgdSchema and Query Builder New replication system preview Download page for latest release: http://www.midgard-project.org/download/1.7.html List of changes made in MidCoM 2.4.6: http://www.midgard-project.org/midcom-permalink-4eceeb29a3b3bbdae31b2b7557d8d0e8 Features and screenshots: http://www.midgard-project.org/midgard/1.7/ Getting started with Midgard: http://www.midgard-project.org/documentation/ Bugs reporting: http://midgard.tigris.org/issues/reports.cgi User and developers support: Mailing list: user@midgard-project.org IRC: #midgard on irc.midgard-project.org About Midgard The Midgard Content Management Framework was initially released in May 1999, and has since gathered a sizable user and developer community. Midgard powers thousands of web sites ranging from simple organizational websites to major portals like New Zealand eGovernment site and Playbill. Midgard is being developed by an international team of professionals. Midgard's development team includes new media designers, system integrators and content management consultants. Midgard development is being supported by several commercial and governmental entities including the European Union. Piotr Pokora, Midgard release manager piotrek.pokora@gmail.com Henri Bergius, Midgard spokesman henri.bergius@iki.fi The Midgard Project http://www.midgard-project.org/ [Less] |
||||||
|
Posted
over 43 years
ago
by
Piotr Pokora
Lodz, June 28th 2006 -- The Midgard Project has released the third alpha release version for the upcoming 1.8 stable branch of the Midgard Open Source Content Management System.
Midgard's 1.8 branch focus on improved stability for Midgard2 ... [More] technology preview features introduced in 1.7 branch. This is the first release from 1.8 branch with full support for initial Midgard installations. It's addressed for developers and users familiar with new pear packages of Midgard CMS. New branch provides metadata for all objects registered from schemas. Improved MgdSchema types managament includes features like automatic guid accessibility and ISO datetimes. Midgard-schema, new command line tool creates database's storage tables and performs tests on registered types before implementing application in production environment. PHP is no more the only one scripting language supported by Midgard. Due to MgdSchema technology Midgard provides better connectivity for Java developers. 1.8 branch is the last one Midgard branch with repligard. Replication and undelete functionality will be fully supported by midgard core library in stable release. Midgard 1.8 for end users Unified Configuration New configuration file format allows users to reuse the same midgard configuration among many different applications and among many environments. New file format is in beta state in this release and will be provided as the only one recommended way to configure any applications in future Midgard releases. The main goal is to reuse configuration even with different binaries without any need to rebuild Midgard. New file format is currently supported by: midgard-php used with php-cli midgard-schema midgard-query midgard-apache2 module Midgard 1.8 for developers Midgard metadata. New midgard_metadata class is new Midgard's internally initialized type which is integral part of every user defined class. midgard_metadata object is accessible as 'metadata' property for every newly created object instance. Informations like date of object's creation or last update, visibility or object's creator are available for all classes defined in schema files. This functionality also supports sheduling dates for registered classes. Even for attachments or persons. Midgard metadata in Query Builder As Midgard Query Builder is the default way to query objects from database, it also supports metadata constraints. Any object may be queried from database not only using its own properties but also using metadata property. Midgard Query Builder Highly improved Query Builder can create join like SQL queries and allow to query schema objects with their corresponding parameters or attachments. New INTREE operator may be used to query objects in Midgard content tree. ISO datetimes Following Midgard mRFC 0020 midgard_metadata properties with MGD_TYPE_TIMESTAMP represents dates as ISO datetimes. All dates are stored in UTC timezone in database. Improved support for GUIDs All midgard_metadata properties which are links to other types use only guids instead of ids. Additionaly every object in midgard database is represented by guid which is now stored in object's table and doesn't have to be retrieved by particular method. Database upgrade performed by datagard updates every record in database, so even records created or updated with old traditional Midgard API are converted and ready for new applications. Midgard Reflection Midgard Reflection is designed for developers who need to write "schema aware" applications without any knowledge about schema registered for application.Property's or type's attributes defined in schema files are easily accessible with Midgard Reflection objects. midgard_reflection_property midgard_reflection_class ( not yet implemented ) New datatype for object's properties. With Midgard's Reflection one may retrieve property's type. Types like longtext or datetime defined in application's schema are easily accessible on any level wihout any need to redefine such data for application which create user's GUI based on used objects. New MidgardCollector type MidgardCollector, special and limited resource data handler optimized for performance and data accessibility. Implementation design focus on fast and easy reusable data accessibility for such features like object's parameters or even powerfull Midgard style engine. Changes from 1.7 branch: Midgard-core Metadata for all MgdSchema objects Support for ISO metadata datetimes New Quota for MgdSchema objects Rewritten database SELECTs with performance in mind Metadata and joined objects supported by MidgardQueryBuilder Guids support for objects and metadata New midgard-schema command line tool for testing schemas and creating database tables Midgard-data Repligard as part of midgard-data package Improved support for pear packages New Midgard sitewizard Midgard-php Extension is not built against MySQL or Apache Changes from 1.8alpha2 release: Midgard-core Midgard Query Builder: parameter and attachment objects queried with parent objects Midgard Query Builder: objects queried in midgard content tree New connection handler New error handling Midgard Schema validation support Pam service configurable Midgard-apache New directives for Pam services Midgard-php Guid support for legacy classes parameters and attachments fixes for parent object's guid Midgard-data Improved PEAR packages installation and configuration support Improved Database UTF-8 update support Planned for next releases Next 1.8beta1 release: July 2006 Automated database MgdSchema management and table initialization Deprecation of the classic functional Midgard API in favor of MgdSchema and Query Builder Deprecation of repligard and apache1 support. Core's library API for replication and undelete Integrated midgard-java package Download page for latest release: http://www.midgard-project.org/download/1.8.html Getting started with Midgard: http://www.midgard-project.org/documentation/ Bugs reporting: http://midgard.tigris.org/issues/reports.cgi User and developers support: Mailing list http://www.midgard-project.org/discussion/user-forum/ http://www.midgard-project.org/discussion/developer-forum/ IRC: #midgard on irc.nehmer.net About Midgard The Midgard Content Management Framework was initially released in May 1999, and has since gathered a sizable user and developer community. Midgard powers thousands of web sites ranging from simple organizational websites to major portals like New Zealand eGovernment site and Playbill. Midgard is being developed by an international team of professionals. Midgard's development team includes new media designers, system integrators and content management consultants. Midgard development is being supported by several commercial and governmental entities including the European Union. Piotr Pokora, Midgard release manager piotrek.pokora@gmail.com Henri Bergius, Midgard spokesman henri.bergius@iki.fi The Midgard Project http://www.midgard-project.org/ [Less] |
||||||
|
Posted
over 43 years
ago
by
Torben Nehmer
Project Leadership of MidCOM will move from Torben Nehmer to Tarjei Huse - Torben will leave the project for personal reasons.
Hello Community, I regret to announce that I will withdraw from the MidCOM Project ... [More] effective as of 2006-08-01. I have found a new employment last week which will start at that date. Unfortunalety, this will mean that I am no longer able to divert any time of mine to the management or the continous development of MidCOM, neither privatly nor on the job. I know that this comes on a rather short notice, but sometimes one must grasp the chances as they offer him. My new employer is the third biggest IT System Houses in all Germany, which builds a new unit devoted to ERP system development. However, this does not mean that MidCOM development will come to an halt entirely. Tarjei Huse, who was aiding me in core and component development for a long time now, has agreed to succeed my in my position as Lead Developer. He has a good knowledge of the core architectureand enough experience with MidCOM to keep development on its tracks. He has my full support and my full authority to continue where I will be leaving off. Please give him the same support and trust you gave me. To be honest, I feel a bit strange at the prospect of "giving up my baby". Especially after all these years. I have always tried to do my best in keeping a stable platform to build on. The current core is more then good enough for an upcoming stable release, except for the final packaging efforts which need to be done. What I recommend for the immediate future is to drop the original plan of a full rewrite for PHP5, not just for the missing manpower, but also because many parts of the current core are good, why rewrite bugproofed code. Instead you should refactor part after part, like I have been doing in the last monts. It has proven to be a quite successful strategy, applied carefully it should be able to yield a stable, PHP5ed core version within a year or so. The start would be a new core architecture, which splits the current application.php into a new request-oriented class tree. But enough details for now. ;-) I will try to stay available in an advisory role as long as I can, of course. Apart from that, I give my project the very best wishes for the future. Note that any further discussion of this should be done on the new MidCOM Development Mailinglist (Archives) hosted on gforge.nehmer.net. Live long and prosper! Torben Nehmer MidCOM Founder and Core Developer [Less] |
||||||
|
Posted
over 43 years
ago
by
Henri Bergius
You can help the Midgard Project by nominating it as the best Open Source CMS in the Packt CMS Awards
The Packt CMS Award '06 nominatios can be made on their website: http://www.packtpub.com/nominations |
||||||
|
Posted
over 43 years
ago
by
Henri Bergius
MidCOM, the Midgard Component Framework is finally getting compatible with PHP 5. Read more in blog entry by Henri Bergius:
Now it is possible to run CVS version of Midgard together with Subversion checkout of MidCOM with PHP 5.1. There are ... [More] still quite a few PHP Notices around, but I'm feeling optimistic that the final releases of Midgard 1.8 and MidCOM 2.6 will support PHP5. And if that happens we can then drop PHP4 support with clear conscience in the 1.9 series. [Less] |
||||||
|
Posted
over 43 years
ago
by
Piotr Pokora
Lodz, August 8th 2006 - The Midgard Project has
released the first beta release version for the upcoming 1.8 stable branch of the Midgard Open Source Content Management System. Midgard's 1.8 branch focus on ... [More] improved stability for Midgard2 technology preview features introduced in 1.7 branch. First beta release is fully customizable and installable release adressed for developers and users who want to use Midgard environment on testing and even semi-production servers. New branch provides metadata for all objects registered from schemas. Improved MgdSchema types managament includes features like automatic guid accessibility and ISO datetimes. Midgard-schema, new command line tool creates database's storage tables and performs tests on registered types before implementing application in production environment. PHP is no more the only one scripting language supported by Midgard. Due to MgdSchema technology Midgard provides better connectivity for Java developers. 1.8 branch is the last one Midgard branch with repligard. Replication and undelete functionality will be fully supported by midgard core library in stable release. Midgard 1.8 for end users Unified Configuration New configuration file format allows users to reuse the same midgard configuration among many different applications and among many environments. New file format is in beta state in this release and will be provided as the only one recommended way to configure any applications in future Midgard releases. The main goal is to reuse configuration even with different binaries without any need to rebuild Midgard. New file format is currently supported by: midgard-php used with php-cli midgard-schema midgard-query midgard-apache2 module Midgard 1.8 for developers Midgard metadata. New midgard_metadata class is new Midgard's internally initialized type which is integral part of every user defined class. midgard_metadata object is accessible as 'metadata' property for every newly created object instance. Informations like date of object's creation or last update, visibility or object's creator are available for all classes defined in schema files. This functionality also supports sheduling dates for registered classes. Even for attachments or persons. Midgard metadata in Query Builder As Midgard Query Builder is the default way to query objects from database, it also supports metadata constraints. Any object may be queried from database not only using its own properties but also using metadata property. Midgard Query Builder Highly improved Query Builder can create join like SQL queries and allow to query schema objects with their corresponding parameters or attachments. New INTREE operator may be used to query objects in Midgard content tree. ISO datetimes Following Midgard mRFC 0020 midgard_metadata properties with MGD_TYPE_TIMESTAMP represents dates as ISO datetimes. All dates are stored in UTC timezone in database. Improved support for GUIDs All midgard_metadata properties which are links to other types use only guids instead of ids. Additionaly every object in midgard database is represented by guid which is now stored in object's table and doesn't have to be retrieved by particular method. Database upgrade performed by datagard updates every record in database, so even records created or updated with old traditional Midgard API are converted and ready for new applications. Midgard Reflection Midgard Reflection is designed for developers who need to write "schema aware" applications without any knowledge about schema registered for application. Property's or type's attributes defined in schema files are easily accessible with Midgard Reflection objects. midgard_reflection_property midgard_reflection_class ( not yet implemented ) New datatype for object's properties. With Midgard's Reflection one may retrieve property's type. Types like longtext or datetime defined in application's schema are easily accessible on any level wihout any need to redefine such data for application which create user's GUI based on used objects. New MidgardCollector type MidgardCollector, special and limited resource data handler optimized for performance and data accessibility. Implementation design focus on fast and easy reusable data accessibility for such features like object's parameters or even powerfull Midgard style engine. Changes from 1.7 branch: Midgard-core Metadata for all MgdSchema objects Support for ISO metadata datetimes New Quota for MgdSchema objects Rewritten database SELECTs with performance in mind Metadata and joined objects supported by MidgardQueryBuilder Guids support for objects and metadata New midgard-schema command line tool for testing schemas and creating database tables Midgard-data Repligard as part of midgard-data package Improved support for pear packages New Midgard sitewizard Midgard-php Extension is not built against MySQL or Apache Changes from 1.8alpha3 release: Midgard-core Improved mulitilingual support Replication related functions rewritten for guids only New API get_languages method for MgdSchema objects midgard_topic class defined with multilingual support Midgard-apache Improved missed root file "detection" Midgard-php Legacy MidgardTopic class rewritten with multilingual support Implemented midgard_collector for PHP4 and PHP5 language bindings Improved PHP5 support New language functions: mgd_set_default_lang and mgd_get_default_lang New API get_languages method for MgdSchema objects. Midgard-data Removed obsolete layout xml packages Fixed new configuration file management Fixed cache and lib directories permissions Midcom's static dirs configurable via pear packages Planned for next releases Next 1.8beta2 release: September 2006 Automated database MgdSchema management and table initialization Deprecation of the classic functional Midgard API in favor of MgdSchema and Query Builder Deprecation of repligard and apache1 support. Core's library API for replication and undelete Integrated midgard-java package Download page for latest release: http://www.midgard-project.org/download/1.8.html Getting started with Midgard: http://www.midgard-project.org/midgard/1.8/ Documentation: http://www.midgard-project.org/documentation/ Bugs reporting: http://midgard.tigris.org/issues/reports.cgi User and developers support: Mailing list http://www.midgard-project.org/discussion/user-forum/ http://www.midgard-project.org/discussion/developer-forum/ IRC: #midgard on irc.nehmer.net About Midgard The Midgard Content Management Framework was initially released in May 1999, and has since gathered a sizable user and developer community. Midgard powers thousands of web sites ranging from simple organizational websites to major portals like New Zealand eGovernment site and Playbill. Midgard is being developed by an international team of professionals. Midgard's development team includes new media designers, system integrators and content management consultants. Midgard development is being supported by several commercial and governmental entities including the European Union. Piotr Pokora, Midgard release manager piotrek.pokora@gmail.com Henri Bergius, Midgard spokesman henri.bergius@iki.fi The Midgard Project http://www.midgard-project.org/ [Less] |
||||||
|
Posted
over 43 years
ago
by
Piotr Pokora
1.7.6.1 hotfix packages
midgard-core fixed float type for Query Builder constraints midgard-php MgdSchema types' parameter metod uses anonymous mode midgard-data fixed cache directory permission Download page |
||||||
Code Data
SCM Data
Community Data
Copyright
©
2013
Black Duck Software, Inc.
and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a
Creative Commons Attribution 3.0 Unported License
. Ohloh
®
and the Ohloh logo are trademarks of
Black Duck Software, Inc.
in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.