Midgard

General
Development
Edit

News

[249 total ]
Come to celebrate the 10th Anniversary of the Midgard Project

Posted 9 months ago by henri....@iki.fi (Henri Bergius)

May 8th 1999:

The Midgard Project has finally released the first public version of Midgard Application Server Suite. The new release contains Midgard core libraries, a PHP3-based web application server for the Apache platform and the needed ... [More] web-based administration tools.
May 8th 2009:

It's time for celebration - Midgard CMS turns ten in May! The decade of Midgard will be celebrated with a guest gala that is to be held at restaurant Ostrobotnia in Helsinki, Finland.
Looking forward to seeing as many of you in the party as possible! Please register ASAP as we need to tell the restaurant how many tables are needed. [Less]

Midgard 8.09.4 "Kaiku" released

Posted 9 months ago

Lodz, March 12th 2009 -- The Midgard Project has released the fourth
maintenance release of Midgard 8.09 Ragnaroek LTS.
Ragnaroek LTS is a Long Term Support version of the free software
content management framework.

The 8.09.4 ... [More] "Kaiku" release focuses on API and architecture cleanups
in order to ease transition from Midgard 1.x series API to Midgard 2.x APIs.

Stable 8.09.4 release is recommended for all users of Midgard.

Main changes from 8.09.3:

