User forum

Binary packages for Midgard 8.09 "Ragnaroek"

Piotr Pokora — Sun, 12 Oct 2008 19:41:57 +0000

Hi!

Binary packages for many distros are ready for downloads.

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

Debian users have special m-p.org mirror, which is apt-get friendly: http://www.midgard-project.org/documentation/installation-distros-debian/

Piotras

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

Announcement: Midgard 8.09.0 "Ragnaroek" released!

Piotr Pokora — Tue, 07 Oct 2008 12:30:01 +0000

Lodz, October 7th 2008 -- The Midgard Project has released stable release of 8.09 "Ragnaroek LTS" generation of the Midgard Content Management System. Midgard is a mature Free Software CMS package targeted for mid-to-high-end web services.

About this release.

Midgard 8.09.0 "Ragnaroek LTS" release is another release of Midgard following the new time-based release process. Because of this, versioning numbering of both Midgard and MidCOM have been synchronized to follow a date-based pattern. Using old version numbering the software included in this release would have been Midgard 1.9 and MidCOM 2.9. The new release process has been created to align Midgard with the release synchronicity model followed by free software projects like GNOME and Ubuntu.

Midgard 8.09.0 "Ragnaroek LTS" is a Long Term Support version of Midgard for which bug fixes and minor feature improvements will be supplied by the Midgard community for several years. It is recommended that all Midgard users upgrade their installations to the Midgard 8.09 series for stability, performance and maintainance reasons. Upgrade from MidCOM 2.8 installations running with PHP5 has been made as seamless as possible.

The version is targeted to ease transition from web services using the deprecated Midgard 1.x APIs to the new Midgard2 architecture. Because of this, the release provides both API versions. This means that the release can be used to run both Midgard 1 applications like the version 2.9 of the MidCOM component framework, and Midgard2 applications like MidCOM3.

Changes from Midgard 1.8 and MidCOM 2.8:

Midgard and MidCOM now follow an unified release schedule and roadmap
There is a new command-line database and website setup utility
There is a new Site Wizard web interface for website creation
PHP4 support has been removed in favor of PHP5
GObject attributes of Midgard objects are directly mapped to PHP objects for performance reasons
Repligard package has been removed and replaced by new built in replication API
The MidCOM framework uses autoloading to reduce memory usage and processing time
Prototype Javascript framework has been removed in favor of jQuery
New Midgard logo and graphical guidelines have been deployed across the system
Packages are built for several Linux distributions using the openSuse Build Service
Classic Midgard API has been deprecated in favor of MgdSchema and Query Builder, but is available via --with-legacy-api configuration switch in midgard-php5
midgard-config command-line tool replaced with Midgard configuration supported by pkg-config

In addition Midgard 8.09 provides new experimental ("Midgard2") features for developers:

D-Bus signals from I/O events, and ability to pass D-Bus messages through Midgard API
Event handling also available for languages without event support (like PHP5)
New authentication and user management API
New API for objects' attachments and parameters
New API for binary blobs

Planned for next releases

Long Term Supported Midgard 8.09 "Ragnaroek" version
First Midgard 9.03 ("Midgard2") stable release: March 2009
- Targeted as general, replicated persistent storage framework reaching further than just the web
- Automated database MgdSchema management and table initialization
- Language bindings for Python and Mono (.Net)
- Support for different database back-ends like PostgreSQL, SQLite, Oracle and MS SQL
- Completely rewritten high-performance MidCOM model-view-controller framework for PHP ("MidCOM3")
- XMPP Peer-to-Peer replication
- Removed Apache module
- Redesigned and web server independent PHP extension (Apache and Lighttpd support)
- Development coordinated via Git instead of Subversion

About Midgard Midgard is a capable open source content management package targeted for mid-to-high-end websites. The Midgard community has always focused on clean and manageable code, high security and multilingual support in the toolkit.

Some feature highlights:

