[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3013) Moving paragraphs using edit bars not working properly in Internet Explorer (IE7 / IE8)
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nickolaus Wing updated MAGNOLIA-3013: - Attachment: general.patch We ran into this problem as well. It only happens when the window has been scrolled down a bit, and for us only seems to happen for paragraphs in our sidebar. There may be some kind of style difference that helps trigger it, but I couldn't tell you which. To fix it I changed getMousePos() to use the same method that the Prototype library uses to get the mouse position from the event. It worked. See the patch file I've included. > Moving paragraphs using edit bars not working properly in Internet Explorer > (IE7 / IE8) > --- > > Key: MAGNOLIA-3013 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3013 > Project: Magnolia > Issue Type: Bug > Components: gui >Affects Versions: 4.2.3 > Environment: Internet Explorer 7.0 and 8.0 under Windows. >Reporter: Hay Kranen >Assignee: Boris Kraft > Attachments: general.patch > > > When moving paragraphs using the 'move' button a bug occurs in both IE7 and > IE8. The green bar is floating approximately 150 pixels higher than were the > mouse cursor is, in some cases it's completely invisible. In Firefox / Safari > the bar is located where you expect it to be, right next to the mouse cursor. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MAGNOLIA-3225) Administratoren-Instanec magnoliaAuthor cannot be started
Administratoren-Instanec magnoliaAuthor cannot be started - Key: MAGNOLIA-3225 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3225 Project: Magnolia Issue Type: Bug Components: admininterface Affects Versions: 4.2.1 Environment: Tomcat Windows Reporter: Andreas Antener Assignee: Philipp Bärfuss Attachments: catalina.2010-06-10.zip Access to ../magnoliaAuthor/admin hangs (html code transfered but login screen ist not visible) no access to files in repository Please call Peter Mohn, +41 76 332 28 44 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2748) i18n: bundles should be chainable in one or the other way (in the configuration)
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28625#action_28625 ] Philipp Bärfuss commented on MAGNOLIA-2748: --- commons configuration has actually a very similar approach for including other properties files http://commons.apache.org/configuration/howto_properties.html > i18n: bundles should be chainable in one or the other way (in the > configuration) > > > Key: MAGNOLIA-2748 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2748 > Project: Magnolia > Issue Type: Improvement >Reporter: Philipp Bärfuss >Assignee: Boris Kraft > > The issue appears if one wants to create a new paragraph based on a paragraph > which uses already messages. In that case one would like to chain two bundles. > After a short discussion we found several potential solutions > A) use a special syntax in labels, .. bundle:key > B) support @include tags in the messages files (postprocess file in > DefaultMessagesImpl.getBundle()) > C) allow comma separated lists in i18nBasename definitions (could be a > general feature of the MessageManager or part of the FreemarekerHelper) > D) site wide template messages (register the bundles to use in a central > place: MAGNOLIA-1519) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLFORM-48) Form field 'selection': default value is not used -> null is passed to the freemarker
Form field 'selection': default value is not used -> null is passed to the freemarker - Key: MGNLFORM-48 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-48 Project: Magnolia Form Module Issue Type: Bug Affects Versions: 1.1.1 Reporter: Christian Ringele Assignee: Teresa Miyar When adding a 'selection' field, and defining a label:value, the value is passed to the template if the checkbox is checked. If not checked, the defined default value should be passed. But 'null' is passed to the freemaker instead. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3224) NPE using magnolia.utf8.enabled=true - UnicodeNormalizationFilter
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28624#action_28624 ] Hudson CI server commented on MAGNOLIA-3224: Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! [magnolia_main-4.3-branch #12|http://hudson.magnolia-cms.com/job/magnolia_main-4.3-branch/12/] Merged revisions 34963 via svnmerge from http://svn.magnolia-cms.com/svn/community/magnolia/trunk r34963 | lucaboati | 2010-06-09 19:11:23 +0200 (mer, 09 giu 2010) | 1 line MAGNOLIA-3224 to avoid double strip of context path if first node equals to context path > NPE using magnolia.utf8.enabled=true - UnicodeNormalizationFilter > - > > Key: MAGNOLIA-3224 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3224 > Project: Magnolia > Issue Type: Bug > Components: core >Affects Versions: 4.3.2 >Reporter: Luca Boati >Assignee: Luca Boati >Priority: Blocker > Fix For: 4.3.3, 5.0 > > Attachments: UnicodeNormalizationFilter.patch > > > Using magnolia.utf8.enabled=true a NPE occurs on UnicodeNormalizationFilter. > With MAGNOLIA-3204 the method resetAggregationState has been modified and now > it set these aggregationState properties to: > {{this.originalURI=null;}} > {{this.originalURL=null;}} > {{this.originalBrowserURI=null;}} > {{this.originalBrowserURL=null;}} > {{this.currentURI = null;}} > cannot be passed a null value to UnicodeNormalizer.normalizeNFC(null), this > cause NPE. > The UnicodeNormaliazioneFilter has to normalize originalURI/URL, to overwrite > these properties it needs to reset it, otherwise IllegalStateException could > occurs. > patch Included, if ok I can commit it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3224) NPE using magnolia.utf8.enabled=true - UnicodeNormalizationFilter
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28623#action_28623 ] Luca Boati commented on MAGNOLIA-3224: -- merge done > NPE using magnolia.utf8.enabled=true - UnicodeNormalizationFilter > - > > Key: MAGNOLIA-3224 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3224 > Project: Magnolia > Issue Type: Bug > Components: core >Affects Versions: 4.3.2 >Reporter: Luca Boati >Assignee: Luca Boati >Priority: Blocker > Fix For: 4.3.3, 5.0 > > Attachments: UnicodeNormalizationFilter.patch > > > Using magnolia.utf8.enabled=true a NPE occurs on UnicodeNormalizationFilter. > With MAGNOLIA-3204 the method resetAggregationState has been modified and now > it set these aggregationState properties to: > {{this.originalURI=null;}} > {{this.originalURL=null;}} > {{this.originalBrowserURI=null;}} > {{this.originalBrowserURL=null;}} > {{this.currentURI = null;}} > cannot be passed a null value to UnicodeNormalizer.normalizeNFC(null), this > cause NPE. > The UnicodeNormaliazioneFilter has to normalize originalURI/URL, to overwrite > these properties it needs to reset it, otherwise IllegalStateException could > occurs. > patch Included, if ok I can commit it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: