User forum

Re: Help: after pear upgrade Midgard stopped working

Henri Bergius — Wed, 21 Jul 2010 13:47:35 +0000

Hi,

I'm running Midgard 8.09 on Debian Lenny (installed from source) and it went fine until i decided to run a "pear upgrade" yesterday..

afterwards I couldn't reach my Midgard-site because of an Error:500 DB Class Loader: Classes from file /usr/share/php/midcom/lib/midcom/config/core_classes.inc couldn't be registered.

This sounds like you have a different configuration for PEAR's Role_MgdSchema and Midgard itself. One expects to place MgdSchemas to /usr/share/midgard/schema, and the other to find them from /usr/local/share/midgard/schema (or whatever prefix you used when building Midgard).

You can check this by looking at those directories, and running pear config-show.

/Bergie

Help: after pear upgrade Midgard stopped working

Alexander Schuster — Fri, 16 Jul 2010 20:19:21 +0000

Hi all,

I'm running Midgard 8.09 on Debian Lenny (installed from source) and it went fine until i decided to run a "pear upgrade" yesterday..

afterwards I couldn't reach my Midgard-site because of an Error:500 DB Class Loader: Classes from file /usr/share/php/midcom/lib/midcom/config/core_classes.inc couldn't be registered.

I've skimmed the logfiles (not yet set to debug) but found nothing helpful. Can anyone point me to a solution???

Thanks in advance,

Alex

PS: I've been with midgard for years (basically the whole midgard1-era) but lost track the last years and now I try to get up-to-date. Expect more stupid questions to come once I've got my midgard back working ;)

[Announcement] Midgard2 10.05.1 "Ratatoskr" LTS released

Piotr Pokora — Tue, 22 Jun 2010 14:22:47 +0000

Lodz, June 22nd 2010 -- The Midgard Project has released the first maintenance release of Midgard2 10.05.1 "Ratatoskr" LTS. Ratatoskr LTS is a Long Term Support version of Midgard2 Content Repository.

About 10.05 releases

Midgard2 10.05 is targeted at web framework and desktop application 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.

In this release we provide:

Content Repository API bindings for the following programming languages: C, Python, PHP and Objective-C. 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.
Midgard MVC, an elegant framework for PHP web applications. Midgard MVC includes interfaces for loadable components, hierarchical sub-requests, a forms system and much more.
Midgard Runtime that combines the Midgard MVC, a PHP application server and a WebKit UI to provide a full Midgard web development environment on the desktop.

Main changes from 10.05.0 release:

Major fixes in new MidgardQuery classes
Many improvements for GObject Introspection
Fixed critical issues in MidgardView generation
MidgardQuery classes has been implemented in PHP and Python bindings
Improved installer for Midgard Runtime
midgard_dbus class available in PHP bindings only if core is built with DBus support
Fixed datetime related crash in Python bindings

Main changes from 9.09 releases:

Improved core which supports GObject Introspection
Built on top of Libgda4
Replication , quota and DBus are now optional and fully configurable
Improved performance

New functionalities in 10.05 releases:

New reflection and introspection routines
New database query interfaces
New language bindings: vala and mono (C#)

Midgard2

Midgard2 is a content repository. It provides an object-oriented and replicated environment for building data-intensive applications. This provides several advantages

Common rules for data access mean that multiple applications can work with same content without breaking consistency of the data
Signals about changes let applications know when another application using the repository modifies something, enabling collaborative data management between apps
Objects instead of SQL mean that developers can deal with data using APIs more compatible with the rest of their desktop programming environment, and without having to fear issues like SQL injection
Data model is scriptable when you use a content repository, meaning that users can easily write Python or PHP scripts to perform batch operations on their data without having to learn your storage format
Synchronization and sharing features can be implemented on the content repository level meaning that you gain these features without having to worry about them

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/why_you_should_use_a_content_repository_for_your_application/ * 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
Objective-C package for Mac OS X and GNUstep developers

It also provides bindings for other languages:

Vala
Mono (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.

Midgard resources

User and developers support:

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

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.

Midgard2 is free software available under the GNU LGPL license.

http://www.midgard2.org

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

[Announcement] Midgard 8.09.9 released!

Piotr Pokora — Tue, 22 Jun 2010 09:00:56 +0000

Lodz, June 22nd 2010 -- The Midgard Project has released the ninth maintenance release of Midgard 8.09 Ragnaroek LTS. Ragnaroek LTS is a Long Term Support version of the free software Content Management Framework.

Midgard is an industrial CMS built on top of a Content Repository and the LAMP stack. It provides object-oriented PHP APIs for developing and modifying website functionalities, and a PEAR-based system for installing new web components from a growing online library. Midgard has been running since 1999 on systems ranging from simple organizational websites to complex web communities and corporate management tools, in organizations like Aalto University, Nokia, Lufthansa, HP, Poland International Fairs and CMS Watch.

The stable 8.09.9 release is recommended for all users of Midgard.

Main changes from 8.09.8:

Rewritten Multilang queries (#1776)
Fixed crashes (#1547, #1684)
Fixed major MidCOM admin and style issues (#1779, #1788)
Midgard internal features are now optional for better performance tunning (#1851)
Many bugfixes and feature enhancements

In total more than 90 feature requests or bugs have been handled in this release. See the Midgard issue tracker for a full list.

Binary packages

The Midgard Project provides binary packages that are ready to install for most popular Linux distributions. This includes various versions of Debian, Fedora, Ubuntu, RHEL and openSUSE. See the full list:

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

Distribution-specific installation instructions can be found from the Midgard documentation site.

Source downloads

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

Instructions for building Midgard from the sources can be found from the Midgard documentation site.

Getting started

On a typical Linux distribution setting up Midgard is quite trivial. Simply add the Midgard repository to your configuration, and then run: # apt-get update # apt-get install midgard-data # datagard

After this you should have a running Midgard server. Simply access it with the browser and follow the instructions provided on the Midgard Getting Started guide

Issue tracker & getting help

See the Midgard issue tracker for currently open issues and planned enhancements. http://trac.midgard-project.org/roadmap

If you need help with your Midgard setup, the #midgard IRC channel on freenode is the best place to start. There is also an user mailing list.

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/

Re: [midgard-user] Midgard and PhPUnit

Henri Bergius — Fri, 18 Jun 2010 13:45:03 +0000

Hi,

On Fri, Jun 18, 2010 at 12:36 PM, Henri Bergius henri.bergius@iki.fi wrote:

In this case the Midgard MVC unit test setup might be possible to adapt to your use:

I just refactored Midgard MVC's PHPUnit test harness a bit. Basically your application would need something similar to http://github.com/midgardproject/midgardmvc_core/blob/master/tests/midgard.php

...then just write your PHPUnit testcases inheriting from that class.

Note that this version uses the methods for opening a Midgard connection that are present from Midgard 8.09 onwards (and in Midgard2), so they need to be rewritten to use the classic Midgard connection API.

-- Henri Bergius Motorcycle Adventures and Free Software http://bergie.iki.fi/

Skype: henribergius Jabber: henri.bergius@gmail.com Microblog: http://www.qaiku.com/home/bergie/

user mailing list user@lists.midgard-project.org http://lists.midgard-project.org/mailman/listinfo/user

Re: [midgard-user] Midgard and PhPUnit

Henri Bergius — Fri, 18 Jun 2010 10:05:02 +0000

Hi,

On Fri, Jun 18, 2010 at 12:14 PM, Piotr Pokora piotrek.pokora@gmail.com wrote:

Our application is an internal application used by thousands of users to manage client environments...

I had heard rumors of this before. The typical situation with Open Source is that you can't really know who is using your software. So, cool! Very nice to hear of this.

Yeah, elements are kept in memory, so no single file is involved here. I wonder if you could try with cache files, usually stored in /var/cache/midgard.

The other option (and probably better) would be to have unit tests for actual classes of the application. Are they handled in filesystem or snippets?

In this case the Midgard MVC unit test setup might be possible to adapt to your use: http://trac.midgard-project.org/browser/trunk/midgardmvc/tests (note: this code uses Midgard2, so quite a few changes needed to work with 1.8)

Piotras

/Bergie

-- Henri Bergius Motorcycle Adventures and Free Software http://bergie.iki.fi/

Skype: henribergius Jabber: henri.bergius@gmail.com Microblog: http://www.qaiku.com/home/bergie/

user mailing list user@lists.midgard-project.org http://lists.midgard-project.org/mailman/listinfo/user

Re: [midgard-user] Midgard and PhPUnit

Piotr Pokora — Fri, 18 Jun 2010 09:25:04 +0000

Hi!

Our application is an internal application used by thousands of users to manage client environments...

Good to hear Midgard feels well in large setups :) BTW, there's OpenPSA2 CRM: http://www.openpsa2.org. It's not officially announced, but it's used by companies like HP or Lufthansa.

We are using midgard-core-1.8.9.2-1.x86_64.rpm ... I must admit I'm new to this project and don't master everything yet ... The problem I saw when trying to put in place PHPUnit is due to Midgard Page construction ... In fact, from what I understand, Midgard allows to build a page by replacing references to other elements by their contents (http://www.midgard-project.org/documentation/concepts-page_and_style/) ... Because PHPUnit directly call a given element, for sure we will miss references to other elements ...

Yeah, elements are kept in memory, so no single file is involved here. I wonder if you could try with cache files, usually stored in /var/cache/midgard.

Convention to file naming is: host_id-page_id-style_id-lang. Those files should contain midgard-root.php file "extracted".

Piotras

user mailing list user@lists.midgard-project.org http://lists.midgard-project.org/mailman/listinfo/user

Re: [midgard-user] Midgard and PhPUnit

Bouteille, Pierre-marie — Fri, 18 Jun 2010 09:05:05 +0000

Hi Henri,

Thanks for your answer ...

Our application is an internal application used by thousands of users to manage client environments ... It's a kind of placeholder to share client environment knowledge (data, documents, contacts, ...) with some more functionalities (read/write access, wiki, ...). It's now an 8 years old application that really help people to collaborate to solve/manage our clients...

I come back to my problem. We are using midgard-core-1.8.9.2-1.x86_64.rpm ... I must admit I'm new to this project and don't master everything yet ... The problem I saw when trying to put in place PHPUnit is due to Midgard Page construction ... In fact, from what I understand, Midgard allows to build a page by replacing references to other elements by their contents (http://www.midgard-project.org/documentation/concepts-page_and_style/) ... Because PHPUnit directly call a given element, for sure we will miss references to other elements ...

What you're pointed to me seems more PHPUnit of MidCOM itself but not PHPUnit of an application using Midgard ... We really wonder how to do ? ... What's the right approach ? ... and definitely need some help, some guidance on this topic ... so we really appreciate if you could help us ?

Regards Pierre-Marie

-----Original Message----- From: henri.bergius@gmail.com [mailto:henri.bergius@gmail.com] On Behalf Of Henri Bergius Sent: Wednesday, June 16, 2010 4:29 PM To: Midgard user list Cc: Bouteille, Pierre-marie Subject: Re: [midgard-user] Midgard and PhPUnit

Hi!

On Wed, Jun 16, 2010 at 1:17 PM, Bouteille, Pierre-marie Pierre-Marie.Bouteille@hp.com wrote:

We need to use PHPUnit to perform unit test of our application that is using Midgard.

Basically we are facing problem due to file inclusion ... Midgard manages inclusion through midgard-root.php but when using PHPUnit we directly call method ...

I assume the application is using Midgard1 (versions up until Midgard 8.09 "Ragnaroek"). In Midgard2 we have a PHPunit test environment bundled with the system, but with Midgard1 it is unfortunately a bit trickier.

Tarjei Huse was working on a unit testing environment for MidCOM in http://trac.midgard-project.org/browser/branches/thor/midcom/midcom.tests.base which might be possible to bring back to life.

BTW, would be interesting to hear a bit more about your Midgard application :-)

Pierre-Marie

/Henri

-- Henri Bergius Motorcycle Adventures and Free Software http://bergie.iki.fi/

Skype: henribergius Jabber: henri.bergius@gmail.com Microblog: http://www.qaiku.com/home/bergie/

user mailing list user@lists.midgard-project.org http://lists.midgard-project.org/mailman/listinfo/user

Re: [midgard-user] Midgard and PhPUnit

Henri Bergius — Wed, 16 Jun 2010 14:35:03 +0000

Hi!

On Wed, Jun 16, 2010 at 1:17 PM, Bouteille, Pierre-marie Pierre-Marie.Bouteille@hp.com wrote:

We need to use PHPUnit to perform unit test of our application that is using Midgard.

Basically we are facing problem due to file inclusion Midgard manages inclusion through midgard-root.php but when using PHPUnit we directly call method

Tarjei Huse was working on a unit testing environment for MidCOM in http://trac.midgard-project.org/browser/branches/thor/midcom/midcom.tests.base which might be possible to bring back to life.

BTW, would be interesting to hear a bit more about your Midgard application :-)

Pierre-Marie

/Henri

-- Henri Bergius Motorcycle Adventures and Free Software http://bergie.iki.fi/

Skype: henribergius Jabber: henri.bergius@gmail.com Microblog: http://www.qaiku.com/home/bergie/

user mailing list user@lists.midgard-project.org http://lists.midgard-project.org/mailman/listinfo/user

Midgard and PhPUnit

Bouteille, Pierre-marie — Wed, 16 Jun 2010 14:25:06 +0000

Hi all,

We need to use PHPUnit to perform unit test of our application that is using Midgard. Basically we are facing problem due to file inclusion ... Midgard manages inclusion through midgard-root.php but when using PHPUnit we directly call method ...

Is there anyone that can provide us some hints on how to do ? Is there a document somewhere explaining how to do ?

Any help would be appreciable ...

Regards Pierre-Marie

user mailing list user@lists.midgard-project.org http://lists.midgard-project.org/mailman/listinfo/user