Modular system that allows construction of a site by creating a directory hierarchy powered by different components
Powerful templating of all output in the system
Highly configurable content entry views
Full caching of generated pages and uploaded file attachments
"Double click to edit" on-site WYSIWYG editing
Comprehensive access controls
Content replication for clustered setups and staging/live publishing
Hosting multiple sites and organizations within one Midgard installation
Full-text search powered by SOLR

The components available for Midgard provide functionality ranging from typical content-oriented websites to highly personalized web services supporting features like geographical positioning and recommendation mining. Several Midgard components include integration features for synchronizing content from popular Social Web services like Flickr, Jaiku and Twitter.

Midgard includes:

System library for persistent storage, replication and interprocess communication
Apache module for HTTP request mapping
PHP5 extension for object-oriented data handling API
MidCOM MVC framework for PHP5
Content management tools and user interfaces
Additional components that may be installed using the PEAR package management tool

Get started with Midgard today! Licensing

Midgard and MidCOM are available under the GNU Lesser General Public License (LGPL)
Some tools bundled in Midgard distribution are available under other open source licenses like GPL and Apache Software License

System requirements

Linux, Unix or any POSIX server
Apache 2.x HTTP server
GLib 2 C library
PHP 5.x programming language
MySQL 5.x database
APC or other PHP byte code cache recommended
1GB of RAM or more recommended (with MidCOM3 256MB is enough)

Find out more about Midgard

Midgard Community Since 1999, Midgard has been worked on by an international team of free software developers. Unlike many other open source CMS projects, Midgard is not controlled by a single corporation, but instead the development work is coordinated and shared by a cluster of organizations mainly located in north Europe. All decisions and development directions in the community are discussed openly, and the decisions are made in Midgard Gatherings - events that are arranged twice a year.

Midgard is a large and mature code base that is being actively developed. Copyrights to the Midgard software are owned by the community members. Contact the community

Mailing lists
- Users' forum
- Developers' forum
IRC: #midgard on irc.freenode.net
#Midgard on Jaiku

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

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

The Midgard Project website www.midgard-project.org

Announcement: Midgard 8.09.0RC2 "Ragnaroek" released!

Piotr Pokora — Thu, 02 Oct 2008 13:12:26 +0000

Lodz, October 2nd 2008 -- The Midgard Project has released second 'Release Canditate' release of 8.09 "Ragnaroek LTS" generation of the Midgard Content Management System. Midgard is a mature Free Software CMS package targeted for mid-to-high-end web services. About this release Midgard 8.09.0RC "Ragnaroek LTS" release is the fourth release of Midgard following the new time-based release process. Because of this, versioning numbering of both Midgard and MidCOM have been synchronized to follow a date-based pattern. Using old version numbering the software included in this release would have been Midgard 1.9 and MidCOM 2.9. The new release process has been created to align Midgard with the release synchronicity model followed by free software projects like GNOME and Ubuntu.

When finalized, the 8.09 "Ragnaroek LTS" will be a Long Term Support version of Midgard for which bug fixes and minor feature improvements will be supplied by the Midgard community for several years. It is recommended that all Midgard users upgrade their installations to the Midgard 8.09 series for stability, performance and maintainance reasons. Upgrade from MidCOM 2.8 installations running with PHP5 has been made as seamless as possible.

Changes from Midgard 1.8 and MidCOM 2.8:

Midgard and MidCOM now follow an unified release schedule and roadmap
There is a new command-line database and website setup utility
There is a new Site Wizard web interface for website creation
PHP4 support has been removed in favor of PHP5
GObject attributes of Midgard objects are directly mapped to PHP objects for performance reasons
Repligard package has been removed and replaced by new built in replication API
The MidCOM framework uses autoloading to reduce memory usage and processing time
Prototype Javascript framework has been removed in favor of jQuery
New Midgard logo and graphical guidelines have been deployed across the system
Packages are built for several Linux distributions using the openSuse Build Service
Classic Midgard API has been deprecated in favor of MgdSchema and Query Builder, but is available via --with-legacy-api configuration switch in midgard-php5
midgard-config command-line tool replaced with Midgard configuration supported by pkg-config

