http://permalink.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/34554 <pre>Metadata - LastAction is not set correctly on public node after activation -------------------------------------------------------------------------- Key: MAGNOLIA-4415 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4415 Project: Magnolia Issue Type: Bug Security Level: Public Components: activation Affects Versions: 4.4.6 Environment: Magnolia EE 4.4.6, Linux, Sun JDK 6 Reporter: Richard Unger Assignee: Philipp Bärfuss You probably hate me by now, but here's another problem I found (my customers reported) to do with activation: When content is activated, the lastAction is set to the publication date on the author system. Unfortunately this seems to happen after the content is sent to public instance. The result is that the activated content on the public instance always has the "previous" value for the lastAction metadata field compared to the author system. Eg: Content is first published </pre> JIRA (on behalf of Richard Unger 2012-05-16T15:38:07 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34553 <pre> [ http://jira.magnolia-cms.com/browse/MAGNOLIA-4410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka updated MAGNOLIA-4410: ---------------------------------- Fix Version/s: 4.4.x (was: 4.4.8) </pre> JIRA (on behalf of Jan Haderka 2012-05-16T14:50:06 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34552 <pre>Class FormParagraph should be FormComponent ------------------------------------------- Key: MGNLFORM-128 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-128 Project: Magnolia Form Module Issue Type: Improvement Affects Versions: 1.4.1 Reporter: Christian Ringele Fix For: 1.4.2 The class info.magnolia.module.form.templates.components.FormParagraph should be renamed to info.magnolia.module.form.templates.components.FormComponent </pre> JIRA (on behalf of Christian Ringele 2012-05-16T11:31:43 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34551 <pre> [ http://jira.magnolia-cms.com/browse/MAGNOLIA-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MAGNOLIA-4413: ---------------------------------------- Description: Open in chrome (not logged in, needs to be server from the cache) the contact form: http://demopublic.magnolia-cms.com/demo-project/service/contact.html See the print screen. At the bottom strange binary content is rendered. Only in chrome, works in firefox and safari. 1. Disable the gzip filter, problem gone. 2 or: server the form not form cache by adding ?something to the url, problem gone. Seems its the combination that the cahche gzipes, and the gzip filter gzipes somehow also, or at least manipulates the http header wrong. was: Open in chrome (not logged in, needs to be server from the cache) th4e contact form: http://demopublic.magnolia-cms.com/.magnolia/pages/adminCentral.html See the print screen. At the bottom stange binary content is rendered. Only in chrome, works in </pre> JIRA (on behalf of Christian Ringele 2012-05-16T10:37:43 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34550 <pre> [ http://jira.magnolia-cms.com/browse/MAGNOLIA-4414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka updated MAGNOLIA-4414: ---------------------------------- Attachment: magnolia-4414.patch Patch for the issue. </pre> JIRA (on behalf of Jan Haderka 2012-05-16T09:49:43 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34549 <pre>Cleanup after unsuccessful attempt to lock the content will remove content in case of cross activation requests --------------------------------------------------------------------------------------------------------------- Key: MAGNOLIA-4414 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4414 Project: Magnolia Issue Type: Bug Security Level: Public Components: activation Affects Versions: 4.5.2, 4.4.7 Reporter: Jan Haderka Assignee: Philipp Bärfuss Priority: Blocker Fix For: 4.4.8, 4.5.3 In case of two concurrent requests for activation of same content arriving to public instances in different order block each other and cause rollback, the cleanup will incorrectly remove the content from all public instances. </pre> JIRA (on behalf of Jan Haderka 2012-05-16T09:43:43 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34548 <pre> [ http://jira.magnolia-cms.com/browse/MAGNOLIA-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka updated MAGNOLIA-4070: ---------------------------------- Summary: Cleanup existing unmaintainable STK tests (was: STK Tests: Set failing test to ignore, so module is compiled again by hudson. This should be changed back, as soon we have a first basic proper STK rendering.) Assignee: Ondřej Chytil (was: Christian Ringele) Description: After reviewing associated code changes I see following outstanding tasks: - STKUtilQueryTest - ignored test should be removed - FooterAboutParagraphRenderingTest =&gt; delete - RedirectTemplateRendererTest - rewrite as integration test if there are no any redirects in there already - AbstractSTKRenderTestCase - delete - PURLoginFormRenderTest - delete In case the above is not clear: - footer, pur are already tested by integration test crawler - redirect should be tested same way either by having demo-content using re</pre> JIRA (on behalf of Jan Haderka 2012-05-15T13:56:44 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34547 <pre>GZip filter breaks cached forms in chrome: stange binary content at bottom -------------------------------------------------------------------------- Key: MAGNOLIA-4413 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4413 Project: Magnolia Issue Type: Bug Security Level: Public Components: cache, core Affects Versions: 4.5.2, 4.4.7 Reporter: Christian Ringele Priority: Critical Fix For: 4.5.x Attachments: StrangeBinaryContent.png Open in chrome (not logged in, needs to be server from the cache) th4e contact form: http://demopublic.magnolia-cms.com/.magnolia/pages/adminCentral.html See the print screen. At the bottom stange binary content is rendered. Only in chrome, works in firefox and safari. 1. Disable the gzip filter, problem gone. 2 or: server the form not form cache by adding ?dijnsi to the url, problem gone. Seems its the combination that the cahch gzipes, and the gzip filte</pre> JIRA (on behalf of Christian Ringele 2012-05-15T12:20:43 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34546 <pre> [ http://jira.magnolia-cms.com/browse/MAGNOLIA-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MAGNOLIA-4413: ---------------------------------------- Attachment: StrangeBinaryContent.png </pre> JIRA (on behalf of Christian Ringele 2012-05-15T12:20:43 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34545 <pre> [ http://jira.magnolia-cms.com/browse/MAGNOLIA-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Wespi updated MAGNOLIA-3821: -------------------------------- Attachment: Screen shot 2012-05-15 at 11.52.17.png </pre> JIRA (on behalf of Tom Wespi 2012-05-15T09:56:43 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34544 <pre> [ http://jira.magnolia-cms.com/browse/MGNLSTK-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MGNLSTK-951: -------------------------------------- Patch included: [Yes] Attachment: BodyClassResolver.txt </pre> JIRA (on behalf of Christian Ringele 2012-05-15T09:02:44 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34543 <pre>Disabling ExtrasArea without need to define class property: BodyClassResolver should first check if enabled, then cast. ----------------------------------------------------------------------------------------------------------------------- Key: MGNLSTK-951 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-951 Project: Magnolia Standard Templating Kit Issue Type: Improvement Components: base system, themepop Affects Versions: 2.0.2, 2.0.1, 2.0 Reporter: Christian Ringele Assignee: Christian Ringele Priority: Major Fix For: 2.0.3 Disabling the extras area is the most common use case on templates, besides reconfigure it. When disabling the extras area by adding the property enabled=false, a class cast exception happens in the BodyClassResolver. Without the definition of the specific bean by the class property, the code does not work. But it is really really hard for people to find out why th</pre> JIRA (on behalf of Christian Ringele 2012-05-15T08:56:44 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34542 <pre>default template variation resolver should consider the extension ------------------------------------------------------------------ Key: MAGNOLIA-4412 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4412 Project: Magnolia Issue Type: Bug Security Level: Public Affects Versions: 4.5.2 Reporter: Philipp Bärfuss Priority: Critical Fix For: 4.5.3 In older versions we supported so called sub templates (selected based on file name extension). In 4.5 we have introduced the more powerful template variations but our default implementation does only consider the channel. But it should use the following lookup for template variation names # channel-extension # extension # channel The instead of the two subclasses we should ship one which combines them: [RenderableVariationResolver|http://nexus.magnolia-cms.com/content/sites/magnolia.public.sites/ref/4.5.2/apidocs/info/magnolia/rendering/template/variation/</pre> JIRA (on behalf of Philipp Bärfuss 2012-05-15T08:08:43 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34541 <pre>Template availability do not use the configured id -------------------------------------------------- Key: MGNLSTK-950 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-950 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: templates Affects Versions: 2.0.2 Reporter: Frank Sommer Assignee: Philipp Bärfuss Priority: Major The {{info.magnolia.module.templatingkit.sites.TemplateAvailability}} class don't use the configured template _id_ from STK configuration. It uses the node name as fallback. The TemplateAvailability should use the configured _id_. </pre> JIRA (on behalf of Frank Sommer 2012-05-15T07:26:43 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34540 <pre> [ http://jira.magnolia-cms.com/browse/DOCU-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Hauser updated DOCU-263: ---------------------------------- Summary: Use Cases: Logical Scaling and Multi-Tenancy, how to deal with different type of content producers and projects (was: Use Cases: Improve Tech Brief 'Magnolia CMS Performance and High Availability') </pre> JIRA (on behalf of Christian Hauser 2012-05-15T07:26:43 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34539 <pre> [ http://jira.magnolia-cms.com/browse/DOCU-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antti Hietala updated DOCU-263: ------------------------------- Attachment: Logical-scaling.jpg </pre> JIRA (on behalf of Antti Hietala 2012-05-15T06:44:43 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34538 <pre>NullPointerException by configured jobs without parameters ---------------------------------------------------------- Key: MGNLSCH-28 URL: http://jira.magnolia-cms.com/browse/MGNLSCH-28 Project: Magnolia Scheduler Module Issue Type: Bug Affects Versions: 1.5.1, 1.4.2 Reporter: Frank Sommer Assignee: Philipp Bärfuss Priority: Minor Workaround is to configure a dummy parameter to this job. Then the job will be executed. Error occured on info.magnolia.module.scheduler.CommandJob line 88. </pre> JIRA (on behalf of Frank Sommer 2012-05-14T15:44:43 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34537 <pre> [ http://jira.magnolia-cms.com/browse/MAGNOLIA-4402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MAGNOLIA-4402: -------------------------------------- Fix Version/s: 4.5.3 (was: 4.5.x) </pre> JIRA (on behalf of Federico Grilli 2012-05-14T13:08:43 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34536 <pre> [ http://jira.magnolia-cms.com/browse/MAGNOLIA-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MAGNOLIA-4411: -------------------------------------- Description: Just realized this after testing the changes I made for MAGNOLIA-4402 (these changes have nothing to do with the issue being reported here which has been verified on current demoauthor.magnolia-cms.com 4.5.2). See attached screenshot. Just for the records, on IE9 it looks fine. Since we're probably going to need different workarounds for different browsers I think it's wise to start having a look at [GWT's conditional css|https://developers.google.com/web-toolkit/doc/latest/DevGuideClientBundle#Conditional_CSS] so that also css, like javascript, is evaluated at compiled-time and a specific version for each browser is produced. One could then write something like, ie {code} &lt; at &gt;if user.agent ie7 { .myClass { //do horrible workarounds } } &lt; at &gt;else { .myClass { //do it right } } {c</pre> JIRA (on behalf of Federico Grilli 2012-05-14T12:56:43 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34535 <pre>Main bar looks ugly on IE7 and IE8 ---------------------------------- Key: MAGNOLIA-4411 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4411 Project: Magnolia Issue Type: Bug Security Level: Public Components: page editor Affects Versions: 4.5.2 Reporter: Federico Grilli Priority: Major Attachments: GSi7H.png Just realized this after testing the changes I made for MAGNOLIA-4402 (these changes have nothing to do with the issue being reported here which has been verified on current demoauthor.magnolia-cms.com 4.5.2). See attached screenshot </pre> JIRA (on behalf of Federico Grilli 2012-05-14T12:44:43 http://permalink.gmane.org/gmane.comp.cms.magnolia.devel/34534 <pre> [ http://jira.magnolia-cms.com/browse/MAGNOLIA-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MAGNOLIA-4411: -------------------------------------- Environment: IE7, IE8 Description: Just realized this after testing the changes I made for MAGNOLIA-4402 (these changes have nothing to do with the issue being reported here which has been verified on current demoauthor.magnolia-cms.com 4.5.2). See attached screenshot. Just for the records, on IE9 it looks fine. (was: Just realized this after testing the changes I made for MAGNOLIA-4402 (these changes have nothing to do with the issue being reported here which has been verified on current demoauthor.magnolia-cms.com 4.5.2). See attached screenshot) </pre> JIRA (on behalf of Federico Grilli 2012-05-14T12:44:43 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.cms.magnolia.devel