Midgard installer doesn't depend on pearified.com channel (#747)
Memory corruption in midgard-php extension has been fixed (#804)
Query Builder and Collector constructors has been improved (#556)
Several crashes has been fixed (#712, #734, #801, #870)
Internal PHP classes can be introspected by PHP Reflection (#479)
midgard_cron has been improved (#813, #816)
URL name handling and generation has been rewritten (#809)
TinyMCE WYSIWYG editor has been upgraded to version 3.2.2
Issues with handling multilingual content have been fixed (#870, #825, #935, #865, #910)
Code editor in Asgard has been changed from CodePress to EditArea
Configuration editor in Asgard now always creates valid configuration snippets (#771)
MidCOM now uses only the modern Midgard2 API (#611)
PAM authentication has been fixed (#750)
Midgard now ships with SELinux policy files (#538)

In total 156 tickets have been closed for this release. See the Midgard
issue tracker for a full list:
http://trac.midgard-project.org/query?status=closed&milestone=8.09.4 Ragnaroek

Planned for next maintenance release:

More performance tuning
Unit tests for midgard-php and MidCOM DBA layers
New Midgard visual guidelines deployed more widely
Filesync git integration for collaborative site development
MidCOM packages distributed by a Midgard-powered PEAR channel

See the full list in:
http://trac.midgard-project.org/query?status=new&status=assigned&status=reopened&status=closed&milestone=8.09.4 Ragnaroek&order=priority

Source downloads

http://www.midgard-project.org/download/

Binary packages

http://download.opensuse.org/repositories/home:/midgardproject:/ragnaroek/

Getting started

http://www.midgard-project.org/documentation/getting-started/

Issue tracker

http://trac.midgard-project.org/roadmap

More information

Piotr Pokora, Midgard release manager
piotrek.pokora(at)gmail.com

Henri Bergius, Midgard bug master
henri.bergius(at)iki.fi

The Midgard Project
http://www.midgard-project.org/

  [Less]

Midgard2 9.03.0beta1 "Kieku" released

Posted 9 months ago

Lodz, March 12th 2009 -- The Midgard Project has released a first beta of Midgard2 9.03 "Vinland" - the new  generation of the Midgard content repository.

About this release

The first beta of Midgard2 9.03 is targeted at web ... [More] framework and desktop developers. It provides a comprehensive set of content repository APIs that can be used to build replicated information applications that share their information using a common storage layer and replication tools.

Vinland series of Midgard2 is not intended to act as a content management system, and so no CMS tools are shipped with the release. Midgard2 Vinland however can be used to build a CMS, or to refactor existing CMS tools to work with a repository-centric model.

In this release we provide Content Repository API bindings for the following programming languages: C, Python, PHP. D-Bus signals are used to inform different Midgard2 applications about things happening in the repository, enabling for example a PHP website and a Python background process to communicate with each other.

Midgard2

Midgard2 is a content reporitory. It provides an object-oriented and replicated environment for building data-intensive applications.

Midgard's philosophy includes building on top of a well-known and supported GNOME libraries like glib and libgda on the system end, and connecting with popular programming languages like PHP and Python. Data storage can utilize SQLite with desktop and mobile applications, or a database server like MySQL or Postgres for web application storage.

The Midgard2 platform enables developers to define a storage structure once and use it on both web and desktop applications, with the possibility of easy data replication between the two.

Read more about Midgard's content repository approach:

http://bergie.iki.fi/blog/midgard2_at_fscons-your_data-everywhere
http://bergie.iki.fi/blog/midgard_and_jcr-a_look_at_two_content_repositories
http://teroheikkinen.iki.fi/blog/midgard_workshop_at_fscons
 

New Midgard architecture
 

Language independence

Midgard is also language independent and due to its powerful architecture has proven as stable, secure and flexible solution implemented in various environments:

PHP5 extension for web application and CMS development
Python module for desktop application and background process development
Mono module for desktop application and background process development in C#
 

Database independence

The Midgard 1.x was heavily coupled with the MySQL database. The new Midgard2 architecture is instead built on top of libgda, the GNOME database abstraction layer. This enables Midgard to be used with various storage engines, including:

MySQL
Postgres
SQLite
Microsoft SQL Server
Oracle
DB2
 

Built-in replication and metadata

All Midgard objects are automatically equipped with a consistent set of metadata properties that can be used for access control and workflow.

In addition, Midgard provides an API for serializing and unserializing stored objects in XML format that can be used for replicating data between different systems. The replication architecture can be used for staging/live web environments or mobile applications that synchronize between each other or a web back-end.

Planned for next Midgard2 releases
MidCOM, an elegant PHP MVC framework written for Midgard2
Objective-C bindings and native Mac packages
Mono (C#) bindings
 

Midgard resources
 

Download page and changelog for latest release
Bug reporting
 

User and developers support:
 

Users' forum
Developers' forum
IRC: #midgard on irc.freenode.net
 

About Midgard

The Midgard Framework development started in 1997 and it was initially released as free software in May 1999. Midgard Project has since gathered an active user and developer community, powering thousands of web sites ranging from simple organizational intranets to large community portals.

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 has been supported by several commercial and governmental entities including the European Union and the Swedish Internet Foundation.

Midgard is free software available under the GNU LGPL license.

Contacts

Piotr Pokora, Midgard release manager
piotrek.pokora(at)gmail.com

Henri Bergius, Midgard spokesman
henri.bergius(at)iki.fi

The Midgard Project
http://www.midgard-project.org [Less]

Midgard-data 8.09.3.1 hotfix

Posted 10 months ago

Midgard-data hotfix already available. Pearified channel related issue has been fixed and datagard works correctly again.

New package is available from download page.

Binary packages should be ready in next few hours.

 

 

New installs of Midgard temporarily disrupted because pearified.com is down

Posted 11 months ago

Pearified.com, an external provider of some PEAR packages used in the Midgard environment is at the moment unavailable. This affects the following Midgard dependencies:

Role_Web: installing public files to server DocumentRoot, deprecated by ... [More] PEAR's new www role
Javascript_Prototype: the prototype javascript library used by some components
Javascript_Scriptaculous: the Scriptaculous javascript library used by some components

Because of this, new installs of Midgard are temporarily unavailable. See bug #747 for more information.

The Midgard team is preparing a 8.09.3.1 maintenance release to resolve this issue as soon as possible. We apologize for the inconvenience. [Less]

Midgard 8.09.3 "New Year's diet" released

Posted 11 months ago by piotrek...@gmail.com (Piotr Pokora)

Lodz, January 12th 2009 -- The Midgard Project has released the third
maintenance release of Midgard 8.09 Ragnaroek LTS.
Ragnaroek LTS is a Long Term Support version of the free software
content management framework.

The 8.09.3 ... [More] "New Year's diet" release focuses on API and architecture cleanups
in order to ease transition from Midgard 1.x series API to Midgard 2.x APIs.

Stable 8.09.3 release is recommended for all users of Midgard.

Main changes from 8.09.2:

MidCOM DBA has been rewritten to follow decorator pattern instead of inheritance (#456 and #599)
There is a new online help and documentation viewer
Safari user experience has been greatly improved (#583, #585)
Basic authentication on Midgard level has been fixed (#485)
MidCOM cron is now automatically set up for new virtual hosts (#378)
All legacy metadata fields have been removed in favor of midgard_metadata object (#387, #464, #476 and #477)
Replication has been changed to work using the new API and decorators (#627, #607, #534, #501, 513, #564
File attachments now have MultiLang emulation (#420)
In-page Ajax editing can now be disabled and enabled globally (#526)
Midgard's tree management has been improved in many ways (#447, #482, #483, #600, #602, #625)
HTTP errors can be mapped to notifications or special logging (#305)
The Midgard PHP extension is now approximately 50% faster

In total 151 tickets have been closed for this release. See the Midgard issue tracker for a full list:
http://trac.midgard-project.org/query?status=closed&milestone=8.09.3 Ragnaroek

Planned for next maintenance release:

More performance tuning
Unit tests for midgard-php and MidCOM DBA layers
New Midgard visual guidelines deployed more widely
Filesync git integration for collaborative site development
MidCOM packages distributed by a Midgard-powered PEAR channel

See the full list in:
http://trac.midgard-project.org/query?status=new&status=assigned&status=reopened&status=closed&milestone=8.09.4 Ragnaroek&order=priority

Source downloads

http://www.midgard-project.org/download/

Binary packages

http://download.opensuse.org/repositories/home:/midgardproject:/ragnaroek/

Getting started

http://www.midgard-project.org/documentation/getting-started/

Issue tracker

http://trac.midgard-project.org/roadmap

More information

Piotr Pokora, Midgard release manager
piotrek.pokora(at)gmail.com

Henri Bergius, Midgard bug master
henri.bergius(at)iki.fi

The Midgard Project
http://www.midgard-project.org/ [Less]

Midgard 8.09.0RC3 "Ragnaroek" released

Posted 12 months ago by piotrek...@gmail.com (Piotr Pokora)

Lodz, December 30th 2008 -- The Midgard Project has released a third release candidate for the third maintenance release of Midgard 8.09 Ragnaroek LTS. Ragnaroek LTS is a Long Term Support version of the free software content management ... [More] framework.

The 8.09.3 release focuses on API and architecture cleanups in order to ease transition from Midgard 1.x series API to Midgard 2.x APIs.

When out, the final 8.09.3 release will be recommended for all users of Midgard.

Changes from 8.09.3RC2:

Fixed database tables' layout for initial setups
Replication is faster objects which hold guid references
Minor bugfixes
Main changes from 8.09.2:

MidCOM DBA has been rewritten to follow decorator pattern instead of inheritance (#456 and #599)
There is a new online help and documentation viewer
Safari user experience has been greatly improved (#583, #585)
Basic authentication on Midgard level has been fixed (#485)
MidCOM cron is now automatically set up for new virtual hosts (#378)
All legacy metadata fields have been removed in favor of midgard_metadata object (#387, #464, #476 and #477)
Replication has been changed to work using the new API and decorators (#627, #607, #534, #501, 513, #564
File attachments now have MultiLang emulation (#420)
In-page Ajax editing can now be disabled and enabled globally (#526)
Midgard's tree management has been improved in many ways (#447, #482, #483, #600, #602, #625)
HTTP errors can be mapped to notifications or special logging (#305)
The Midgard PHP extension is now approximately 50% faster

In total 145 tickets have been closed for this release. See the Midgard issue tracker for a full list:
http://trac.midgard-project.org/query?status=closed&milestone=8.09.3 Ragnaroek

Planned for next maintenance release:

More performance tuning
Unit tests for midgard-php and MidCOM DBA layers
New Midgard visual guidelines deployed more widely
Filesync git integration for collaborative site development
MidCOM packages distributed by a Midgard-powered PEAR channel

See the full list in:
http://trac.midgard-project.org/query?status=new&status=assigned&status=reopened&status=closed&milestone=8.09.4 Ragnaroek&order=priority

Source downloads

http://www.midgard-project.org/download/

Binary packages

http://download.opensuse.org/repositories/home:/midgardproject:/ragnaroek/

Getting started

http://www.midgard-project.org/documentation/getting-started/

Issue tracker

http://trac.midgard-project.org/roadmap

More information

Piotr Pokora, Midgard release manager
piotrek.pokora(at)gmail.com

Henri Bergius, Midgard bug master
henri.bergius(at)iki.fi

The Midgard Project
http://www.midgard-project.org/ [Less]

Midgard 8.09.3RC2 released

Posted 12 months ago by piotrek...@gmail.com (Piotr Pokora)

Lodz, December 18th 2008 -- The Midgard Project has released a second release candidate for the third maintenance release of Midgard 8.09 Ragnaroek LTS. Ragnaroek LTS is a Long Term Support version of the free software content management ... [More] framework.

The 8.09.3 release focuses on API and architecture cleanups in order to ease transition from Midgard 1.x series API to Midgard 2.x APIs.

When out, the final 8.09.3 release will be recommended for all users of Midgard.

This release includes several major - backward compatible - improvements and fixes.

Main changes from 8.09.2:

MidCOM DBA has been rewritten to follow decorator pattern instead of inheritance (#456 and #599)
There is a new online help and documentation viewer
Safari user experience has been greatly improved (#583, #585)
Basic authentication on Midgard level has been fixed (#485)
MidCOM cron is now automatically set up for new virtual hosts (#378)
All legacy metadata fields have been removed in favor of midgard_metadata object (#387, #464, #476 and #477)
Replication has been changed to work using the new API and decorators (#627, #607, #534, #501, 513, #564
File attachments now have MultiLang emulation (#420)
In-page Ajax editing can now be disabled and enabled globally (#526)
Midgard's tree management has been improved in many ways (#447, #482, #483, #600, #602, #625)
HTTP errors can be mapped to notifications or special logging (#305)
The Midgard PHP extension is now approximately 50% faster

In total 130 tickets have been closed for this release. See the Midgard issue tracker for a full list:
http://trac.midgard-project.org/query?status=closed&milestone=8.09.3 Ragnaroek

Planned for next maintenance release:

More performance tuning
Unit tests for midgard-php and MidCOM DBA layers
New Midgard visual guidelines deployed more widely
Filesync git integration for collaborative site development
MidCOM packages distributed by a Midgard-powered PEAR channel

See the full list in:
http://trac.midgard-project.org/query?status=new&status=assigned&status=reopened&status=closed&milestone=8.09.4 Ragnaroek&order=priority

Source downloads

http://www.midgard-project.org/download/

Binary packages

http://download.opensuse.org/repositories/home:/midgardproject:/ragnaroek/

Getting started

http://www.midgard-project.org/documentation/getting-started/

Issue tracker

http://trac.midgard-project.org/roadmap

More information

Piotr Pokora, Midgard release manager
piotrek.pokora(at)gmail.com

Henri Bergius, Midgard bug master
henri.bergius(at)iki.fi

The Midgard Project
http://www.midgard-project.org/ [Less]

Midgard 8.09.3RC released

Posted 12 months ago by piotrek...@gmail.com (Piotr Pokora)

Lodz, December 15h 2008 -- The Midgard Project has released a release candidate for the third maintenance release of Midgard 8.09 Ragnaroek LTS. Ragnaroek LTS is a Long Term Support version of the free software content management ... [More] framework.

The 8.09.3 release focuses on API and architecture cleanups in order to ease transition from Midgard 1.x series API to Midgard 2.x APIs.

When out, the final 8.09.3 release will be recommended for all users of Midgard.

Main changes from 8.09.2:

MidCOM DBA has been rewritten to follow decorator pattern instead of inheritance (#456 and #599)
There is a new online help and documentation viewer
Safari user experience has been greatly improved (#583, #585)
Basic authentication on Midgard level has been fixed (#485)
MidCOM cron is now automatically set up for new virtual hosts (#378)
All legacy metadata fields have been removed in favor of midgard_metadata object (#387, #464, #476 and #477)
Replication has been changed to work using the new API and decorators (#627, #607, #534, #501, 513, #564
File attachments now have MultiLang emulation (#420)
In-page Ajax editing can now be disabled and enabled globally (#526)
Midgard's tree management has been improved in many ways (#447, #482, #483, #600, #602, #625)
HTTP errors can be mapped to notifications or special logging (#305)
The Midgard PHP extension is now approximately 50% faster

In total 130 tickets have been closed for this release. See the Midgard issue tracker for a full list:
http://trac.midgard-project.org/query?status=closed&milestone=8.09.3 Ragnaroek

Planned for next maintenance release:

More performance tuning
Unit tests for midgard-php and MidCOM DBA layers
New Midgard visual guidelines deployed more widely
Filesync git integration for collaborative site development
MidCOM packages distributed by a Midgard-powered PEAR channel

See the full list in:
http://trac.midgard-project.org/query?status=new&status=assigned&status=reopened&status=closed&milestone=8.09.4 Ragnaroek&order=priority

Source downloads

http://www.midgard-project.org/download/

Binary packages

http://download.opensuse.org/repositories/home:/midgardproject:/ragnaroek/

Getting started

http://www.midgard-project.org/documentation/getting-started/

Issue tracker

http://trac.midgard-project.org/roadmap

More information

Piotr Pokora, Midgard release manager
piotrek.pokora(at)gmail.com

Henri Bergius, Midgard bug master
henri.bergius(at)iki.fi

The Midgard Project
http://www.midgard-project.org/ [Less]

Midgard's SVN reorganized

Posted about 1 year ago by henri....@iki.fi (Henri Bergius)

As part of the Midgard Gathering held in Espoo, Finland last weekend, Midgard's SVN repository was reorganized to follow the new release synchronicity strategy.

The repository is now organized in the following way:

trunk: The next ... [More] generation of Midgard that is currently under development, at the moment 9.03 Vinland
branches/ragnaroek: Midgard 8.09 Ragnaroek LTS
branches/thor: Midgard 1.8 and MidCOM 2.8
branches/loki: Midgard 1.7 and MidCOM 2.6
branches/classic: Midgard 1.6 and MidCOM 2.4

Under each of these there are two subdirectories:

midgard: Midgard core and language bindings
midcom: The Midgard components framework

The policy on working with Midgard sources is that each generation branch, and Midgard trunk should be kept stable. To make larger changes possible, it is recommended that developers utilize git-svn and feature branches for their work.

To make a local git checkout of Midgard's SVN repository, use the following command:

git svn clone https://svn.midgard-project.org/midgard/ -T trunk -b branches -t tags

For working with Git, there are some useful tutorials:

Git SVN crash course
How to track multiple SVN branches in git
Feature branches in Midgard development with git

Commit access to the repository can be requested from the VCS Tyrant Eero af Heurlin, who also monitors all commits. The same username and password as used on this site is applicable with Midgard SVN. [Less]