In addition Midgard 8.09 provides new experimental ("Midgard2") features for developers:

D-Bus signals from I/O events, and ability to pass D-Bus messages through Midgard API
Event handling also available for languages without event support (like PHP5)
New authentication and user management API
New API for objects' attachments and parameters
New API for binary blobs

Planned for next releases

First stable release of 8.09 ("Ragnaroek LTS"): October 6th, 2008
- Long Term Supported Midgard version
First Midgard 9.03 ("Midgard2") stable release: March 2009
- Targeted as general, replicated persistent storage framework reaching further than just the web
- Automated database MgdSchema management and table initialization
- Language bindings for Python and Mono (.Net)
- Support for different database back-ends like PostgreSQL, SQLite, Oracle and MS SQL
- Completely rewritten high-performance MidCOM model-view-controller framework for PHP ("MidCOM3")
- XMPP Peer-to-Peer replication
- Removed Apache module
- Redesigned and web server independent PHP extension (Apache and Lighttpd support)
- Development coordinated via Git instead of Subversion

Some feature highlights:

Modular system that allows construction of a site by creating a directory hierarchy powered by different components
Powerful templating of all output in the system
Highly configurable content entry views
Full caching of generated pages and uploaded file attachments
"Double click to edit" on-site WYSIWYG editing
Comprehensive access controls
Content replication for clustered setups and staging/live publishing
Hosting multiple sites and organizations within one Midgard installation
Full-text search powered by SOLR

Midgard includes:

System library for persistent storage, replication and interprocess communication
Apache module for HTTP request mapping
PHP5 extension for object-oriented data handling API
MidCOM MVC framework for PHP5
Content management tools and user interfaces
Additional components that may be installed using the PEAR package management tool

Get started with Midgard today! Licensing

Midgard and MidCOM are available under the GNU Lesser General Public License (LGPL)
Some tools bundled in Midgard distribution are available under other open source licenses like GPL and Apache Software License

System requirements

Linux, Unix or any POSIX server
Apache 2.x HTTP server
GLib 2 C library
PHP 5.x programming language
MySQL 5.x database
APC or other PHP byte code cache recommended
1GB of RAM or more recommended (with MidCOM3 256MB is enough)

Find out more about Midgard

Midgard is a large and mature code base that is being actively developed. Copyrights to the Midgard software are owned by the community members. Contact the community

Mailing lists
- Users' forum
- Developers' forum
IRC: #midgard on irc.freenode.net
#Midgard on Jaiku

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

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

The Midgard Project website www.midgard-project.org

Announcement: Midgard 8.09.0RC "Ragnaroek" released!

Piotr Pokora — Mon, 29 Sep 2008 12:10:28 +0000

Lodz, September 29th 2008 -- The Midgard Project has released first 'Release Canditate' release of 8.09 "Ragnaroek LTS" generation of the Midgard Content Management System. Midgard is a mature Free Software CMS package targeted for mid-to-high-end web services. About this release Midgard 8.09.0RC "Ragnaroek LTS" release is the third release of Midgard following the new time-based release process. Because of this, versioning numbering of both Midgard and MidCOM have been synchronized to follow a date-based pattern. Using old version numbering the software included in this release would have been Midgard 1.9 and MidCOM 2.9. The new release process has been created to align Midgard with the release synchronicity model followed by free software projects like GNOME and Ubuntu.

Changes from Midgard 1.8 and MidCOM 2.8:

Midgard and MidCOM now follow an unified release schedule and roadmap
There is a new command-line database and website setup utility
There is a new Site Wizard web interface for website creation
PHP4 support has been removed in favor of PHP5
GObject attributes of Midgard objects are directly mapped to PHP objects for performance reasons
Repligard package has been removed and replaced by new built in replication API
The MidCOM framework uses autoloading to reduce memory usage and processing time
Prototype Javascript framework has been removed in favor of jQuery
New Midgard logo and graphical guidelines have been deployed across the system
Packages are built for several Linux distributions using the openSuse Build Service
Classic Midgard API has been deprecated in favor of MgdSchema and Query Builder, but is available via --with-legacy-api configuration switch in midgard-php5
midgard-config command-line tool replaced with Midgard configuration supported by pkg-config

In addition Midgard 8.09 provides new experimental ("Midgard2") features for developers:

D-Bus signals from I/O events, and ability to pass D-Bus messages through Midgard API
Event handling also available for languages without event support (like PHP5)
New authentication and user management API
New API for objects' attachments and parameters
New API for binary blobs

Planned for next releases

First stable release of 8.09 ("Ragnaroek LTS"): October 6th, 2008
- Long Term Supported Midgard version
First Midgard 9.03 ("Midgard2") stable release: March 2009
- Targeted as general, replicated persistent storage framework reaching further than just the web
- Automated database MgdSchema management and table initialization
- Language bindings for Python and Mono (.Net)
- Support for different database back-ends like PostgreSQL, SQLite, Oracle and MS SQL
- Completely rewritten high-performance MidCOM model-view-controller framework for PHP ("MidCOM3")
- XMPP Peer-to-Peer replication
- Removed Apache module
- Redesigned and web server independent PHP extension (Apache and Lighttpd support)
- Development coordinated via Git instead of Subversion

Some feature highlights:

Modular system that allows construction of a site by creating a directory hierarchy powered by different components
Powerful templating of all output in the system
Highly configurable content entry views
Full caching of generated pages and uploaded file attachments
"Double click to edit" on-site WYSIWYG editing
Comprehensive access controls
Content replication for clustered setups and staging/live publishing
Hosting multiple sites and organizations within one Midgard installation
Full-text search powered by SOLR

Midgard includes:

System library for persistent storage, replication and interprocess communication
Apache module for HTTP request mapping
PHP5 extension for object-oriented data handling API
MidCOM MVC framework for PHP5
Content management tools and user interfaces
Additional components that may be installed using the PEAR package management tool

Get started with Midgard today! Licensing

Midgard and MidCOM are available under the GNU Lesser General Public License (LGPL)
Some tools bundled in Midgard distribution are available under other open source licenses like GPL and Apache Software License

System requirements

Linux, Unix or any POSIX server
Apache 2.x HTTP server
GLib 2 C library
PHP 5.x programming language
MySQL 5.x database
APC or other PHP byte code cache recommended
1GB of RAM or more recommended (with MidCOM3 256MB is enough)

Find out more about Midgard

Midgard is a large and mature code base that is being actively developed. Copyrights to the Midgard software are owned by the community members. Contact the community

Mailing lists
- Users' forum
- Developers' forum
IRC: #midgard on irc.freenode.net
#Midgard on Jaiku

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

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

The Midgard Project website www.midgard-project.org

heads-up! potentially breaking change in branch-28

eero.afheurlin@iki.fi — Fri, 26 Sep 2008 11:10:09 +0000

-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160

cross-posting for maximum awareness, discussion should be held on dev-list.

Actually the likelyhood of problems is very, very small. BUT you have setup where HTML-files are served as attachments via /path/to/topic/attachment.html then you need to change those to use the /midcom-serveattachmentguid- stanza.

From IRC he quoteth:

[1:40pm] mashiara: heads up people! Related to http://trac.midgard-project.org/ticket/47 a potentially breaking change in http://trac.midgard-project.org/changeset/17715 [1:41pm] mashiara: all components should be able to handle this gracefully but if you know your component has some weird functionality that depends on URI having .html then you should change your ways... [1:42pm] mashiara: this does not mean component authors should stay lazy removing those suffixes from the urls they give out [1:43pm] mashiara: since unneccessary 301 is still an unneccessary request and under SSL (especially under IE which behaves badly and thus one must always disable keep-alive in ssl if user-agent looks like IE) extra requests can be costly [1:47pm] bergie: mashiara: note that file attachments with .html suffix should remain valid [1:48pm] mashiara: midcom-somethign methods are unaffected [1:48pm] mashiara: for /path/to/folder/attachment.html we cannot know... [1:49pm] mashiara: and since in 99.99% (possibly even higher percentage) of cases it's not an attachment with .html suffix we just have to accept this [1:50pm] bergie: mashiara: I'm a bit uneasy about fixing this on redirection level by default [1:50pm] bergie: maybe a MidCOM config option? [1:51pm] mashiara: me too, however configs are not loaded yet, this is done at the earliest possible point to avoid wasting cycles [1:52pm] mashiara: however based on my hand-waving approximations likelyhood of issues in existing installations is very small [1:53pm] bergie: well... we may be shooting ourselves in the foot here [1:53pm] bergie: but lets try it [1:53pm] bergie: should be easy to revert anyway [1:54pm] mashiara: do you recall any setup where .html files are server as attachments ? [1:54pm] mashiara: does anyone recall any setup ? [1:55pm] mashiara: the next question is what percentage of these are served as /path/to/folder/attachment.html [1:56pm] bergie: mashiara: I remember some sites having .html files as attachments for some pop-ups etc [1:57pm] mashiara: but they're served via midcom-serveattchment [1:57pm] mashiara: which is unaffected [2:00pm] mashiara: the main point is that we can fix a potentially major issue (in-content links behaving differently based on how you happen to land on the page) without requiring co-operation (and duplicated code) from all components [2:01pm] mashiara: with introducing only one arbitary limitation that can be easily worked around [2:01pm] bergie: ok [2:03pm] mashiara: since the default behaviour for imagepopup etc co is to use midcom-serveattachment for attachment serving I'm fairly sure we have no issues from this -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFI3MMQi7iLtQbxbW8RA49oAKCTLQpnCDn/UDzEjXiI2q++JttEFgCbBQTq hczxNTRjsghyivfyCfRYV68= =aOLS -----END PGP SIGNATURE-----

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

Announcement: Midgard 8.09.0beta2 "Ragnaroek" released!

Piotr Pokora — Mon, 08 Sep 2008 18:02:39 +0000

Lodz, September 8th 2008 -- The Midgard Project has released second beta release of 8.09 "Ragnaroek LTS" generation of the Midgard Content Management System. Midgard is a mature Free Software CMS package targeted for mid-to-high-end web services. About this release Midgard 8.09.0beta2 "Ragnaroek LTS" beta release is the second release of Midgard following the new time-based release process. Because of this, versioning numbering of both Midgard and MidCOM have been synchronized to follow a date-based pattern. Using old version numbering the software included in this release would have been Midgard 1.9 and MidCOM 2.9. The new release process has been created to align Midgard with the release synchronicity model followed by free software projects like GNOME and Ubuntu.

Changes from Midgard 1.8 and MidCOM 2.8:

Midgard and MidCOM now follow an unified release schedule and roadmap
There is a new command-line database and website setup utility
There is a new Site Wizard web interface for website creation
PHP4 support has been removed in favor of PHP5
GObject attributes of Midgard objects are directly mapped to PHP objects for performance reasons
Repligard package has been removed and replaced by new built in replication API
The MidCOM framework uses autoloading to reduce memory usage and processing time
Prototype Javascript framework has been removed in favor of jQuery
New Midgard logo and graphical guidelines have been deployed across the system
Packages are built for several Linux distributions using the openSuse Build Service
Classic Midgard API has been deprecated in favor of MgdSchema and Query Builder, but is available via --with-legacy-api configuration switch in midgard-php5
midgard-config command-line tool replaced with Midgard configuration supported by pkg-config

In addition Midgard 8.09 provides new experimental ("Midgard2") features for developers:

D-Bus signals from I/O events, and ability to pass D-Bus messages through Midgard API
Event handling also available for languages without event support (like PHP5)
New authentication and user management API
New API for objects' attachments and parameters
New API for binary blobs

Planned for next releases

First stable release of 8.09 ("Ragnaroek LTS"): September 2008 o Long Term Supported Midgard version
First Midgard 9.03 ("Midgard2") stable release: March 2009 o Targeted as general, replicated persistent storage framework reaching further than just the web o Automated database MgdSchema management and table initialization o Language bindings for Python and Mono (.Net) o Support for different database back-ends like PostgreSQL, SQLite, Oracle and MS SQL o Completely rewritten high-performance MidCOM model-view-controller framework for PHP ("MidCOM3") o XMPP Peer-to-Peer replication o Removed Apache module o Redesigned and web server independent PHP extension (Apache and Lighttpd support) o Development coordinated via Git instead of Subversion

Some feature highlights:

Modular system that allows construction of a site by creating a directory hierarchy powered by different components
Powerful templating of all output in the system
Highly configurable content entry views
Full caching of generated pages and uploaded file attachments
"Double click to edit" on-site WYSIWYG editing
Comprehensive access controls
Content replication for clustered setups and staging/live publishing
Hosting multiple sites and organizations within one Midgard installation
Full-text search powered by SOLR

Midgard includes:

System library for persistent storage, replication and interprocess communication
Apache module for HTTP request mapping
PHP5 extension for object-oriented data handling API
MidCOM MVC framework for PHP5
Content management tools and user interfaces
Additional components that may be installed using the PEAR package management tool

Get started with Midgard today! Licensing

Midgard and MidCOM are available under the GNU Lesser General Public License (LGPL)
Some tools bundled in Midgard distribution are available under other open source licenses like GPL and Apache Software License

System requirements

Linux, Unix or any POSIX server
Apache 2.x HTTP server
GLib 2 C library
PHP 5.x programming language
MySQL 5.x database
APC or other PHP byte code cache recommended
1GB of RAM or more recommended (with MidCOM3 256MB is enough)

Find out more about Midgard

Midgard is a large and mature code base that is being actively developed. Copyrights to the Midgard software are owned by the community members. Contact the community

Mailing lists o Users' forum o Developers' forum
IRC: #midgard on irc.freenode.net
#Midgard on Jaiku

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

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

The Midgard Project website www.midgard-project.org

Re: [midgard-user] o.r.photostream exifrotate problem

eero.afheurlin@iki.fi — Sat, 30 Aug 2008 11:47:52 +0000

i.e. if I explicitly call exifrotate for the 'view' image, it gets rotated as well. But the auto_thumbnail still is in landscape mode and I don't know how to add a filter there. But wouldn't it make sense for the auto_thumbnail to inherit the filter_chain from the main image?

Ah I have forgotten how the ancient imagefilter works. Anyways auto_thumbnail is really stupid as it says on the api docs, it just inserts 'thumbnail' to derived images with the correct resize parameters.

as for filter chain inherits/derived images in general I have though about making it work so that the derived images are derived from the main not the original, which subtly different than inhereting the filter chain but both have same drawbacks for situations when one would want to use more exotic combination of filters.

Probably this thinking has led me to forget to make the schemadb_default to work correctly (ie insert the exifrotate on all chains and explicitly specify thumbnail as derived image).

/Rambo

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

Re: [midgard-user] o.r.photostream exifrotate problem

Andreas Flack — Sat, 30 Aug 2008 10:30:55 +0000

Eero af Heurlin schrieb:

Andreas Flack wrote:

Hi!

I'm playing with my new cellphone right now and am trying to upload some of it's pictures into a o.r.photostream topic. It all works relatively well, except for one problem: Pictures in landscape orientation work fine, but for pictures in portrait orientation, all derived images have the wrong orientation, i.e. the archival image is correctly displayed in portrait mode, but all derived images are displayed in landscape mode.

