[magnolia-dev] [JIRA] (MGNLWORKFLOW-294) Magnolia module descriptor depends on diff module, which is missing from POM dependencies
Title: Message Title Nils Breunese updated an issue Magnolia Workflow Module / MGNLWORKFLOW-294 Magnolia module descriptor depends on diff module, which is missing from POM dependencies Change By: Nils Breunese Project: Magnolia Public User Registration Workflow Module Key: MGNLPUR MGNLWORKFLOW - 153 294 Affects Version/s: 5.4.5 Affects Version/s: 2.4.3 Add Comment This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814) 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:
[magnolia-dev] [JIRA] (MGNLPUR-153) Magnolia module descriptor depends on diff module, which is missing from POM dependencies
Title: Message Title Nils Breunese created an issue Magnolia Public User Registration / MGNLPUR-153 Magnolia module descriptor depends on diff module, which is missing from POM dependencies Issue Type: Bug Affects Versions: 2.4.3 Assignee: Unassigned Created: 20/Apr/15 4:09 PM Priority: Neutral Reporter: Nils Breunese I got the following error at Magnolia startup: Module Magnolia Public User Registration Module (version 2.4.3) is dependent on mail version 5.0.2/*, which was not found. Magnolia module descriptor depends on mail module, which is missing from POM dependencies. Adding this dependency fixes this issue: info.magnolia magnolia-module-mail
[magnolia-dev] [JIRA] (MGNLPUR-152) Magnolia module descriptor depends on mail module, which is missing from POM dependencies
Title: Message Title Nils Breunese created an issue Magnolia Public User Registration / MGNLPUR-152 Magnolia module descriptor depends on mail module, which is missing from POM dependencies Issue Type: Bug Affects Versions: 2.4.3 Assignee: Unassigned Created: 20/Apr/15 4:08 PM Priority: Neutral Reporter: Nils Breunese I got the following error at Magnolia startup: Module Magnolia Public User Registration Module (version 2.4.3) is dependent on mail version 5.0.2/*, which was not found. Magnolia module descriptor depends on mail module, which is missing from POM dependencies. Adding this dependency fixes this issue: info.magnolia magnolia-module-mail
[magnolia-dev] [JIRA] (MGNLFORM-259) Magnolia module descriptor depends on mail module, which is missing from POM dependencies
Title: Message Title Nils Breunese updated an issue Magnolia Form Module / MGNLFORM-259 Magnolia module descriptor depends on mail module, which is missing from POM dependencies Change By: Nils Breunese Project: Magnolia Observation Form Module Key: MGNLOBS MGNLFORM - 34 259 Affects Version/s: 2.2.11 Affects Version/s: 2.0.3 Security: Public Add Comment This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814) For list detail
[magnolia-dev] [JIRA] (MGNLFORM-259) Magnolia module descriptor depends on mail module, which is missing from POM dependencies
Title: Message Title
Nils Breunese updated an issue
Magnolia Form Module / MGNLFORM-259
Magnolia module descriptor depends on mail module, which is missing from POM dependencies
Change By:
Nils Breunese
I got the following error at Magnolia startup:{code}Module Magnolia Observation Form Module (version 2. 0 2 . 3 11 ) is dependent on mail version 5.0 .1 /*, which was not found.{code}Magnolia module descriptor depends on mail module, which is missing from POM dependencies. Adding this dependency fixes this issue:{code} info.magnolia magnolia-module-mail{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814)
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:
[magnolia-dev] [JIRA] (MGNLWORKFLOW-295) CLONE - Magnolia module descriptor depends on mail module, which is missing from POM dependencies
Title: Message Title Nils Breunese created an issue Magnolia Workflow Module / MGNLWORKFLOW-295 CLONE - Magnolia module descriptor depends on mail module, which is missing from POM dependencies Issue Type: Bug Affects Versions: 5.4.5 Assignee: Unassigned Created: 20/Apr/15 4:11 PM Priority: Neutral Reporter: Nils Breunese I got the following error at Magnolia startup: Module Magnolia Workflow Module (version 5.4.5) is dependent on diff version 1.6/*, which was not found. Magnolia module descriptor depends on diff module, which is missing from POM dependencies. Adding this dependency fixes this issue: info.magnolia magnolia-module-diff
[magnolia-dev] [JIRA] (MGNLWORKFLOW-295) Magnolia module descriptor depends on mail module, which is missing from POM dependencies
Title: Message Title Nils Breunese updated an issue Magnolia Workflow Module / MGNLWORKFLOW-295 Magnolia module descriptor depends on mail module, which is missing from POM dependencies Change By: Nils Breunese Summary: CLONE - Magnolia module descriptor depends on mail module, which is missing from POM dependencies Add Comment This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814) 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:
[magnolia-dev] [JIRA] (MGNLWORKFLOW-294) Magnolia module descriptor depends on diff module, which is missing from POM dependencies
Title: Message Title
Nils Breunese updated an issue
Magnolia Workflow Module / MGNLWORKFLOW-294
Magnolia module descriptor depends on diff module, which is missing from POM dependencies
Change By:
Nils Breunese
I got the following error at Magnolia startup:{code}Module Magnolia Public User Registration Workflow Module (version 2 5 .4. 3 5 ) is dependent on mail diff version 5 1 . 0.2 6 /*, which was not found.{code}Magnolia module descriptor depends on mail diff module, which is missing from POM dependencies. Adding this dependency fixes this issue:{code} info.magnolia magnolia-module- mail diff {code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814)
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:
[magnolia-dev] [JIRA] (MGNLRSSAGG-201) Magnolia module descriptor depends on mte 0.5/*, but has no Maven dependency
Title: Message Title Nils Breunese created an issue Magnolia RSS Aggregator Module / MGNLRSSAGG-201 Magnolia module descriptor depends on mte 0.5/*, but has no Maven dependency Issue Type: Bug Affects Versions: 2.4 Assignee: Unassigned Created: 10/Jul/15 4:05 PM Priority: Neutral Reporter: Nils Breunese Security Level: Public The Magnolia module descriptor of magnolia-module-rssaggregator-2.4 has this dependency: mte 0.5/* However, pom.xml doesn't depend on mte, so unless we manually add a dependency on mte to our project we get this error message on Magnolia startup: Module Magnolia RSS Aggregator Module (version 2.4.0) is dependent on mte (version 0.5/*), which was not found.
[magnolia-dev] [JIRA] (MGNLRSSAGG-201) Module Magnolia RSS Aggregator Module (version 2.4.0) is dependent on mte (version 0.5/*), which was not found.
Title: Message Title Nils Breunese updated an issue Magnolia RSS Aggregator Module / MGNLRSSAGG-201 Module Magnolia RSS Aggregator Module (version 2.4.0) is dependent on mte (version 0.5/*), which was not found. Change By: Nils Breunese Summary: Module Magnolia module descriptor depends RSS Aggregator Module (version 2.4.0) is dependent on mte (version 0.5/* ) , but has no Maven dependency for it which was not found. Add Comment This message was sent by Atlassian JIRA (v6.4.7#64022-sha1:4cb2968) 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:
[magnolia-dev] [JIRA] (MGNLRSSAGG-201) Magnolia module descriptor depends on mte 0.5/*, but has no Maven dependency for it
Title: Message Title Nils Breunese updated an issue Magnolia RSS Aggregator Module / MGNLRSSAGG-201 Magnolia module descriptor depends on mte 0.5/*, but has no Maven dependency for it Change By: Nils Breunese Summary: Magnolia module descriptor depends on mte 0.5/*, but has no Maven dependency for it Add Comment This message was sent by Atlassian JIRA (v6.4.7#64022-sha1:4cb2968) 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:
[magnolia-dev] [JIRA] (MGNLRSSAGG-201) Magnolia module descriptor depends on mte 0.5/*, but has no Maven dependency
Title: Message Title Nils Breunese updated an issue Magnolia RSS Aggregator Module / MGNLRSSAGG-201 Magnolia module descriptor depends on mte 0.5/*, but has no Maven dependency Change By: Nils Breunese Visible to: Rico Jansen Add Comment This message was sent by Atlassian JIRA (v6.4.7#64022-sha1:4cb2968) 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:
[magnolia-dev] [JIRA] (MGNLFORUM-287) Module Magnolia Module Forum (version 3.4.6) is dependent on adminInterface (version 5.0.2/*), which was not found.
Title: Message Title Nils Breunese created an issue Magnolia Forum Module / MGNLFORUM-287 Module Magnolia Module Forum (version 3.4.6) is dependent on adminInterface (version 5.0.2/*), which was not found. Issue Type: Bug Affects Versions: 3.4.6 Assignee: Unassigned Created: 10/Jul/15 4:18 PM Priority: Neutral Reporter: Nils Breunese Security Level: Public The Magnolia module descriptor of magnolia-module-forum-3.4.6 has this dependency: adminInterface 5.0.2/* However, pom.xml doesn't depend on the legacy admin interface, so unless we manually add the legacy admin interface to our project we get the following error message on Magnolia startup: Module Magnolia Module Forum (version 3.4.6) is dependent on adminInterface (version 5.0.2/*), which was not found.
[magnolia-dev] [JIRA] (MGNLFORUM-287) Module Magnolia Module Forum (version 3.4.6) is dependent on adminInterface (version 5.0.2/*), which was not found.
Title: Message Title Nils Breunese updated an issue Magnolia Forum Module / MGNLFORUM-287 Module Magnolia Module Forum (version 3.4.6) is dependent on adminInterface (version 5.0.2/*), which was not found. Change By: Nils Breunese Visible to: Rico Jansen Add Comment This message was sent by Atlassian JIRA (v6.4.7#64022-sha1:4cb2968) 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:
[magnolia-dev] [JIRA] (MGNLCACHE-119) "The defaultPageCache property is not set for the cache CacheFilter, falling back to defaultPageCache."
Title: Message Title Nils Breunese created an issue Magnolia Cache Module / MGNLCACHE-119 "The defaultPageCache property is not set for the cache CacheFilter, falling back to defaultPageCache." Issue Type: Bug Affects Versions: 5.4 Assignee: Unassigned Created: 20/Jul/15 2:49 PM Priority: Minor Reporter: Nils Breunese On a Magnolia 5.4 installation with a cleanly bootstrapped cache module, we get the following log message on startup: WARN info.magnolia.module.cache.filter.CacheFilter 20.07.2015 14:32:42 -- The defaultPageCache property is not set for the cache CacheFilter, falling back to defaultPageCache. This message seems to be logged by CacheFilter:119. The code in oCacheModuleStart() checks if defaultContentCachingConfigurationName is null, and apparently it is, but it seems the way to set this variable is to make sure setDefaultContentCachingConfigurationName() gets called. The obvious way to make sure that happens is via Node2Bean, which would mean having a property called defaultContentCachingConfigurationName. This property indeed doesn't exist, but the log message suggests that it's a property called defaultPageCache that's missing, which is actually not missing. My theory is that CacheFilter.DEFAULT_CONTENT_CACHING_CONFIGURATION_NAME is used for two different things:
[magnolia-dev] [JIRA] (MGNLUI-3623) Division by zero in JcrThumbnailContainer with less than 3 assets
Title: Message Title Nils Breunese created an issue Magnolia UI / MGNLUI-3623 Division by zero in JcrThumbnailContainer with less than 3 assets Issue Type: Bug Affects Versions: 5.4.2 Assignee: Unassigned Created: 13/Oct/15 3:32 PM Priority: Neutral Reporter: Nils Breunese Security Level: Public When there are less than 3 assets opening the thumbnail view in the assets app results in a division by zero error. In info.magnolia.ui.workbench.thumbnail.JcrThumbnailContainer#setPageSize pageSize gets divided by 3, but since this in an integer division 2/3 = 0. Then in AbstractJcrContainer#updateOffsetAndCache you get a division by zero in this code: currentOffset = (index / (pageLength * cacheRatio)) * (pageLength * cacheRatio); (Maybe this calculation should be more like the one in AbstractJcrContainer#indexOfId, which has a similar statement, but with +1 in the division?)
[magnolia-dev] [JIRA] (PAGES-45) Support URL fragments in preview mode
Title: Message Title Nils Breunese updated an issue Magnolia pages module / PAGES-45 Support URL fragments in preview mode Change By: Nils Breunese Affects Version/s: 5.4.1 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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:
[magnolia-dev] [JIRA] (APPSWITCH-13) App switcher does not work, throws exception
Title: Message Title Nils Breunese created an issue App switcher component / APPSWITCH-13 App switcher does not work, throws exception Issue Type: Bug Affects Versions: 1.1 Assignee: Aleksandr Pchelintcev Created: 05/Jan/16 5:44 PM Priority: Neutral Reporter: Nils Breunese I have added magnolia-appswitcher 1.1 to my Magnolia 5.4.2 based Maven project to try it out. When I press ALT+SHIFT on my iMac (OS X 10.11.2) the following appears in a red bar: Error: info.magnolia.appswitcher.vaadin.AppSwitcherLauncher$1.call(Lelemental/json/JsonArray;)V [MORE] The log shows this error: 2016-01-05 17:43:08,009 ERROR info.magnolia.ui.admincentral.AdmincentralErrorHandler#error.70 AdmincentralUI has encountered an unhandled exception. com.vaadin.server.ServerRpcManager$RpcInvocationException: Unable to invoke method call in com.vaadin.ui._javascript_$_javascript_CallbackRpc at com.vaadin.server.ServerRpcManager.applyInvocation(ServerRpcManager.java:170) at com.vaadin.server.ServerRpcManager.applyInvocation(ServerRpcManager.java:118) at com.vaadin.server.communication.ServerRpcHandler.handleInvocations(ServerRpcHandler.java:291) at com.vaadin.server.communication.ServerRpcHandler.handleRpc(ServerRpcHandler.java:184) at com.vaadin.server.communication.UidlRequestHandler.synchronizedHandleR
[magnolia-dev] [JIRA] (MGNLACTIVATION-126) Include workspace name in activation log message
Title: Message Title
Nils Breunese created an issue
Magnolia Activation Module / MGNLACTIVATION-126
Include workspace name in activation log message
Issue Type:
Improvement
Affects Versions:
5.4.3
Assignee:
Unassigned
Created:
22/Mar/16 1:39 PM
Priority:
Neutral
Reporter:
Nils Breunese
BaseSyndicatorImpl logs an INFO level message when activation has succeeded, but only logs the path of the activated node:
log.info("Exchange: activation succeeded [{}]", path);
It would be very helpful if the name of the workspace was also logged, because we have similarly named root nodes in for instance our website and dam workspaces.
Add Comment
[magnolia-dev] [JIRA] Created: (MAGNOLIA-3252) Version should not ignore SNAPSHOT classifier
Version should not ignore SNAPSHOT classifier - Key: MAGNOLIA-3252 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3252 Project: Magnolia Issue Type: Bug Components: updatemechanism Affects Versions: 4.3.2 Reporter: Nils Breunese Assignee: Boris Kraft Priority: Minor We have used some Magnolia and STK/ETK SNAPSHOT jars for a while on our central development repository and upgraded to final releases when they became available. The version numbers in the configuration workspace still say "4.3.2-SNAPSHOT" and "1.3.1-SNAPSHOT" though. Javadoc for info.magnolia.module.model.Version says: "Format is x.y.z-classifier. y,z and classifier are optional. The classifier string is ignored in version comparisons." I feel this could result in problems if version handler are changed during the SNAPSHOT phase. We install the SNAPSHOT jar, the module version is set to a SNAPSHOT version in the configuration workspace, but when we later upgrade to the release jar the Version class doesn't think the release version number is more recent, so the version handler won't be executed again. I feel it would be good to modify the Version class to reflect that version "x.y.z" is more recent than "x.y.z-SNAPSHOT". -- 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: (MGNLDATA-104) Add option to activate including sub nodes
Add option to activate including sub nodes -- Key: MGNLDATA-104 URL: http://jira.magnolia-cms.com/browse/MGNLDATA-104 Project: Magnolia Data Module Issue Type: Improvement Affects Versions: 1.4.2 Reporter: Nils Breunese Assignee: Philipp Bärfuss Priority: Minor The website repository provides two kinds of activation commands via the right mouse button click: 'Activate this page' and 'Activate incl. sub pages'. Sadly the data module only supports 'Activate this node' and no 'Activate incl. sub nodes'. This last option would have saved one of our editors activating ~300 individual nodes, so I feel it would make sense to add this option. -- 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] Updated: (MAGNOLIA-3341) Setting defaultExtension to '' breaks some functionality
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nils Breunese updated MAGNOLIA-3341: Summary: Setting defaultExtension to '' breaks some functionality (was: Setting defaultExtension to '' breaks certain functionality) > Setting defaultExtension to '' breaks some functionality > > > Key: MAGNOLIA-3341 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3341 > Project: Magnolia > Issue Type: Bug >Affects Versions: 4.3.7 >Reporter: Nils Breunese >Assignee: Boris Kraft >Priority: Minor > > I tried setting config:/server/defaultExtension to '' (empty string), because > I like extension-less page URL's. Most generated links work fine, but for > instance links to category pages stop working. -- 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-3341) Setting defaultExtension to '' breaks certain functionality
Setting defaultExtension to '' breaks certain functionality --- Key: MAGNOLIA-3341 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3341 Project: Magnolia Issue Type: Bug Affects Versions: 4.3.7 Reporter: Nils Breunese Assignee: Boris Kraft Priority: Minor I tried setting config:/server/defaultExtension to '' (empty string), because I like extension-less page URL's. Most generated links work fine, but for instance links to category pages stop working. -- 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-3367) Cannot move paragraph to another area
Cannot move paragraph to another area - Key: MAGNOLIA-3367 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3367 Project: Magnolia Issue Type: Bug Affects Versions: 4.3.8 Reporter: Nils Breunese Assignee: Boris Kraft A *lot* of pain would be taken away for our users if it were possible to move paragraphs between areas that both allow the paragraph type of the paragraph being moved. -- 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-3378) Cannot export/import XML under Security in AdminCentral
Cannot export/import XML under Security in AdminCentral --- Key: MAGNOLIA-3378 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3378 Project: Magnolia Issue Type: Bug Components: admininterface Affects Versions: 4.3.8 Reporter: Nils Breunese Assignee: Philipp Bärfuss Priority: Minor Most AdminCentral interfaces support exporting to and importing from XML, but this is not available for Roles and Groups. We'd like to be able to at least export to XML these items in order to be able to bootstrap them. We can do this via a workaround, but I think it should be possible to do this directly in AdminCentral when view Roles or Groups. -- 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] Updated: (MAGNOLIA-3378) Cannot export/import XML under Security in AdminCentral
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nils Breunese updated MAGNOLIA-3378: Description: Most AdminCentral interfaces support exporting to and importing from XML, but this is not available for Roles and Groups. We'd like to be able to at least export to XML these items in order to be able to bootstrap them. We can do this via a workaround, but I think it should be possible to do this directly in AdminCentral when viewing Roles or Groups. (was: Most AdminCentral interfaces support exporting to and importing from XML, but this is not available for Roles and Groups. We'd like to be able to at least export to XML these items in order to be able to bootstrap them. We can do this via a workaround, but I think it should be possible to do this directly in AdminCentral when view Roles or Groups.) > Cannot export/import XML under Security in AdminCentral > --- > > Key: MAGNOLIA-3378 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3378 > Project: Magnolia > Issue Type: Bug > Components: admininterface >Affects Versions: 4.3.8 >Reporter: Nils Breunese >Assignee: Philipp Bärfuss >Priority: Minor > > Most AdminCentral interfaces support exporting to and importing from XML, but > this is not available for Roles and Groups. We'd like to be able to at least > export to XML these items in order to be able to bootstrap them. We can do > this via a workaround, but I think it should be possible to do this directly > in AdminCentral when viewing Roles or Groups. -- 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-3532) Site definition with empty handlePrefix breaks AdminCentral
Site definition with empty handlePrefix breaks AdminCentral --- Key: MAGNOLIA-3532 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3532 Project: Magnolia Issue Type: Bug Affects Versions: 4.3.8 Reporter: Nils Breunese Assignee: Boris Kraft During some experimenting the handlePrefix for a site definition was accidentally set to "". After that AdminCentral was completely unavailable (login page with broken images, LDAP logins no longer worked, superuser login returned a blank page). Apparently this site definition was now being applied to /, which also broke AdminCentral. We had to configure the Groovy Rescue Servlet to fix the handlePrefix and bring back the author instance. To prevent others from experiencing the same problem it might be good if AdminCentral would not break if a handlePrefix is set to "". -- 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-3533) AdminCentral generates incorrect link to site when site definition name equals site node name (handlePrefix) and URIPrefix is not empty
AdminCentral generates incorrect link to site when site definition name equals site node name (handlePrefix) and URIPrefix is not empty --- Key: MAGNOLIA-3533 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3533 Project: Magnolia Issue Type: Bug Affects Versions: 4.3.8 Reporter: Nils Breunese Assignee: Boris Kraft 1. Put a website's content under /site in the website workspace. 2. Create a site definition with the name 'site' like this: + site \-- mappings \-- website |-- URIPrefix: /url |-- handlePrefix: /site \-- repository: website 3. Now try to open the website on the author instance. AdminCentral will send you to /site.html which yields a HTTP 404 Not Found error. Our findings are that this 404 only occurs when the site definition name equals the site node name (used in the handlePrefix) and the URIPrefix is not empty. Other cases seem to work. Sadly the not working case is the one we would like to use. -- 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] Updated: (MAGNOLIA-3533) AdminCentral generates incorrect link to site when site definition name equals site node name (handlePrefix) and URIPrefix is not empty
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nils Breunese updated MAGNOLIA-3533: Description: 1. Put a website's content under /site in the website workspace. 2. Create a site definition with the name 'site' like this: + site + mappings + website + URIPrefix: /url + handlePrefix: /site + repository: website 3. Now try to open the website on the author instance. AdminCentral will send you to /site.html which yields a HTTP 404 Not Found error. Our findings are that this 404 only occurs when the site definition name equals the site node name (used in the handlePrefix) and the URIPrefix is not empty. Other cases seem to work. Sadly the not working case is the one we would like to use. was: 1. Put a website's content under /site in the website workspace. 2. Create a site definition with the name 'site' like this: + site \- mappings \- website |- URIPrefix: /url |- handlePrefix: /site \- repository: website 3. Now try to open the website on the author instance. AdminCentral will send you to /site.html which yields a HTTP 404 Not Found error. Our findings are that this 404 only occurs when the site definition name equals the site node name (used in the handlePrefix) and the URIPrefix is not empty. Other cases seem to work. Sadly the not working case is the one we would like to use. > AdminCentral generates incorrect link to site when site definition name > equals site node name (handlePrefix) and URIPrefix is not empty > --- > > Key: MAGNOLIA-3533 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3533 > Project: Magnolia > Issue Type: Bug >Affects Versions: 4.3.8 >Reporter: Nils Breunese >Assignee: Boris Kraft > > 1. Put a website's content under /site in the website workspace. > 2. Create a site definition with the name 'site' like this: > + site > + mappings > + website > + URIPrefix: /url > + handlePrefix: /site > + repository: website > 3. Now try to open the website on the author instance. AdminCentral will send > you to /site.html which yields a HTTP 404 Not Found error. > Our findings are that this 404 only occurs when the site definition name > equals the site node name (used in the handlePrefix) and the URIPrefix is not > empty. Other cases seem to work. Sadly the not working case is the one we > would like to use. -- 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] Updated: (MAGNOLIA-3533) AdminCentral generates incorrect link to site when site definition name equals site node name (handlePrefix) and URIPrefix is not empty
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nils Breunese updated MAGNOLIA-3533: Description: 1. Put a website's content under /site in the website workspace. 2. Create a site definition with the name 'site' like this: + site \- mappings \- website |- URIPrefix: /url |- handlePrefix: /site \- repository: website 3. Now try to open the website on the author instance. AdminCentral will send you to /site.html which yields a HTTP 404 Not Found error. Our findings are that this 404 only occurs when the site definition name equals the site node name (used in the handlePrefix) and the URIPrefix is not empty. Other cases seem to work. Sadly the not working case is the one we would like to use. was: 1. Put a website's content under /site in the website workspace. 2. Create a site definition with the name 'site' like this: + site \-- mappings \-- website |-- URIPrefix: /url |-- handlePrefix: /site \-- repository: website 3. Now try to open the website on the author instance. AdminCentral will send you to /site.html which yields a HTTP 404 Not Found error. Our findings are that this 404 only occurs when the site definition name equals the site node name (used in the handlePrefix) and the URIPrefix is not empty. Other cases seem to work. Sadly the not working case is the one we would like to use. > AdminCentral generates incorrect link to site when site definition name > equals site node name (handlePrefix) and URIPrefix is not empty > --- > > Key: MAGNOLIA-3533 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3533 > Project: Magnolia > Issue Type: Bug >Affects Versions: 4.3.8 >Reporter: Nils Breunese >Assignee: Boris Kraft > > 1. Put a website's content under /site in the website workspace. > 2. Create a site definition with the name 'site' like this: > + site > \- mappings > \- website > |- URIPrefix: /url > |- handlePrefix: /site > \- repository: website > 3. Now try to open the website on the author instance. AdminCentral will send > you to /site.html which yields a HTTP 404 Not Found error. > Our findings are that this 404 only occurs when the site definition name > equals the site node name (used in the handlePrefix) and the URIPrefix is not > empty. Other cases seem to work. Sadly the not working case is the one we > would like to use. -- 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] Updated: (MAGNOLIA-3533) AdminCentral generates incorrect link to site when site definition name equals site node name (handlePrefix) and URIPrefix is not empty
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nils Breunese updated MAGNOLIA-3533: Description: 1. Put a website's content under /site in the website workspace. 2. Create a site definition with the name 'site' like this: * site ** mappings *** website URIPrefix: /url handlePrefix: /site repository: website 3. Now try to open the website on the author instance. AdminCentral will send you to /site.html which yields a HTTP 404 Not Found error. Our findings are that this 404 only occurs when the site definition name equals the site node name (used in the handlePrefix) and the URIPrefix is not empty. Other cases seem to work. Sadly the not working case is the one we would like to use. was: 1. Put a website's content under /site in the website workspace. 2. Create a site definition with the name 'site' like this: * site ** mappings *** website *** URIPrefix: /url *** handlePrefix: /site *** repository: website 3. Now try to open the website on the author instance. AdminCentral will send you to /site.html which yields a HTTP 404 Not Found error. Our findings are that this 404 only occurs when the site definition name equals the site node name (used in the handlePrefix) and the URIPrefix is not empty. Other cases seem to work. Sadly the not working case is the one we would like to use. > AdminCentral generates incorrect link to site when site definition name > equals site node name (handlePrefix) and URIPrefix is not empty > --- > > Key: MAGNOLIA-3533 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3533 > Project: Magnolia > Issue Type: Bug >Affects Versions: 4.3.8 >Reporter: Nils Breunese >Assignee: Boris Kraft > > 1. Put a website's content under /site in the website workspace. > 2. Create a site definition with the name 'site' like this: > * site > ** mappings > *** website > URIPrefix: /url > handlePrefix: /site > repository: website > 3. Now try to open the website on the author instance. AdminCentral will send > you to /site.html which yields a HTTP 404 Not Found error. > Our findings are that this 404 only occurs when the site definition name > equals the site node name (used in the handlePrefix) and the URIPrefix is not > empty. Other cases seem to work. Sadly the not working case is the one we > would like to use. -- 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] Updated: (MAGNOLIA-3533) AdminCentral generates incorrect link to site when site definition name equals site node name (handlePrefix) and URIPrefix is not empty
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nils Breunese updated MAGNOLIA-3533: Description: 1. Put a website's content under /site in the website workspace. 2. Create a site definition with the name 'site' like this: * site ** mappings *** website *** URIPrefix: /url *** handlePrefix: /site *** repository: website 3. Now try to open the website on the author instance. AdminCentral will send you to /site.html which yields a HTTP 404 Not Found error. Our findings are that this 404 only occurs when the site definition name equals the site node name (used in the handlePrefix) and the URIPrefix is not empty. Other cases seem to work. Sadly the not working case is the one we would like to use. was: 1. Put a website's content under /site in the website workspace. 2. Create a site definition with the name 'site' like this: + site + mappings + website + URIPrefix: /url + handlePrefix: /site + repository: website 3. Now try to open the website on the author instance. AdminCentral will send you to /site.html which yields a HTTP 404 Not Found error. Our findings are that this 404 only occurs when the site definition name equals the site node name (used in the handlePrefix) and the URIPrefix is not empty. Other cases seem to work. Sadly the not working case is the one we would like to use. > AdminCentral generates incorrect link to site when site definition name > equals site node name (handlePrefix) and URIPrefix is not empty > --- > > Key: MAGNOLIA-3533 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3533 > Project: Magnolia > Issue Type: Bug >Affects Versions: 4.3.8 >Reporter: Nils Breunese >Assignee: Boris Kraft > > 1. Put a website's content under /site in the website workspace. > 2. Create a site definition with the name 'site' like this: > * site > ** mappings > *** website > *** URIPrefix: /url > *** handlePrefix: /site > *** repository: website > 3. Now try to open the website on the author instance. AdminCentral will send > you to /site.html which yields a HTTP 404 Not Found error. > Our findings are that this 404 only occurs when the site definition name > equals the site node name (used in the handlePrefix) and the URIPrefix is not > empty. Other cases seem to work. Sadly the not working case is the one we > would like to use. -- 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: (MGNLRES-32) pom.xml missing dependency on fckeditor module
pom.xml missing dependency on fckeditor module -- Key: MGNLRES-32 URL: http://jira.magnolia-cms.com/browse/MGNLRES-32 Project: Magnolia Resources Module Issue Type: Bug Affects Versions: 1.3.1 Reporter: Nils Breunese Assignee: Federico Grilli The Magnolia module descriptor has a dependency on the fckeditor, but the Maven pom.xml doesn't have this dependency. This caused a problem when writing unit tests. -- 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: (MGNLPUR-52) pom.xml missing dependency on mail module
pom.xml missing dependency on mail module - Key: MGNLPUR-52 URL: http://jira.magnolia-cms.com/browse/MGNLPUR-52 Project: Magnolia Public User Registration Issue Type: Bug Affects Versions: 1.1.3 Reporter: Nils Breunese Assignee: Grégory Joseph The Magnolia module descriptor has a dependency on the mail, but the Maven pom.xml doesn't have this dependency. This caused a problem when writing unit tests and we had to manually add the test dependency on the mail module ourselves. -- 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-3539) AdminCentral generates incorrect link to site when the site root node is no direct child of website repository root
AdminCentral generates incorrect link to site when the site root node is no direct child of website repository root --- Key: MAGNOLIA-3539 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3539 Project: Magnolia Issue Type: Bug Components: admininterface Affects Versions: 4.3.8 Reporter: Nils Breunese Assignee: Philipp Bärfuss Attachments: config.modules.extended-templating-kit.config.sites.pip-test1.xml, website.pip.xml We no longer want all site root nodes on one level, as we get too many sites. We want to group them, so site root nodes are no longer direct children of the repository root. But if the site root node is not a child of the website repository root, then you need a link like: /[site def name]/[urlPrefix or path to site].html, but admin central creates link: /[url prefix or path to page].html so sites don't open correctly from admin central. Site definition and website tree attached. -- 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] Updated: (MGNLSTK-756) CssSelectorSupportRenderingModel doesn't use generics
[
http://jira.magnolia-cms.com/browse/MGNLSTK-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nils Breunese updated MGNLSTK-756:
--
Labels: vpro (was: )
> CssSelectorSupportRenderingModel doesn't use generics
> -
>
> Key: MGNLSTK-756
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-756
> Project: Magnolia Standard Templating Kit
> Issue Type: Bug
>Affects Versions: 1.4.2
>Reporter: Nils Breunese
>Assignee: Philipp Bärfuss
>
> RenderingModelImpl has apparently been fixed to use generics correctly
> ('implements RenderingModel' instead the former 'implements
> RenderingModel'), but now we run into problems with other Magnolia class
> which don't use generics.
> For instance we have a class of our own which 'extends
> RenderingModelImpl implements CssSelectorSupportRenderingModel',
> but since CssSelectorSupportRenderingModel 'extends RenderingModel' we get
> compilation errors.
> Please use generics consistently to avoid these problems.
--
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: (MGNLSTK-756) CssSelectorSupportRenderingModel doesn't use generics
CssSelectorSupportRenderingModel doesn't use generics
-
Key: MGNLSTK-756
URL: http://jira.magnolia-cms.com/browse/MGNLSTK-756
Project: Magnolia Standard Templating Kit
Issue Type: Bug
Affects Versions: 1.4.2
Reporter: Nils Breunese
Assignee: Philipp Bärfuss
RenderingModelImpl has apparently been fixed to use generics correctly
('implements RenderingModel' instead the former 'implements
RenderingModel'), but now we run into problems with other Magnolia class which
don't use generics.
For instance we have a class of our own which 'extends
RenderingModelImpl implements CssSelectorSupportRenderingModel', but
since CssSelectorSupportRenderingModel 'extends RenderingModel' we get
compilation errors.
Please use generics consistently to avoid these problems.
--
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-3598) Show time in JCR browser
Show time in JCR browser Key: MAGNOLIA-3598 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3598 Project: Magnolia Issue Type: Improvement Components: admininterface Affects Versions: 4.3.8 Reporter: Nils Breunese Assignee: Philipp Bärfuss I have a dialog with a date control which has time set to true. When I save a date with the time set and then go to AdminCentral > Tools > JCR Browser (Website) and browse to the saved property it displays as only the date part, not the time. I can see the associated time when opening the dialog again or exporting to XML, but I think the JCR Browser should show the time as well. -- 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] (MGNLSITE-59) Site app should automatically configure itself correctly when added to a project
Title: Message Title Nils Breunese created an issue Magnolia Site Module / MGNLSITE-59 Site app should automatically configure itself correctly when added to a project Issue Type: Improvement Affects Versions: 1.0.5 Assignee: Unassigned Components: app Created: 12/Apr/16 3:35 PM Priority: Neutral Reporter: Nils Breunese We build our own Magnolia WAR project with custom modules. We added the magnolia-site-app to our project after we had already upgraded to STK 2.9.3 and found that we had to manually change config:/modules/site-app/apps/site/subApps/browser/contentConnector@rootPath to /modules/multisite/config/sites for our multisite setup. Also, STKModuleVersionHandler removes the legacy Site definitions and Themes entries from the STK app launcher group when the site-app module is installed when upgrading to STK 2.9.3, but in our case the site-app module was installed after upgrading to STK 2.9.3, so this didn't happen and we also had to remove these legacy entries manually. Maybe it would be better to have SiteAppModuleVersionHandler take care of this, so that this also happens when adding the site-app module later on.
[magnolia-dev] [JIRA] (DOCU-819) Wrong log in link at the bottom of documentation pages
Title: Message Title Nils Breunese created an issue Documentation / DOCU-819 Wrong log in link at the bottom of documentation pages Issue Type: Bug Assignee: Unassigned Created: 15/Sep/16 10:26 AM Priority: Neutral Reporter: Nils Breunese Security Level: Public The link at the bottom of a documentation page points to http://wiki.magnolia-cms.com/login.action which logs you in on the wiki, but not the documentation site, so I can't leave a comment after logging in via that link. The log in link at the top right of the page has the correct link for logging in to the documentation site. Add Comment
[magnolia-dev] [JIRA] (MGNLREST-79) Provide error messages for REST calls that return a client error message
Title: Message Title Nils Breunese created an issue Magnolia REST Framework / MGNLREST-79 Provide error messages for REST calls that return a client error message Issue Type: Improvement Affects Versions: 1.1.1 Assignee: Unassigned Components: services Created: 30/Sep/16 3:08 PM Priority: Neutral Reporter: Nils Breunese Security Level: Public Currently for instance PUT calls to /.rest/workspace/path return 400 Bad Request for all of the following error conditions: No name specified for node to create No type specified for node to create Parent path does not exist
[magnolia-dev] [JIRA] (MGNLUI-4086) Add option to set 'now as the default value for a date field
Title: Message Title Nils Breunese created an issue Magnolia UI / MGNLUI-4086 Add option to set 'now as the default value for a date field Issue Type: Improvement Assignee: Unassigned Components: forms Created: 24/Nov/16 11:28 AM Priority: Neutral Reporter: Nils Breunese Security Level: Public We have multiple use cases where it would be nice to have the option to set the default value of a date field to the current date/time (the moment the dialog field is instantiated). Now editors need to click the calendar, which does pre-select the current date, but it would be great if that wasn't required and the current date would just be pre-filled in the field when the field configuration says so. Add Comment
[magnolia-dev] [JIRA] (MGNLUI-4087) Set focus to newly created field when clicking 'add' for a multi-value field
Title: Message Title Nils Breunese created an issue Magnolia UI / MGNLUI-4087 Set focus to newly created field when clicking 'add' for a multi-value field Issue Type: Improvement Assignee: Unassigned Components: forms Created: 24/Nov/16 11:34 AM Priority: Neutral Reporter: Nils Breunese Security Level: Public We use some multi-value fields in dialogs, for instance to add tags, and our editors would appreciate it if the focus was automatically set to the newly created field when clicking 'add' for a multi-value field. Add Comment
[magnolia-dev] [JIRA] (MGNLUI-4086) Add option to set 'now' as the default value for a date field
Title: Message Title Nils Breunese updated an issue Magnolia UI / MGNLUI-4086 Add option to set 'now' as the default value for a date field Change By: Nils Breunese Summary: Add option to set 'now ' as the default value for a date field Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 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:
[magnolia-dev] [JIRA] (MGNLRES-60) Allow loading of file system resources from relative path
Nils Breunese created MGNLRES-60 Allow loading of file system resources from relative path Issue Type: New Feature Affects Versions: 1.4.3 Assignee: Federico Grilli Created: 24/May/13 2:12 PM Description: Following from SUPPORT-1942 which we opened, MGNLRES-52 introduced a feature to allow configuring filesystem resource loaders, as documented via DOCU-349. This almost solves our use case, but sadly FileSystemResourceLoader currently doesn't allow using relative paths. Since our application has to work in many different environments, using absolute paths is not really an option. I believe that if on line 75 of FileSystemResourceLoader 'path' would be changed to 'file.getCanonicalPath()' the feature would still be secure, but would also allow using relative paths. Project: Magnolia Resources Module Labels: VPRO Priority: Neutral Reporter: Nils Breunese This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira 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:
[magnolia-dev] [JIRA] (MAGNOLIA-5080) ${contextPath} in magnolia.initialization.file context parameter in web.xml is not replaced
Nils Breunese
created MAGNOLIA-5080
${contextPath} in magnolia.initialization.file context parameter in web.xml is not replaced
Issue Type:
Bug
Affects Versions:
4.4.11
Assignee:
Unassigned
Components:
core
Created:
05/Jun/13 11:27 AM
Description:
According to http://documentation.magnolia-cms.com/reference/configuration.html#Customization it is possible to use $
{contextPath} in the value of the magnolia.initialization.file context parameter in web.xml, but this does not seem to be the case.
PropertiesInitializer.processPropertyFilesString(context, servername, webapp, propertiesFilesString) indeed does not seem to replace ${contextPath}
.
Project:
Magnolia
Labels:
vpro
Priority:
Neutral
Reporter:
Nils Breunese
Security Level:
Public
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
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:
[magnolia-dev] [JIRA] (MGNLFORM-173) Some Dutch translations for the form module
Nils Breunese created MGNLFORM-173 Some Dutch translations for the form module Issue Type: Improvement Affects Versions: 1.3.5 Assignee: Unassigned Attachments: 0001-Added-some-Dutch-messages.patch Created: 05/Jun/13 12:01 PM Description: Here are some Dutch translated strings for the form module. Project: Magnolia Form Module Labels: vpro Priority: Neutral Reporter: Nils Breunese Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira 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:
[magnolia-dev] [JIRA] (MGNLFORM-173) Some Dutch translations for the form module
Nils Breunese updated MGNLFORM-173 Some Dutch translations for the form module Change By: Nils Breunese (05/Jun/13 12:01 PM) Attachment: 0001-Added-some-Dutch-messages.patch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira 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:
[magnolia-dev] [JIRA] (MAGNOLIA-5111) Time does not get saved, because date control ignores extends property
Nils Breunese created MAGNOLIA-5111 Time does not get saved, because date control ignores extends property Issue Type: Bug Affects Versions: 4.4.11 Assignee: Unassigned Components: admininterface Created: 13/Jun/13 12:06 PM Description: info.magnolia.module.admininterface.SaveHandlerImpl#processDate checks whether the configNode has a property called 'time' set to 'true' to decide whether or not to save the time part of the date. When a date control which doesn't have the 'time' property set extends another date control which does have 'time' set to 'true' this is ignored and the time is not saved. This is a regression from 4.4.9-jr24, because with that version this worked fine for us. Project: Magnolia Labels: vpro Priority: Major Reporter: Nils Breunese Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira 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:
[magnolia-dev] [JIRA] (MAGNOLIA-5120) Magnolia sends empty Pragma header for login page CSS
Nils Breunese created MAGNOLIA-5120 Magnolia sends empty Pragma header for login page CSS Issue Type: Bug Affects Versions: 4.4.11 Assignee: Unassigned Components: admininterface Created: 18/Jun/13 12:01 PM Description: http://redbot.org/?uri=http%3A%2F%2Fdemo.magnolia-cms.com%2F.resources%2FloginForm%2Flogin.css says "The Pragma header is being used in an undefined way". The CSS for the login page is served with a Pragma header without a value, while the HTTP spec only defines 'Pragma: no-cache'. Project: Magnolia Labels: vpro Priority: Neutral Reporter: Nils Breunese Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira 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:
[magnolia-dev] [JIRA] (MGNLMIGRATION-251) Migration fails to update available component if node name and node's name property don't contain the same name
Nils Breunese
created MGNLMIGRATION-251
Migration fails to update available component if node name and node's name property don't contain the same name
Issue Type:
Bug
Affects Versions:
1.2.3
Assignee:
Unassigned
Components:
Migration Task
Created:
22/Jul/13 4:04 PM
Description:
Before Magnolia 4.5 a node representing an available component (paragraph in prototype for instance) will often have the same name as the value the node's name property (node data). When this is not the case (which is valid AFAIK) TransformStkBasedTemplateMigrationTask#updateAvailableComponent(node) will look for the wrong component name.
I believe the fix is to have this method use node.getProperty("name") (which is used when removing the old value!) instead of node.getName().
Project:
Magnolia Migration
Priority:
Neutral
Reporter:
Nils Breunese
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
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:
[magnolia-dev] [JIRA] (MGNLRSSAGG-91) Using a path with a dash ("-") in a stkSingleFeed paragraph causes an exception in FeedListModel
Nils Breunese
created MGNLRSSAGG-91
Using a path with a dash ("-") in a stkSingleFeed paragraph causes an exception in FeedListModel
Issue Type:
Bug
Affects Versions:
1.2.4
Assignee:
Unassigned
Created:
01/Aug/13 1:52 PM
Description:
I created an RSS Aggregator under AdminCentral > Data > RSS Aggregators and called it '3FM Lowlands'. This created data:/rssaggregator/3FM-Lowlands.
When selecting this path in an instance of stkSingleFeed the FeedListModel class throws an InvalidQueryException in the getFeeds() method, saying:
javax.jcr.query.InvalidQueryException: Encountered "-" at line 1, column 38.
Was expecting one of:
...
...
...
...
" ...
" ...
...
...
...
...
...
...
...
...
...
...
...
...
"$" ...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
"*" ...
...
...
"(" ...
"@" ...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
"." ...
".." ...
...
"<" ...
"<" ...
"
[magnolia-dev] [JIRA] (MGNLRSSAGG-91) Using a path with a dash ("-") in a stkSingleFeed paragraph causes an exception in FeedListModel
Nils Breunese
updated MGNLRSSAGG-91
Using a path with a dash ("-") in a stkSingleFeed paragraph causes an exception in FeedListModel
Change By:
Nils Breunese
(01/Aug/13 1:53 PM)
Description:
I created an RSS Aggregator under AdminCentral > Data > RSS Aggregators and called it '3FM Lowlands'. This created {{data:/rssaggregator/3FM-Lowlands}}.When selecting this path in an instance of {{stkSingleFeed}} the {{FeedListModel}} class throws an InvalidQueryException in the {{getFeeds()}} method, saying:{code}javax.jcr.query.InvalidQueryException: Encountered "-" at line 1, column 38.Was expecting one of: ... ... ... ..."" ... ... ... ... ... ... ... ... ... ... ... ..."$" ... ... ... ... ... ... ... ... ... ... ... ... ... ... ..."*" ... ... ..."(" ..."@" ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ..."." ...".." ... ..."<" ..."<" ..."
[magnolia-dev] [JIRA] (MGNLRSSAGG-91) Using a path with a dash ("-") or a feed name starting with a digit in a stkSingleFeed paragraph causes an exception in FeedListModel
Nils Breunese
updated MGNLRSSAGG-91
Using a path with a dash ("-") or a feed name starting with a digit in a stkSingleFeed paragraph causes an exception in FeedListModel
Change By:
Nils Breunese
(01/Aug/13 2:29 PM)
Summary:
Using a path with a dash ("-") or
a feed name
starting with a digit in a stkSingleFeed paragraph causes an exception in FeedListModel
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
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:
[magnolia-dev] [JIRA] (MGNLRSSAGG-91) Using a path with a dash ("-") or starting with a digit in a stkSingleFeed paragraph causes an exception in FeedListModel
Nils Breunese
updated MGNLRSSAGG-91
Using a path with a dash ("-") or starting with a digit in a stkSingleFeed paragraph causes an exception in FeedListModel
Change By:
Nils Breunese
(01/Aug/13 2:28 PM)
Summary:
Using a path with a dash ("-")
or starting with a digit
in a stkSingleFeed paragraph causes an exception in FeedListModel
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
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:
[magnolia-dev] [JIRA] (MGNLSTK-1219) stkSingleFeed paragraph doesn't honor setting for number of entries
Nils Breunese created MGNLSTK-1219 stkSingleFeed paragraph doesn't honor setting for number of entries Issue Type: Bug Affects Versions: 1.4.9 Assignee: Unassigned Components: paragraphs Created: 02/Aug/13 11:15 AM Description: I configured the RSS module to import an RSS feed with 20 items. I then placed an stkSingleFeed paragraph on a page and set 'Number of entries' in its dialog to 10. The paragraph still displays 20 items. Project: Magnolia Standard Templating Kit Priority: Neutral Reporter: Nils Breunese Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira 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:
[magnolia-dev] [JIRA] (DOCU-454) Magnolia 4.5.10 release notes
Nils Breunese created DOCU-454 Magnolia 4.5.10 release notes Issue Type: Bug Assignee: Antti Hietala Created: 05/Aug/13 3:50 PM Description: According to http://wiki.magnolia-cms.com/display/DOCS45/Release+notes+for+Magnolia+4.5.10 Pacakager 4.0.9 was released. This version does not seem to be available in Nexus. The list of new modules also contains two versions of the Form module (1.4.7 and 1.4.8), two versions of the Groovy module (1.2.6 twice), two versions of the Diff module (1.1.5 and 1.2) and two versions of the LDAP module (1.6.1 and 1.6.2). And then below there is another section called 'Updated modules' which contains no modules. This is all a bit confusing. Project: Documentation Priority: Neutral Reporter: Nils Breunese Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira 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:
[magnolia-dev] [JIRA] (DOCU-454) Mistakes in Magnolia 4.5.10 release notes
Nils Breunese updated DOCU-454 Mistakes in Magnolia 4.5.10 release notes Change By: Nils Breunese (05/Aug/13 4:22 PM) Summary: Mistakes in Magnolia 4.5.10 release notes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira 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:
[magnolia-dev] [JIRA] (MGNLRSSAGG-94) Add default node data in config workspace for backup setting of RSSFeedImportHandler
Nils Breunese created MGNLRSSAGG-94 Add default node data in config workspace for backup setting of RSSFeedImportHandler Issue Type: Improvement Affects Versions: 1.2.4 Assignee: Unassigned Created: 06/Aug/13 11:52 AM Description: I noticed that since configuring the RSS aggregator to automatically import an external feed every hour I noticed that Magnolia started creating backup files every hour as well. It took some code digging to find that this behavior can be controlled by adding a node data called backup and setting it to false (since RSSFeedImportHandler extends ImportHandler and that class creates backups based on a property called backup which can be set via Content2Bean). It would be helpful if a default node data backup would have been bootstrapped by the RSS aggregator module and if the RSS aggregator module documentation would have mentioned this behavior. Project: Magnolia RSS Aggregator Module Priority: Neutral Reporter: Nils Breunese This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira 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:
[magnolia-dev] [JIRA] (MAGNOLIA-5328) magnolia-templating-editor-4.5.11.jar contains both sources and class files
Nils Breunese created MAGNOLIA-5328 magnolia-templating-editor-4.5.11.jar contains both sources and class files Issue Type: Bug Affects Versions: 4.5.11 Assignee: Unassigned Components: templating Created: 23/Sep/13 1:35 PM Description: When inspecting magnolia-templating-editor in my IDE I noticed that all classes were listed twice. Inspecting the jar shows that it contains both sources and class files. Project: Magnolia Priority: Neutral Reporter: Nils Breunese Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira 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:
[magnolia-dev] [JIRA] (MAGNOLIA-5407) PropertyUtil should offer a getLong() method
Nils Breunese created MAGNOLIA-5407 PropertyUtil should offer a getLong() method Issue Type: Improvement Affects Versions: 4.5.12 Assignee: Unassigned Components: core Created: 21/Oct/13 4:04 PM Description: PropertyUtil has get methods for strings, dates and booleans, but no method for longs. It would be nice if PropertyUtil had a getLong() method as well. Project: Magnolia Labels: vpro Priority: Neutral Reporter: Nils Breunese Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira 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:
[magnolia-dev] [JIRA] (MAGNOLIA-5408) In preview mode click handlers are not fired on document elements
Nils Breunese
created MAGNOLIA-5408
In preview mode click handlers are not fired on document elements
Issue Type:
Bug
Affects Versions:
4.5.12
Assignee:
Unassigned
Components:
page editor
Created:
22/Oct/13 11:54 AM
Description:
We noticed that in preview mode certain functionality that used to work in Magnolia 4.4 doesn't anymore in 4.5. It seems some GWT _javascript_ added by Magnolia is preventing click events on the document.
We understand clicks are prevented in edit mode, but we believe the site should work as on a public node in preview mode.
Try the adding the following using for example the _javascript_ console in your browser:
jQuery(document).click(function() { alert('Should give alert'); });
Project:
Magnolia
Labels:
vpro
Priority:
Major
Reporter:
Nils Breunese
Security Level:
Public
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
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:
[magnolia-dev] [JIRA] (MAGNOLIA-5408) In preview mode click handlers are not fired on document elements
Nils Breunese
updated MAGNOLIA-5408
In preview mode click handlers are not fired on document elements
Change By:
Nils Breunese
(22/Oct/13 11:55 AM)
Description:
We noticed that in *preview mode* certain
site
functionality that used to work in Magnolia 4.4 doesn't anymore in 4.5. It seems some GWT _javascript_ added by Magnolia is preventing click events on the document.We understand clicks are prevented in edit mode, but we believe the site should work as on a public node in preview mode.Try the adding the following using for example the _javascript_ console in your browser: {code}jQuery(document).click(function() { alert('Should give alert'); });{code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
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:
[magnolia-dev] [JIRA] (MGNLSTK-1261) STKPageModel should return List
Nils Breunese created MGNLSTK-1261 STKPageModel should return List Issue Type: Bug Assignee: Unassigned Created: 28/Oct/13 11:52 AM Description: The return type for STKPageModel#getCategories() is List. The method comment for STKPageModel#getCategories() suggests the method returns List, but it really returns List, since that is what STKTemplatingFunctions#getCategories(Node page) returns. Project: Magnolia Standard Templating Kit Labels: vpro Priority: Neutral Reporter: Nils Breunese Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira 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:
[magnolia-dev] [JIRA] (MGNLSTK-1261) STKPageModel should return List
Nils Breunese updated MGNLSTK-1261 STKPageModel should return List Change By: Nils Breunese (28/Oct/13 11:53 AM) Affects Version/s: 2.0.13 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira 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:
[magnolia-dev] [JIRA] (MAGNOLIA-5426) DumperUtil should offer a dump method with a single Node argument
Nils Breunese created MAGNOLIA-5426 DumperUtil should offer a dump method with a single Node argument Issue Type: Improvement Affects Versions: 4.5.12 Assignee: Unassigned Created: 28/Oct/13 4:01 PM Description: It would be nice if DumperUtil had a dump(Node node) method, just like it has a dump(Content content) method. Project: Magnolia Labels: vpro Priority: Neutral Reporter: Nils Breunese Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira 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:
[magnolia-dev] [JIRA] (MGNLRSSAGG-117) Importing an RSS feed fails because of missing required metaData
Nils Breunese created MGNLRSSAGG-117 Importing an RSS feed fails because of missing required metaData Issue Type: Bug Affects Versions: 1.4.3 Assignee: Unassigned Created: 04/Nov/13 2:44 PM Description: While importing an RSS feed the recreateFeedChannelNode method of RSSFeedImportHandler is called and calls NodeUtil.createPath to create a node for the channel with the dataItemNode node type. This ends with an exception in ItemSaveOperation.validateTransientItems because this method checks for mandatory child nodes (line 554) and the data:/rssaggregator/news/data node doesn't have a MetaData node. Indeed magnolia-module-data-nodetypes.xml defines mgnl:metaData as a required child node definition for the dataItemNode node type. We are using RSS Aggregator module 1.4.5 and Data module 1.7.7. Should a migration task add metaData to dataItemNode nodes or shouldn't metaData be required for these nodes? Project: Magnolia RSS Aggregator Module Labels: vpro Priority: Neutral Reporter: Nils Breunese This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira 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:
[magnolia-dev] [JIRA] (MGNLUI-1786) Cannot move page component to another area
Nils Breunese updated MGNLUI-1786 Cannot move page component to another area Change By: Nils Breunese (05/Dec/13 11:02 AM) Description: A *lot* of pain would be taken away for our users if it were possible to move paragraphs components between areas that both allow the paragraph component type of the paragraph component being moved. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira 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:
[magnolia-dev] [JIRA] (MGNLCACHE-53) CLONE - Delegating ServletOutputStream implementations should delegate calls for writing chunks
Nils Breunese created MGNLCACHE-53 CLONE - Delegating ServletOutputStream implementations should delegate calls for writing chunks Issue Type: Improvement Assignee: Tobias Mattsson Created: 11/Feb/14 11:50 PM Description: Currently GZipCacheResponseWrapper.DeferredServletOutputStream and SimpleServletOutputStream only overrides write(byte) and therefore each byte is treated individually when written to the output stream. This happens when we're caching, for instance serving pages via RenderingEngine, images from the imaging module and the dam module. We also go through this code when the gzip filter wraps the response in order to compress it. By implementing write(byte[]) and write(byte[], int, int) we can reduce the amount of work needed both in these classes and the classes being delegated to. Specifically ThresholdingOutputStream can test if the threshold will be exceeded once instead of for every byte. The improvements in performance by this fix has been measured to be very limited. Fix Versions: 5.2.1 Project: Magnolia Cache Module Priority: Neutral Reporter: Nils Breunese This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira 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:
[magnolia-dev] [JIRA] Created: (MGNLGA-3) Rename GoggleAnalyticsJSResourceModel.java to GoogleAnalyticsJSResourceModel.java
Rename GoggleAnalyticsJSResourceModel.java to GoogleAnalyticsJSResourceModel.java - Key: MGNLGA-3 URL: http://jira.magnolia-cms.com/browse/MGNLGA-3 Project: Magnolia Google Analytics Issue Type: Bug Reporter: Nils Breunese Assignee: Christian Ringele Priority: Trivial Please refactor src/main/java/info/magnolia/module/googleanalytics/model/GoggleAnalyticsJSResourceModel.java to src/main/java/info/magnolia/module/googleanalytics/model/GoogleAnalyticsJSResourceModel.java. -- 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: (MGNLGA-4) Remove redundant basic install tasks from extra install tasks in version handler
Remove redundant basic install tasks from extra install tasks in version handler Key: MGNLGA-4 URL: http://jira.magnolia-cms.com/browse/MGNLGA-4 Project: Magnolia Google Analytics Issue Type: Bug Reporter: Nils Breunese Assignee: Christian Ringele Priority: Minor The getExtraInstallTasks() method has the following call: installTasks.addAll(super.getBasicInstallTasks(ctx)); This is redundant and should be removed. Please see the thread at http://www.nabble.com/Version-handler-install-tasks-td26011961.html for Jan Haderka's comment. -- 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- 2945) FreeMarker ?ancestors and ?root built-ins don't work
FreeMarker ?ancestors and ?root built-ins don't work Key: MAGNOLIA-2945 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2945 Project: Magnolia Issue Type: Bug Components: templating Affects Versions: 4.1.1 Reporter: Nils Breunese Assignee: Philipp Bärfuss I wanted to use the FreeMarker ?ancestors built-in (http://freemarker.sourceforge.net/docs/ref_builtins_node.html) in a FreeMarker template. However, it doesn't seem to work. I added this: [#assign ancs = content?ancestors] But just this statement results in: Can't get parent of I18nContentWrapper for website:/[rep:root]:root node doesn't have a parent I found the same goes for the ?root built-in: [#assign r = content?root] Just this assignment results in the same error message: Can't get parent of I18nContentWrapper for website:/[rep:root]:root node doesn't have a parent This bug was previously discussed on the Magnolia User-List: http://old.nabble.com/Problem-with-FreeMarker-built-in-for-ancestors-ts26334726.html -- 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] Updated: (MAGNOLIA- 2945) FreeMarker ?ancestors and ?root built-ins don't work
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nils Breunese updated MAGNOLIA-2945:
Description:
I wanted to use the FreeMarker ?ancestors built-in
(http://freemarker.sourceforge.net/docs/ref_builtins_node.html) in a FreeMarker
template. However, it doesn't seem to work. I added this:
{code}[#assign ancs = content?ancestors]{code}
But just this statement results in the following error:
{noformat}Can't get parent of I18nContentWrapper for website:/[rep:root]:root
node doesn't have a parent{noformat}
I found the same goes for the ?root built-in:
{code}[#assign r = content?root]{code}
Just this assignment results in the same error message:
{noformat}Can't get parent of I18nContentWrapper for website:/[rep:root]:root
node doesn't have a parent{noformat}
This bug was previously discussed on the Magnolia User-List:
http://old.nabble.com/Problem-with-FreeMarker-built-in-for-ancestors-ts26334726.html
was:
I wanted to use the FreeMarker ?ancestors built-in
(http://freemarker.sourceforge.net/docs/ref_builtins_node.html) in a FreeMarker
template. However, it doesn't seem to work. I added this:
[#assign ancs = content?ancestors]
But just this statement results in:
Can't get parent of I18nContentWrapper for website:/[rep:root]:root node
doesn't have a parent
I found the same goes for the ?root built-in:
[#assign r = content?root]
Just this assignment results in the same error message:
Can't get parent of I18nContentWrapper for website:/[rep:root]:root node
doesn't have a parent
This bug was previously discussed on the Magnolia User-List:
http://old.nabble.com/Problem-with-FreeMarker-built-in-for-ancestors-ts26334726.html
> FreeMarker ?ancestors and ?root built-ins don't work
>
>
> Key: MAGNOLIA-2945
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2945
> Project: Magnolia
> Issue Type: Bug
> Components: templating
>Affects Versions: 4.1.1
>Reporter: Nils Breunese
>Assignee: Philipp Bärfuss
>
> I wanted to use the FreeMarker ?ancestors built-in
> (http://freemarker.sourceforge.net/docs/ref_builtins_node.html) in a
> FreeMarker template. However, it doesn't seem to work. I added this:
> {code}[#assign ancs = content?ancestors]{code}
> But just this statement results in the following error:
> {noformat}Can't get parent of I18nContentWrapper for website:/[rep:root]:root
> node doesn't have a parent{noformat}
> I found the same goes for the ?root built-in:
> {code}[#assign r = content?root]{code}
> Just this assignment results in the same error message:
> {noformat}Can't get parent of I18nContentWrapper for website:/[rep:root]:root
> node doesn't have a parent{noformat}
> This bug was previously discussed on the Magnolia User-List:
> http://old.nabble.com/Problem-with-FreeMarker-built-in-for-ancestors-ts26334726.html
--
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-3005) Content does not correctly implement equals()
Content does not correctly implement equals()
-
Key: MAGNOLIA-3005
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3005
Project: Magnolia
Issue Type: Bug
Components: core
Affects Versions: 4.2.3
Reporter: Nils Breunese
Assignee: Philipp Bärfuss
The Content class does not seem to correctly implement an equals() method.
Running the following Groovy code via the Groovy Shell returns false, while I
am pretty sure it should return true.
{code:title=ContentEqualsTest.groovy}
import info.magnolia.cms.util.*
def repository = "website"
def path = "/demo-project"
def c1 = ContentUtil.getContent(repository, path)
def c2 = ContentUtil.getContent(repository, path)
return c1.equals(c2)
{code}
Correctly implementing equals() and hashCode() is pretty important for working
with objects like these. I ran into this bug while filling a Set with
references to pages and noting that the same page was in the Set multiple
times. I haven't checked if there are more objects that do not correctly
implement equals() and/or hashCode(), but there may be more.
--
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: (MGNLSTK-575) Add a parameters map to the Site class
Add a parameters map to the Site class -- Key: MGNLSTK-575 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-575 Project: Magnolia Standard Templating Kit Issue Type: Improvement Affects Versions: 1.2.1 Reporter: Nils Breunese Assignee: Philipp Bärfuss Attachments: Site.java.patch Unlike for paragraphs/templates there is no parameters map for the STK Site class. If this is added it can be used to store site-wide settings, which would be very handy. -- 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: (MGNLSTK-533) pur integration in templating kit breaks with external users.
[
http://jira.magnolia-cms.com/browse/MGNLSTK-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26266#action_26266
]
Nils Breunese commented on MGNLSTK-533:
---
Yep, it works on updates, not on fresh installs. Just ran into that problem...
> pur integration in templating kit breaks with external users.
> -
>
> Key: MGNLSTK-533
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-533
> Project: Magnolia Standard Templating Kit
> Issue Type: Bug
> Components: paragraphs
>Reporter: Rico Jansen
>Assignee: Federico Grilli
> Fix For: 1.2.2, 1.2.3, 1.3
>
> Attachments: freemarker-user-unsupportedexception.patch,
> link-ftl.patch, user-model.patch
>
>
> I have an issue with an exception that occurs when I log in with an LDAP
> account,
> the adminInterface works fine , but the site gives an exception:
> 2009-11-20 11:00:31,969 ERROR freemarker.runtime
> :
> Method public java.lang.String
> info.magnolia.cms.security.ExternalUser.getProperty(java.lang.String) threw
> an exception when invoked on info.magnolia.cms.security.externalu...@11fde0
> The problematic instruction:
> --
> ==> assignment: userFullName=ctx.user.getProperty("title")!userName [on line
> 4, column 1 in templating-kit/paragraphs/pur/link.ftl]
> --
> Java backtrace for programmers:
> --
> freemarker.template.TemplateModelException: Method public java.lang.String
> info.magnolia.cms.security.ExternalUser.getProperty(java.lang.String) threw
> an exception when invoked on info.magnolia.cms.security.externalu...@11fde0
> at freemarker.ext.beans.SimpleMethodModel.exec(SimpleMethodModel.java:130)
> at freemarker.core.MethodCall._getAsTemplateModel(MethodCall.java:93)
> at freemarker.core.Expression.getAsTemplateModel(Expression.java:89)
> at
> freemarker.core.DefaultToExpression._getAsTemplateModel(DefaultToExpression.java:100)
> Caused by: java.lang.UnsupportedOperationException: not implemented for this
> ExternalUser
> at
> info.magnolia.cms.security.ExternalUser.getProperty(ExternalUser.java:155)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> It seems that the / templating-kit/paragraphs/pur/link.ftl tries to get the
> fullname from an external user:
> [#assign userFullName = ctx.user.getProperty("title")!userName]
> But ExternalUser has this as
> its getProperty:
> public String getProperty(String propertyName) {
> throw new UnsupportedOperationException("not implemented for this
> ExternalUser");
> }
> I am currently runing Magnolia Enterprise Edition 4.1RC1 and
> Templating Kit Standard 1.2RC2 , Extended 1.2RC1
--
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: (MGNLSTK-533) pur integration in templating kit breaks with external users.
[
http://jira.magnolia-cms.com/browse/MGNLSTK-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26339#action_26339
]
Nils Breunese commented on MGNLSTK-533:
---
After upgrading to STK 1.2.3 this problem still seems to be present when using
the commenting module with external users.
Method public java.lang.String
info.magnolia.cms.security.ExternalUser.getProperty(java.lang.String) threw an
exception when invoked on info.magnolia.cms.security.externalu...@1d5d81a
The problematic instruction:
--
==> ${ctx.user.getProperty('email')!''} [on line 93, column 89 in
info/magnolia/module/commenting/frontend/comment.inc.ftl]
in user-directive messageform [on line 60, column 5 in
info/magnolia/module/commenting/frontend/commentPreview.ftl]
--
(...)
Caused by: java.lang.UnsupportedOperationException: not implemented for this
ExternalUser
> pur integration in templating kit breaks with external users.
> -
>
> Key: MGNLSTK-533
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-533
> Project: Magnolia Standard Templating Kit
> Issue Type: Bug
> Components: paragraphs
>Reporter: Rico Jansen
>Assignee: Federico Grilli
> Fix For: 1.2.2, 1.2.3, 1.3
>
> Attachments: freemarker-user-unsupportedexception.patch,
> link-ftl.patch, user-model.patch
>
>
> I have an issue with an exception that occurs when I log in with an LDAP
> account,
> the adminInterface works fine , but the site gives an exception:
> 2009-11-20 11:00:31,969 ERROR freemarker.runtime
> :
> Method public java.lang.String
> info.magnolia.cms.security.ExternalUser.getProperty(java.lang.String) threw
> an exception when invoked on info.magnolia.cms.security.externalu...@11fde0
> The problematic instruction:
> --
> ==> assignment: userFullName=ctx.user.getProperty("title")!userName [on line
> 4, column 1 in templating-kit/paragraphs/pur/link.ftl]
> --
> Java backtrace for programmers:
> --
> freemarker.template.TemplateModelException: Method public java.lang.String
> info.magnolia.cms.security.ExternalUser.getProperty(java.lang.String) threw
> an exception when invoked on info.magnolia.cms.security.externalu...@11fde0
> at freemarker.ext.beans.SimpleMethodModel.exec(SimpleMethodModel.java:130)
> at freemarker.core.MethodCall._getAsTemplateModel(MethodCall.java:93)
> at freemarker.core.Expression.getAsTemplateModel(Expression.java:89)
> at
> freemarker.core.DefaultToExpression._getAsTemplateModel(DefaultToExpression.java:100)
> Caused by: java.lang.UnsupportedOperationException: not implemented for this
> ExternalUser
> at
> info.magnolia.cms.security.ExternalUser.getProperty(ExternalUser.java:155)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> It seems that the / templating-kit/paragraphs/pur/link.ftl tries to get the
> fullname from an external user:
> [#assign userFullName = ctx.user.getProperty("title")!userName]
> But ExternalUser has this as
> its getProperty:
> public String getProperty(String propertyName) {
> throw new UnsupportedOperationException("not implemented for this
> ExternalUser");
> }
> I am currently runing Magnolia Enterprise Edition 4.1RC1 and
> Templating Kit Standard 1.2RC2 , Extended 1.2RC1
--
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] Issue Comment Edited: (MGNLSTK-533) pur integration in templating kit breaks with external users.
[
http://jira.magnolia-cms.com/browse/MGNLSTK-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26339#action_26339
]
Nils Breunese edited comment on MGNLSTK-533 at 2/3/10 4:58 PM:
---
After upgrading to STK 1.2.3 this problem still seems to be present when using
the commenting module with external users (LDAP).
Method public java.lang.String
info.magnolia.cms.security.ExternalUser.getProperty(java.lang.String) threw an
exception when invoked on info.magnolia.cms.security.externalu...@1d5d81a
The problematic instruction:
--
==> ${ctx.user.getProperty('email')!''} [on line 93, column 89 in
info/magnolia/module/commenting/frontend/comment.inc.ftl]
in user-directive messageform [on line 60, column 5 in
info/magnolia/module/commenting/frontend/commentPreview.ftl]
--
(...)
Caused by: java.lang.UnsupportedOperationException: not implemented for this
ExternalUser
was (Author: breun):
After upgrading to STK 1.2.3 this problem still seems to be present when
using the commenting module with external users.
Method public java.lang.String
info.magnolia.cms.security.ExternalUser.getProperty(java.lang.String) threw an
exception when invoked on info.magnolia.cms.security.externalu...@1d5d81a
The problematic instruction:
--
==> ${ctx.user.getProperty('email')!''} [on line 93, column 89 in
info/magnolia/module/commenting/frontend/comment.inc.ftl]
in user-directive messageform [on line 60, column 5 in
info/magnolia/module/commenting/frontend/commentPreview.ftl]
--
(...)
Caused by: java.lang.UnsupportedOperationException: not implemented for this
ExternalUser
> pur integration in templating kit breaks with external users.
> -
>
> Key: MGNLSTK-533
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-533
> Project: Magnolia Standard Templating Kit
> Issue Type: Bug
> Components: paragraphs
>Reporter: Rico Jansen
>Assignee: Federico Grilli
> Fix For: 1.2.2, 1.2.3, 1.3
>
> Attachments: freemarker-user-unsupportedexception.patch,
> link-ftl.patch, user-model.patch
>
>
> I have an issue with an exception that occurs when I log in with an LDAP
> account,
> the adminInterface works fine , but the site gives an exception:
> 2009-11-20 11:00:31,969 ERROR freemarker.runtime
> :
> Method public java.lang.String
> info.magnolia.cms.security.ExternalUser.getProperty(java.lang.String) threw
> an exception when invoked on info.magnolia.cms.security.externalu...@11fde0
> The problematic instruction:
> --
> ==> assignment: userFullName=ctx.user.getProperty("title")!userName [on line
> 4, column 1 in templating-kit/paragraphs/pur/link.ftl]
> --
> Java backtrace for programmers:
> --
> freemarker.template.TemplateModelException: Method public java.lang.String
> info.magnolia.cms.security.ExternalUser.getProperty(java.lang.String) threw
> an exception when invoked on info.magnolia.cms.security.externalu...@11fde0
> at freemarker.ext.beans.SimpleMethodModel.exec(SimpleMethodModel.java:130)
> at freemarker.core.MethodCall._getAsTemplateModel(MethodCall.java:93)
> at freemarker.core.Expression.getAsTemplateModel(Expression.java:89)
> at
> freemarker.core.DefaultToExpression._getAsTemplateModel(DefaultToExpression.java:100)
> Caused by: java.lang.UnsupportedOperationException: not implemented for this
> ExternalUser
> at
> info.magnolia.cms.security.ExternalUser.getProperty(ExternalUser.java:155)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> It seems that the / templating-kit/paragraphs/pur/link.ftl tries to get the
> fullname from an external user:
> [#assign userFullName = ctx.user.getProperty("title")!userName]
> But ExternalUser has this as
> its getProperty:
> public String getProperty(String propertyName) {
> throw new UnsupportedOperationException("not implemented for this
> ExternalUser");
> }
> I am currently runing Magnolia Enterprise Edition 4.1RC1 and
> Templating Kit Standard 1.2RC2 , Extended 1.2RC1
--
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: (MGNLSTK-533) pur integration in templating kit breaks with external users.
[
http://jira.magnolia-cms.com/browse/MGNLSTK-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26347#action_26347
]
Nils Breunese commented on MGNLSTK-533:
---
According to my colleague (who is working on the commenting, but not at work
today) the email field should be mapped from LDAP, so it's too bad that the
method throws an UnsupportedOperationException.
We plan on going live with our first Magnolia-powered site in March and it
would be nice if this could be fixed before then...
> pur integration in templating kit breaks with external users.
> -
>
> Key: MGNLSTK-533
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-533
> Project: Magnolia Standard Templating Kit
> Issue Type: Bug
> Components: paragraphs
>Reporter: Rico Jansen
>Assignee: Federico Grilli
> Fix For: 1.2.2, 1.2.3, 1.3
>
> Attachments: freemarker-user-unsupportedexception.patch,
> link-ftl.patch, user-model.patch
>
>
> I have an issue with an exception that occurs when I log in with an LDAP
> account,
> the adminInterface works fine , but the site gives an exception:
> 2009-11-20 11:00:31,969 ERROR freemarker.runtime
> :
> Method public java.lang.String
> info.magnolia.cms.security.ExternalUser.getProperty(java.lang.String) threw
> an exception when invoked on info.magnolia.cms.security.externalu...@11fde0
> The problematic instruction:
> --
> ==> assignment: userFullName=ctx.user.getProperty("title")!userName [on line
> 4, column 1 in templating-kit/paragraphs/pur/link.ftl]
> --
> Java backtrace for programmers:
> --
> freemarker.template.TemplateModelException: Method public java.lang.String
> info.magnolia.cms.security.ExternalUser.getProperty(java.lang.String) threw
> an exception when invoked on info.magnolia.cms.security.externalu...@11fde0
> at freemarker.ext.beans.SimpleMethodModel.exec(SimpleMethodModel.java:130)
> at freemarker.core.MethodCall._getAsTemplateModel(MethodCall.java:93)
> at freemarker.core.Expression.getAsTemplateModel(Expression.java:89)
> at
> freemarker.core.DefaultToExpression._getAsTemplateModel(DefaultToExpression.java:100)
> Caused by: java.lang.UnsupportedOperationException: not implemented for this
> ExternalUser
> at
> info.magnolia.cms.security.ExternalUser.getProperty(ExternalUser.java:155)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> It seems that the / templating-kit/paragraphs/pur/link.ftl tries to get the
> fullname from an external user:
> [#assign userFullName = ctx.user.getProperty("title")!userName]
> But ExternalUser has this as
> its getProperty:
> public String getProperty(String propertyName) {
> throw new UnsupportedOperationException("not implemented for this
> ExternalUser");
> }
> I am currently runing Magnolia Enterprise Edition 4.1RC1 and
> Templating Kit Standard 1.2RC2 , Extended 1.2RC1
--
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: (MGNLSTK-582) Support for auto-generated paragraphs in all extras columns
Support for auto-generated paragraphs in all extras columns --- Key: MGNLSTK-582 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-582 Project: Magnolia Standard Templating Kit Issue Type: Improvement Affects Versions: 1.2.3 Reporter: Nils Breunese Assignee: Philipp Bärfuss Attachments: autogeneratedparagraphs-support-for-extras-columns.tar.gz I have implemented custom versions of the AutoGeneratedExtrasArea and SingletonParagraphTemplateModel classes (and added an ExtrasColumn class) so now we are able to configure auto-generated paragraphs for specific columns in the extrasArea. Currently all auto-generated paragraphs go into extras1, which is too limited for our current project. For example we can now configure a template like this: templateName extrasArea extrasColumns extras2 autoGeneratedParagraphs someParagraph defaultValues someKey1: someValue1 someKey2: someValue2 name: someParagraph class: (custom).ExtrasColumn class: (custom).AutoGeneratedExtrasArea columns: 2 modelClass: (custom).SingletonParagraphTemplateModel Along the way I have also changed createMainArea, so it is not necessary to have an auto-generated paragraph in the main area when you want an auto-generated paragraph in the extrasArea. -- 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-3075) Opening a page from Admin Central does not honor the defaultExtension
Opening a page from Admin Central does not honor the defaultExtension - Key: MAGNOLIA-3075 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3075 Project: Magnolia Issue Type: Bug Components: admininterface Affects Versions: 4.2.3 Reporter: Nils Breunese Assignee: Philipp Bärfuss Priority: Minor When opening a page from the Website menu in Admin Central the page opens with an '.html' extension, even when config:/server/defaultExtension is set to another extension. -- 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-3738) Watch Log4j configuration for live changes
Watch Log4j configuration for live changes -- Key: MAGNOLIA-3738 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3738 Project: Magnolia Issue Type: Improvement Affects Versions: 4.4.4 Reporter: Nils Breunese info.magnolia.logging.Log4jConfigurer uses DOMConfigurator.configure(Element element) and PropertyConfigurator.configure(Properties properties), so the Log4j configuration is read once, but when we want to change the configuration, for instance to debug a problem on a production instance, we need to restart our Magnolia instances. If would be nice if the configureAndWatch(String configFilename) methods could be used instead, so changes to the Log4j configuration do not require restarting Magnolia. -- 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-3843) Cannot find MIME type for extension "html;jsessionid=(...)"
Cannot find MIME type for extension "html;jsessionid=(...)" --- Key: MAGNOLIA-3843 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3843 Project: Magnolia Issue Type: Bug Security Level: Public Affects Versions: 4.4.5 Reporter: Nils Breunese When logging into AdminCentral on a Magnolia 4.4.5 author instance, a jsessionid is added to the URL, whereas it was not before (4.4.4). It seems info.magnolia.cms.beans.config.MIMEMapping does not handle that too well: 2011-09-21 11:24:10,894 INFO info.magnolia.cms.beans.config.MIMEMapping : Cannot find MIME type for extension "html;jsessionid=9856D899C20D654FBCE6E7DE1C720350" -- 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/community/mailing-lists.html To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MAGNOLIA-4955) It should not be possible to move a page to a location where it can't be created
Nils Breunese created MAGNOLIA-4955 It should not be possible to move a page to a location where it can't be created Issue Type: Bug Affects Versions: 4.4.9 Assignee: Unassigned Components: admininterface Created: 05/Apr/13 1:35 PM Description: We use template availability per site to define the structure of a site. However, editors can easily subvert this mechanism by creating a page with a certain template and then moving that page to a location where creating a page with that template is not allowed. (And yes, our editors are doing this all the time.) I feel Admin Central should not allow moving a page to a location where that page's template is not available. Project: Magnolia Labels: vpro Priority: Neutral Reporter: Nils Breunese Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira 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:
