http://blog.gmane.org/gmane.comp.cms.magnolia.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34603 <pre> [ http://jira.magnolia-cms.com/browse/MAGNOLIA-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MAGNOLIA-4380: -------------------------------------- Summary: magnolia-empty-webapp should provide dependency on magnolia-templating-jsp and compatibility jars (was: magnolia-empty-webapp should provide dependency on magnolia-templating-jsp) Description: As both CE and EE webapps depend on m-empty-webapp and as Magnolia aims at providing JSP support out of the box, it makes sense to add m-templating-jsp dependency to the m-empty-webapp module. We also want to provide compatibility jars directly in the magnolia-empty-webapp rather than provide them as an add-on or as separate downloads. Furthermore, m-templating-samples should use scope {{provided}} so that the add-ons folder in the bundles does not contain a useless duplicate of m-templating-jsp jar (was: As both CE and EE webapps depend on m-empty-webapp and as Magnolia aims at providing JSP support out of the box, it makes sense to add m-templating-jsp dependency to the m-empty-webapp module. Furthermore, m-templating-samples should use scope {{provided}} so that the add-ons folder in the bundles does not contain a useless duplicate of m-templating-jsp jar) </pre> JIRA (on behalf of Federico Grilli 2012-05-23T16:56:06 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34602 <pre> [ http://jira.magnolia-cms.com/browse/MAGNOLIA-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MAGNOLIA-4380: -------------------------------------- Priority: Neutral (was: Critical) </pre> JIRA (on behalf of Federico Grilli 2012-05-23T16:50:06 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34601 <pre>Hi everyone, I recently filed a bug: http://jira.magnolia-cms.com/browse/MAGNOLIA-4415 which was closed as "Not an Issue". However, Jan encouraged me to post this issue to the user list for discussion, which I am now doing. The error I posted was this: When activating, magnolia activates the content "as is", and then sets the "lastAction" metadata field on the author instance after activation. This means that the values of the "lastAction" metadata field differ between author and public instances, with the public instance always trailing "one activation behind" the author instance with respect to the "lastAction" field. We noticed this error because we use the "lastAction" field to implement sorting by publication date, and were getting different sort-order on author and public instances. Jan has proposed 2 solutions, which will work for us, but IMHO they are more workarounds than final solutions. Jan writes: "lastAction date in meta data is value meant for Magnolia internal use only and is used on author instance to keep track of performed activations" è In this case my contention is that it would be extremely useful to have a "publication-date" field that is automatically set by magnolia Jan writes: "If you want to sort content by the date I would suggest to use custom property for such values rather than value that is meant to be for internal use by activation." è In other areas of the site we do exactly this. However, this requires that the editor manually set and update the property. Sometimes this is what is wanted. Other times, this is NOT wanted, i.e. it is not desired to give the editor this control (and the opportunity to introduce errors), the content *should* be ordered by actual publication date. The solutions offered, namely using a modified ReceiveFilter or the observation module to set the lastAction field automatically on the public instances will work for us, but I consider it a workaround for the following reasons: - This still means content will differ between author and public instances. - In addition, it means content will also differ between our 2 public instances, since it can't be guaranteed that the activation will occur at the same time on both nodes. I'm wondering if anyone else had this problem, and what your solution was? Is there any way to solve this satisfactorily? Between multiple subscribers, transactional activation, versioning, workflow-activation with delays, etc... this is actually quite a tricky problem. Might it be a solution to set the lastAction field before activation, instead of afterwards? Failure to activate would leave the lastAction value "incorrect" on the author system in this case... Does anyone have any other ideas how this could be better solved? Thanks! Regards from Vienna, Richard ---------------------------------------------------------------- For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: &lt;dev-list-unsubscribe&lt; at &gt;magnolia-cms.com&gt; ---------------------------------------------------------------- </pre> Unger, Richard 2012-05-23T14:24:58 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34600 <pre> [ http://jira.magnolia-cms.com/browse/MGNLDMS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka updated MGNLDMS-231: -------------------------------- Fix Version/s: 1.6.x (was: 1.6.2) </pre> JIRA (on behalf of Jan Haderka 2012-05-23T10:26:06 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34599 <pre> [ http://jira.magnolia-cms.com/browse/MGNLSTK-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka updated MGNLSTK-953: -------------------------------- Fix Version/s: 2.0.4 (was: 2.0.3) </pre> JIRA (on behalf of Jan Haderka 2012-05-23T10:20:06 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34598 <pre> [ http://jira.magnolia-cms.com/browse/MAGNOLIA-3571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka updated MAGNOLIA-3571: ---------------------------------- Priority: Critical (was: Neutral) Setting priority to critical to make sure we do not release w/o fix. Reset to neutral once done. </pre> JIRA (on behalf of Jan Haderka 2012-05-23T10:08:08 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34597 <pre> [ http://jira.magnolia-cms.com/browse/MAGNOLIA-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka updated MAGNOLIA-4380: ---------------------------------- Priority: Critical (was: Neutral) Change priority to critical to make sure this is solved before release. Reset to neutral once done. </pre> JIRA (on behalf of Jan Haderka 2012-05-23T10:08:08 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34596 <pre> [ http://jira.magnolia-cms.com/browse/MAGNOLIA-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Šiška updated MAGNOLIA-4418: ----------------------------------- Summary: Integration tests webapp doesn't provide correct path to the keypair file. (was: Keypair updating function uses relative paths) Description: Integration tests webapp doesn't provide correct path to the keypair file, which renders the activation impossible. Note: perhaps the path in WEB-INF/config/default/keypair.properties should be valid even without ${magnolia.app.rootdir} as a prefix. was: On some deployments (Jetty in integration tests, for example), the SystemProperty.getProperty() returns relative path resulting in SecurityUtil.updateKeys() saving into the wrong location. SecurityUtil.updateKeys() should convert the path to the absolute path before saving. </pre> JIRA (on behalf of Robert Šiška 2012-05-23T08:32:06 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34595 <pre> [ http://jira.magnolia-cms.com/browse/MGNLSTK-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MGNLSTK-957: ---------------------------------- Assignee: (was: Philipp Bärfuss) Fix Version/s: 2.0.4 Thanks for reporting the issue Frank. </pre> JIRA (on behalf of Ondřej Chytil 2012-05-22T14:32:06 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34594 <pre>Keypair updating function uses relative paths --------------------------------------------- Key: MAGNOLIA-4418 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4418 Project: Magnolia Issue Type: Bug Security Level: Public Affects Versions: 4.5 Reporter: Robert Šiška Assignee: Robert Šiška Fix For: 4.5.3 On some deployments (Jetty in integration tests, for example), the SystemProperty.getProperty() returns relative path resulting in SecurityUtil.updateKeys() saving into the wrong location. SecurityUtil.updateKeys() should convert the path to the absolute path before saving. </pre> JIRA (on behalf of Robert Šiška 2012-05-22T14:08:07 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34593 <pre>Internal link component throws freemarker exception if target is not available ------------------------------------------------------------------------------ Key: MGNLSTK-957 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-957 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: demoproject Affects Versions: 2.0.2 Reporter: Frank Sommer Assignee: Philipp Bärfuss Tested on demoauthor instance. Try to reference a not existing page in a internal link component and a freemarker stack trace will occure. {{stkFunctions.getReferencedContent(content, "link", RepositoryConstants.WEBSITE)}} throws an uncatched runtime exception. </pre> JIRA (on behalf of Frank Sommer 2012-05-22T13:14:08 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34592 <pre>Glossary model can not add letter sub pages ------------------------------------------- Key: MGNLSTK-956 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-956 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: demoproject Affects Versions: 2.0.2 Reporter: Frank Sommer Assignee: Philipp Bärfuss The mode of the glossary info.magnolia.module.templatingkit.templates.GlossaryTemplateModel throws an exception, if a letter sub page is not available. The model can not add the letter node automatically. I tested it successfully on the demo author instance. </pre> JIRA (on behalf of Frank Sommer 2012-05-22T13:08:06 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34591 <pre>Update Maven site layouts ------------------------- Key: BUILD-107 URL: http://jira.magnolia-cms.com/browse/BUILD-107 Project: Build Issue Type: Improvement Security Level: Public Components: poms Reporter: Grégory Joseph Assignee: Grégory Joseph Fix For: POMs24 * use common header (see http://dev.magnolia-cms.com) * use current slogan "yes, we're open" </pre> JIRA (on behalf of Grégory Joseph 2012-05-22T12:38:06 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34590 <pre> [ http://jira.magnolia-cms.com/browse/BUILD-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grégory Joseph updated BUILD-105: --------------------------------- Description: The branch name is not resolved: http://jira.codehaus.org/browse/MBUILDNUM-87 (upgrading to 1.1 does not help) Revision number works, so we can derive the branch from that, but it's just silly. There are workarounds or alternatives, but unless pressing, I'd rather wait for this to be implemented in the "official" plugin. * http://stackoverflow.com/questions/2685069/maven-buildnumber-plugin-git * https://github.com/alx3apps/jgit-buildnumber was: The branch name is not resolved: http://jira.codehaus.org/browse/MBUILDNUM-87 (upgrading to 1.1 does not help) Revision number works, so we can derive the branch from that, but it's just silly. There are workarounds, and even a fork of the plugin, but unless pressing, I'd rather wait for this to be implemented in the "official" plugin. http://stackoverflow.com/questions/2685069/maven-buildnumber-plugin-git </pre> JIRA (on behalf of Grégory Joseph 2012-05-22T11:32:06 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34589 <pre> [ http://jira.magnolia-cms.com/browse/BUILD-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grégory Joseph updated BUILD-105: --------------------------------- Description: The branch name is not resolved: http://jira.codehaus.org/browse/MBUILDNUM-87 (upgrading to 1.1 does not help) Revision number works, so we can derive the branch from that, but it's just silly. There are workarounds, and even a fork of the plugin, but unless pressing, I'd rather wait for this to be implemented in the "official" plugin. http://stackoverflow.com/questions/2685069/maven-buildnumber-plugin-git was: The branch name is not resolved: http://jira.codehaus.org/browse/MBUILDNUM-87 (upgrading to 1.1 does not help) Revision number works, so we can derive the branch from that, but it's just silly. </pre> JIRA (on behalf of Grégory Joseph 2012-05-22T11:20:06 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34588 <pre>buildnumber plugin's support for Git is half-baked -------------------------------------------------- Key: BUILD-105 URL: http://jira.magnolia-cms.com/browse/BUILD-105 Project: Build Issue Type: Bug Components: poms Reporter: Grégory Joseph Assignee: Grégory Joseph Priority: Major Fix For: POMs24 The branch name is not resolved: http://jira.codehaus.org/browse/MBUILDNUM-87 (upgrading to 1.1 does not help) Revision number works, so we can derive the branch from that, but it's just silly. </pre> JIRA (on behalf of Grégory Joseph 2012-05-22T11:20:06 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34587 <pre>Impossible to edit an Event Overview component ---------------------------------------------- Key: MGNLSTK-955 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-955 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: paragraphs Affects Versions: 2.0.x Reporter: Samuel Schmitt Priority: Critical Fix For: 2.0.3 Attachments: Screen Shot 2012-05-22 at 9.48.09 AM.png Open this page http://demoauthor.magnolia-cms.com/demo-project/news-and-events/events-overview.html and try to edit the Event Overview component. The "next/prev month" links are hover the button of the edit bar... so no way to click on the edit bar buttons. </pre> JIRA (on behalf of Samuel Schmitt 2012-05-22T07:56:06 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34586 <pre> [ http://jira.magnolia-cms.com/browse/MGNLFORM-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marvin Kerkhoff updated MGNLFORM-123: ------------------------------------- Attachment: formSelection.ftl Here is the Right Template for that. I also add the possibility to add optgroups in a select element. Like in this Case: Main Countries{ Schweiz:Schweiz| Deutschland:Deutschland| Österreich:Österreich } Other Countries { Afghanistan:Afghanistan| Ägypten:Ägypten| Albanien:Albanien| Algerien:Algerien| Amerikanisch-Samoa:Amerikanisch-Samoa| Andorra:Andorra| Angola:Angola| Anguilla:Anguilla| Antarctica:Antarctica| Antigua und Barbuda:Antigua und Barbuda| Äquatorial-Guinea:Äquatorial-Guinea| Argentinien:Argentinien| Armenien:Armenien| Aruba:Aruba| Aserbaidshan:Aserbaidshan| Ashmore und Cartier Islands:Ashmore und Cartier Islands| Äthiopien:Äthiopien| Australien:Australien| Bahamas:Bahamas| Bahrain:Bahrain| Bangladesh:Bangladesh| Barbados:Barbados| Belarus:Belarus| Belgien:Belgien| Belize:Belize| Benin:Benin| Bermuda:Bermuda| Bhutan:Bhutan| Bolivien:Bolivien| Bosnien-Herzegowina:Bosnien-Herzegowina| Botswana:Botswana| Bouvet Island:Bouvet Island| Brasilien:Brasilien| British Indian Ocean Territory:British Indian Ocean Territory| British Virgin Islands:British Virgin Islands| Brunei:Brunei| Bulgarien:Bulgarien| Burkina Faso:Burkina Faso| Burundi:Burundi| Cayman Islands:Cayman Islands| Chile:Chile| China:China| Christmas Island:Christmas Island| Cocos (Keeling) Islands:Cocos (Keeling) Islands| Comoros:Comoros| Cook Islands:Cook Islands| Costa Rica:Costa Rica| Dänemark:Dänemark| Demokratische Republik Kongo:Demokratische Republik Kongo| Djibouti:Djibouti| Dominica:Dominica| Dominikanische Republik:Dominikanische Republik| Ekuador:Ekuador| El Salvador:El Salvador| Elfenbeinküste:Elfenbeinküste| England:England| Eritrea:Eritrea| Estland:Estland| Falkland Inseln (Malvinas):Falkland Inseln (Malvinas)| Faroer Inseln:Faroer Inseln| Fiji:Fiji| Finnland:Finnland| Frankreich:Frankreich| Französisch-Guyana:Französisch-Guyana| Französisch-Polynesien:Französisch-Polynesien| French Southern and Antarctic Lands:French Southern and Antarctic Lands| Gabun:Gabun| Gambia:Gambia| Georgien:Georgien| Ghana:Ghana| Gibraltar:Gibraltar| Grenada:Grenada| Griechenland:Griechenland| Grönland:Grönland| Guadeloupe:Guadeloupe| Guam:Guam| Guatemala:Guatemala| Guinea:Guinea| Guinea-Bissau:Guinea-Bissau| Guyana:Guyana| Haiti:Haiti| Heard Island und McDonald Islands:Heard Island und McDonald Islands| Honduras:Honduras| Hong Kong, SAR:Hong Kong, SAR| Indien:Indien| Indonesien:Indonesien| Irak:Irak| Iran:Iran| Irland:Irland| Island:Island| Israel:Israel| Italien:Italien| Jamaika:Jamaika| Japan:Japan| Jordanien:Jordanien| Jugoslawien:Jugoslawien| Kambodscha:Kambodscha| Kamerun:Kamerun| Kanada:Kanada| Kap Verde:Kap Verde| Kasachstan:Kasachstan| Katar:Katar| Kenia:Kenia| Kirgistan:Kirgistan| Kiribati:Kiribati| Kolumbien:Kolumbien| Kongo:Kongo| Kroatien:Kroatien| Kuba:Kuba| Kuwait:Kuwait| Laos:Laos| Lesotho:Lesotho| Libanon:Libanon| Liberia:Liberia| Liechtenstein:Liechtenstein| Litauen:Litauen| Litauen:Litauen| Luxemburg:Luxemburg| Lybien:Lybien| Macau:Macau| Madagaskar:Madagaskar| Malawi:Malawi| Malaysia:Malaysia| Malediven:Malediven| Mali:Mali| Malta:Malta| Marokko:Marokko| Marshall-Inseln:Marshall-Inseln| Martinique:Martinique| Mauritanien:Mauritanien| Mauritius:Mauritius| Mayotte:Mayotte| Mazedonien:Mazedonien| Mexiko:Mexiko| Mikronesien:Mikronesien| Moldavien:Moldavien| Monaco:Monaco| Mongolei:Mongolei| Montenegro:Montenegro| Montserrat:Montserrat| Mozambique:Mozambique| Myanmar:Myanmar| Namibia:Namibia| Nauru:Nauru| Nepal:Nepal| Neukaledonien:Neukaledonien| Neuseeland:Neuseeland| Nicaragua:Nicaragua| Niederlande:Niederlande| Niederländische Antillen:Niederländische Antillen| Niger:Niger| Nigeria:Nigeria| Niue:Niue| Nord-Korea:Nord-Korea| Norfolk Island:Norfolk Island| Northern Mariana Islands:Northern Mariana Islands| Norwegen:Norwegen| Oman:Oman| Pakistan:Pakistan| Palau:Palau| Panama:Panama| Papua-Neuguinea:Papua-Neuguinea| Paraguay:Paraguay| Peru:Peru| Philippinen:Philippinen| Pitcairn Islands:Pitcairn Islands| Polen:Polen| Portugal:Portugal| Puerto Rico:Puerto Rico| Reunion:Reunion| Ruanda:Ruanda| Rumänien:Rumänien| Russland:Russland| Saint Helena:Saint Helena| Saint Kitts und Nevis:Saint Kitts und Nevis| Saint Lucia:Saint Lucia| Saint Pierre und Miquelon:Saint Pierre und Miquelon| Saint Vincent and the Grenadines:Saint Vincent and the Grenadines| Sambia:Sambia| San Marino:San Marino| Sao Tome und Principe:Sao Tome und Principe| Saudi-Arabien:Saudi-Arabien| Schweden:Schweden| Senegal:Senegal| Serbia:Serbia| Seychellen:Seychellen| Sierra Leone:Sierra Leone| Simbabwe:Simbabwe| Singapur:Singapur| Slowakei:Slowakei| Slowenien:Slowenien| Solomon Islands:Solomon Islands| Somalia:Somalia| Spanien:Spanien| Sri Lanka:Sri Lanka| Südafrika:Südafrika| Sudan:Sudan| Südgeorgien:Südgeorgien| Süd-Korea:Süd-Korea| Surinam:Surinam| Svalbard:Svalbard| Swaziland:Swaziland| Syrien:Syrien| Tadschikistan:Tadschikistan| Taiwan:Taiwan| Tansania:Tansania| Thailand:Thailand| Togo:Togo| Tokelau:Tokelau| Tonga:Tonga| Trinidad und Tobago:Trinidad und Tobago| Tschad:Tschad| Tschechien:Tschechien| Tunesien:Tunesien| Türkei:Türkei| Turkmenistan:Turkmenistan| Turks and Caicos Islands:Turks and Caicos Islands| Tuvalu:Tuvalu| Uganda:Uganda| Ukraine:Ukraine| Ungarn:Ungarn| United States Minor Outlying Islands:United States Minor Outlying Islands| Uruguay:Uruguay| USA:USA| Usbekistan:Usbekistan| Vanuatu:Vanuatu| Vatikanstaat:Vatikanstaat| Venezuela:Venezuela| Vereinigte Arabische Emirate:Vereinigte Arabische Emirate| Vietnam:Vietnam| Virgin Islands, U.S.:Virgin Islands, U.S.| Wallis und Futuna:Wallis und Futuna| Western Sahara:Western Sahara| Yemen:Yemen| Zaire:Zaire| Zypern:Zypern} </pre> JIRA (on behalf of Marvin Kerkhoff 2012-05-22T06:44:06 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34585 <pre> [ http://jira.magnolia-cms.com/browse/MAGNOLIA-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MAGNOLIA-4411: -------------------------------------- Attachment: mainbarontop-IMPROVED.png </pre> JIRA (on behalf of Federico Grilli 2012-05-21T15:32:08 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34584 <pre>Hi everyone, is it possible to configure the ContentSecurity Filter Callback so that it returns instead of the magnolia-login form a 403 Http Error? Thanks and best regards Dominik </pre> Dominik Berger (via Magnolia Forums 2012-05-21T14:58:42 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34583 <pre>Hi Jan, Thanks for the answer. That's fine for us, since we aren't using any of the filters, I will just remove that JAR to solve my conflict. Regards from Vienna, Richard Von: dev-list-owner&lt; at &gt;magnolia-cms.com [mailto:dev-list-owner&lt; at &gt;magnolia-cms.com] Im Auftrag von Jan Haderka Gesendet: Montag, 21. Mai 2012 15:21 An: Magnolia Dev-List Betreff: Re: [magnolia-dev] filters-2.0.235.jar - is it necessary? jar is there to allow you define and use image operations contained in the jar. The amount of ops there is quite big and should cover needs of most users. OTOH, if you don't use any custom image ops and don't use any modules that might define such ops (which should declare dependency in their pom), you are free to remove it. HTH, Jan On May 21, 2012, at 2:48 PM, Unger, Richard wrote: Hello Magnolia Developers, Magnolia 4.4.6 EE Bundle contains the JAR "filters-2.0.235.jar". This contains image and math classes from com.jhlabs. However, a quick search through the magnolia code shows that the import "jhlabs" is used only in the imaging module test-classes. My Question: - Is it safe to remove the JAR "filters-2.0.235.jar" ? - Did I miss something? Is this JAR used by some other module? - Could you remove JARs needed only for testing from the official bundle releases? That would make the releases more compact, and help to minimize class conflict type errors. Background info: I have a conflict with the jcaptcha library, which also includes the jhlabs classes. I'm trying to serve captchas from Magnolia, and have rewritten the magnoliacaptcha module to work with our version. Thanks &amp; regards from Vienna, Richard ________________________________ ---------------------------------------------------------------- For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: &lt;dev-list-unsubscribe&lt; at &gt;magnolia-cms.com&lt;mailto:dev-list-unsubscribe&lt; at &gt;magnolia-cms.com&gt;&gt; ---------------------------------------------------------------- ________________________________ ---------------------------------------------------------------- For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: &lt;dev-list-unsubscribe&lt; at &gt;magnolia-cms.com&lt;mailto:dev-list-unsubscribe&lt; at &gt;magnolia-cms.com&gt;&gt; ---------------------------------------------------------------- ---------------------------------------------------------------- For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: &lt;dev-list-unsubscribe&lt; at &gt;magnolia-cms.com&gt; ---------------------------------------------------------------- </pre> Unger, Richard 2012-05-21T14:15:13 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.cms.magnolia.devel