The EXIF data in the picture is wrong (blame cellphone). Take exifrotate out of the filter chains and always rotate manually as needed.

Funny hat the archival image gets rotated, it AFAIRecall should not be touched after upload.

Sorry, I was a bit confused there. I said archival image because I meant the image that is shown when you click the "archival" link on the view page. But the image shown when you click on the link is not the archival image, but the "main" one:

 * archival_img_0012.JPG: 1600x1200, 431.558 Byte
 * img_0012.JPG: 1200x1600, 429.955 Byte
 * thumbnail_img_0012.JPG: 113x150, 13.902 Byte
 * view_img_0012.JPG: 450x600, 72.713 Byte

The archival_img_0012.JPG file really doesn't change at all, it's the one called img_0012.JPG. So when I upload photos with exifrotate enabled, archival_img, thumbnail_img and view_img are in landscape mode, while img is in portrait mode.

This is the schema I use:

     'photo' => Array
     (
         'title' => 'photo',
         'type' => 'photo',
         'type_config' => Array
         (
             'filter_chain' => "exifrotate()"
             'auto_thumbnail' => Array(150,150),
             'derived_images' => array
             (
                 // Intentionally this way, so that portraits can be

taller 'view' => 'resize(600,700)', ), ), 'widget' => 'photo', ),

I tried removing exifrotate from the filter_chain. When I recreate all derived images afterwards, everything (except archival_img) is in landscape mode, so rotating now works.

I researched a bit and found out that according to API doc, filter_chain is supposed to work only on the main image, so the behavior I'm seeing would be explainable. In fact, when I change my schema to this:

     'photo' => Array
     (
         'title' => 'photo',
         'type' => 'photo',
         'type_config' => Array
         (
             'filter_chain' => 'exifrotate()',
             'auto_thumbnail' => Array(150,150),
             'derived_images' => array
             (
                 // Intentionally this way, so that portraits can be

taller 'view' => 'exifrotate();resize(600,700)', ), ), 'widget' => 'photo', ),

i.e. if I explicitly call exifrotate for the 'view' image, it gets rotated as well. But the auto_thumbnail still is in landscape mode and I don't know how to add a filter there. But wouldn't it make sense for the auto_thumbnail to inherit the filter_chain from the main image?

Bye,

Andreas

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

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

Re: [midgard-user] o.r.photostream exifrotate problem

eero.afheurlin@iki.fi — Sat, 30 Aug 2008 08:41:35 +0000

Andreas Flack wrote:

Hi!

I'm playing with my new cellphone right now and am trying to upload some of it's pictures into a o.r.photostream topic. It all works relatively well, except for one problem: Pictures in landscape orientation work fine, but for pictures in portrait orientation, all derived images have the wrong orientation, i.e. the archival image is correctly displayed in portrait mode, but all derived images are displayed in landscape mode.

The EXIF data in the picture is wrong (blame cellphone). Take exifrotate out of the filter chains and always rotate manually as needed.

Funny hat the archival image gets rotated, it AFAIRecall should not be touched after upload.

/Rambo

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

o.r.photostream exifrotate problem

Andreas Flack — Fri, 29 Aug 2008 16:24:31 +0000

Hi!

I'm playing with my new cellphone right now and am trying to upload some of it's pictures into a o.r.photostream topic. It all works relatively well, except for one problem: Pictures in landscape orientation work fine, but for pictures in portrait orientation, all derived images have the wrong orientation, i.e. the archival image is correctly displayed in portrait mode, but all derived images are displayed in landscape mode.

When I rotate one of the offending images, the derived images are correct, but then the archival image has the wrong orientation. Plus, when I select "recreate derived images", all rotation changes are reverted.

I looked a bit through the code, but I didn't see anything obvious. Does anybody else have this problem with uploads from digital cameras or is this somehow specific to my setup? Also, where would I start to look for the cause of this bug?

Bye,

Andreas

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