[magnolia-dev] [JIRA] Updated: (MGNLUI-390) Users are created under root after a deletion happens
[ http://jira.magnolia-cms.com/browse/MGNLUI-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MGNLUI-390: --- Fix Version/s: 5.0 Alpha2 s011 (was: 5.0 Alpha1 s010) Too late, put off to next sprint Users are created under root after a deletion happens - Key: MGNLUI-390 URL: http://jira.magnolia-cms.com/browse/MGNLUI-390 Project: Magnolia UI Issue Type: Bug Security Level: Public Components: content app, security app Affects Versions: 5.0 Alpha1 s009 Reporter: Federico Grilli Priority: Critical Fix For: 5.0 Alpha2 s011 To reproduce - create a user - delete it - create a new one - for some reason (likely related to http://jira.magnolia-cms.com/browse/MGNLUI-315) the selected workbench path is root which is wrong, whereas it should either be /admin or /system - no UI feedback is given to the poor user which is left wondering why that does not work - the only way to make it work is restarting the app or switching views -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLUI-391) Fullscreen in tabbed editing broken
Fullscreen in tabbed editing broken --- Key: MGNLUI-391 URL: http://jira.magnolia-cms.com/browse/MGNLUI-391 Project: Magnolia UI Issue Type: Bug Security Level: Public Affects Versions: 5.0 Alpha1 s010 Reporter: Espen Jervidalo Fix For: 5.0 Alpha2 s011 When switching to fullscreen view when in tabbed editing the tabsheet is calculating height and position wrong. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLUI-388) Config app: missing the possibility to add an mgnl:content
[ http://jira.magnolia-cms.com/browse/MGNLUI-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MGNLUI-388: --- Description: To recap: - initial state (root selected) -- can add folder, contentNode, property - folder selected -- can add folder, contentNode, property -- can delete folder - contentNode selected -- can add contentNode, property -- can delete contentNode - property selected -- can delete contentNode was:fix ready locally Config app: missing the possibility to add an mgnl:content Key: MGNLUI-388 URL: http://jira.magnolia-cms.com/browse/MGNLUI-388 Project: Magnolia UI Issue Type: Bug Security Level: Public Affects Versions: 5.0 Alpha1 Reporter: Federico Grilli Assignee: Federico Grilli Priority: Critical Fix For: 5.0 Alpha1 To recap: - initial state (root selected) -- can add folder, contentNode, property - folder selected -- can add folder, contentNode, property -- can delete folder - contentNode selected -- can add contentNode, property -- can delete contentNode - property selected -- can delete contentNode -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLUI-388) Config app: missing the possibility to add an mgnl:content
[ http://jira.magnolia-cms.com/browse/MGNLUI-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MGNLUI-388: --- Description: To recap: - initial state (root selected) -- can add folder, contentNode, property - folder selected -- can add folder, contentNode, property -- can delete folder - contentNode selected -- can add contentNode, property -- can delete contentNode - property selected -- can delete property was: To recap: - initial state (root selected) -- can add folder, contentNode, property - folder selected -- can add folder, contentNode, property -- can delete folder - contentNode selected -- can add contentNode, property -- can delete contentNode - property selected -- can delete contentNode Config app: missing the possibility to add an mgnl:content Key: MGNLUI-388 URL: http://jira.magnolia-cms.com/browse/MGNLUI-388 Project: Magnolia UI Issue Type: Bug Security Level: Public Affects Versions: 5.0 Alpha1 Reporter: Federico Grilli Assignee: Federico Grilli Priority: Critical Fix For: 5.0 Alpha1 To recap: - initial state (root selected) -- can add folder, contentNode, property - folder selected -- can add folder, contentNode, property -- can delete folder - contentNode selected -- can add contentNode, property -- can delete contentNode - property selected -- can delete property -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLSTK-1053) CLONE -JavaScript Libraries should be updated to latest versions to fix issues related to Chrome 16.0 release and possibly other WebKit based browsers
CLONE -JavaScript Libraries should be updated to latest versions to fix issues related to Chrome 16.0 release and possibly other WebKit based browsers -- Key: MGNLSTK-1053 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1053 Project: Magnolia Standard Templating Kit Issue Type: Task Components: templates Affects Versions: 2.0 Environment: Mac OS X 10.6.8, Google Chrome 16.0.912.63 Reporter: Jaroslav Simak Assignee: Jaroslav Simak Priority: Critical Fix For: 2.0.7 Hi, While working on some theme development using the STK 2.0 Static Prototype, I came across a couple issues with the JS libs that are currently shipped with the STK. Both issues relate to changes in the Google Chrome 16.0 release, and have been resolved recently by jQuery and Webshims Lib. I've updated my local copies of jQuery to 1.7.1 and Webshims Lib to 1.8.4. I've done some preliminary regression testing in the STK 2.0 Static Prototype. Everything seems to be fine. Here are the links to the related issues for jQuery and Webshims lib: h2.jQuery Issue * [Ticket #10531 CONSIDER REMOVING LAYERX AND LAYERY FROM $.EVENT.PROPS|http://bugs.jquery.com/ticket/10531] h2. Webshims Lib Issues * [#66 INVALID_STATE_ERR with Chrome 16|https://github.com/aFarkas/webshim/issues/66] * [#73 DOM Exception thrown in Chrome 16.0.912.21 beta-m|https://github.com/aFarkas/webshim/issues/74] h2. Download Links: * [jQuery 1.7.1|http://code.jquery.com/jquery-1.7.1.min.js] * [Webshims lib 1.8.4|https://github.com/aFarkas/webshim/downloads] Please let me know if you have any questions. Cheers, Matt -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSTK-1053) CLONE -JavaScript Libraries should be updated to latest versions to fix issues related to Chrome 16.0 release and possibly other WebKit based browsers
[ http://jira.magnolia-cms.com/browse/MGNLSTK-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Simak updated MGNLSTK-1053: Fix Version/s: 2.5 (was: 2.0.7) CLONE -JavaScript Libraries should be updated to latest versions to fix issues related to Chrome 16.0 release and possibly other WebKit based browsers -- Key: MGNLSTK-1053 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1053 Project: Magnolia Standard Templating Kit Issue Type: Task Components: templates Affects Versions: 2.0 Environment: Mac OS X 10.6.8, Google Chrome 16.0.912.63 Reporter: Jaroslav Simak Assignee: Jaroslav Simak Priority: Critical Fix For: 2.5 Hi, While working on some theme development using the STK 2.0 Static Prototype, I came across a couple issues with the JS libs that are currently shipped with the STK. Both issues relate to changes in the Google Chrome 16.0 release, and have been resolved recently by jQuery and Webshims Lib. I've updated my local copies of jQuery to 1.7.1 and Webshims Lib to 1.8.4. I've done some preliminary regression testing in the STK 2.0 Static Prototype. Everything seems to be fine. Here are the links to the related issues for jQuery and Webshims lib: h2.jQuery Issue * [Ticket #10531 CONSIDER REMOVING LAYERX AND LAYERY FROM $.EVENT.PROPS|http://bugs.jquery.com/ticket/10531] h2. Webshims Lib Issues * [#66 INVALID_STATE_ERR with Chrome 16|https://github.com/aFarkas/webshim/issues/66] * [#73 DOM Exception thrown in Chrome 16.0.912.21 beta-m|https://github.com/aFarkas/webshim/issues/74] h2. Download Links: * [jQuery 1.7.1|http://code.jquery.com/jquery-1.7.1.min.js] * [Webshims lib 1.8.4|https://github.com/aFarkas/webshim/downloads] Please let me know if you have any questions. Cheers, Matt -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLCACHE-1) Update pom.xml
Update pom.xml -- Key: MGNLCACHE-1 URL: http://jira.magnolia-cms.com/browse/MGNLCACHE-1 Project: Magnolia Cache Module Issue Type: Task Reporter: Federico Grilli Assignee: Federico Grilli Priority: Critical Fix For: 5.0 Alpha1 As the cache module has moved away from the main project and has become an independent CE module, we need to change its parent pom, groupId, scm info, dependencies etc -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4720) High CPU consumption on idle AdminCentral
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Lipp updated MAGNOLIA-4720: -- Fix Version/s: 5.0 Alpha2 s011 (was: 5.0 Alpha1) High CPU consumption on idle AdminCentral - Key: MAGNOLIA-4720 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4720 Project: Magnolia Issue Type: Bug Security Level: Public Components: admininterface Affects Versions: 5.0 Alpha1 Reporter: Jan Haderka Priority: Critical Fix For: 5.0 Alpha2 s011 Login to AdminCentral using Safari, open Config app, expand tree to 2nd-3rd level and open Activity Monitor. Safari will suddenly use 20-30% of CPU even when nothing is being done w/ AdminCentral and even when it's not focused. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLIMG-97) activate caching for generated images in the admin central
[ http://jira.magnolia-cms.com/browse/MGNLIMG-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Lipp updated MGNLIMG-97: --- Assignee: (was: Grégory Joseph) Fix Version/s: 2.3 Alpha2 s011 (was: 2.3 Alpha1) activate caching for generated images in the admin central -- Key: MGNLIMG-97 URL: http://jira.magnolia-cms.com/browse/MGNLIMG-97 Project: Magnolia Imaging Module Issue Type: Task Affects Versions: 2.3 Alpha1 Reporter: Espen Jervidalo Fix For: 2.3 Alpha2 s011 Currently the generated images are not beeing cached by magnolia, this should be fixed. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSTK-1048) Previewing Demo-Project doesn't render Magnolia Logo in the upper left anymore
[ http://jira.magnolia-cms.com/browse/MGNLSTK-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Espen Jervidalo updated MGNLSTK-1048: - Assignee: (was: Espen Jervidalo) Fix Version/s: 2.5 Alpha2 s011 (was: 2.5 Alpha1) Previewing Demo-Project doesn't render Magnolia Logo in the upper left anymore -- Key: MGNLSTK-1048 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1048 Project: Magnolia Standard Templating Kit Issue Type: Bug Affects Versions: 2.5 Alpha1 Reporter: Daniel Lipp Priority: Critical Fix For: 2.5 Alpha2 s011 Attachments: Screen Shot 2012-12-06 at 11.22.51.jpg -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLUI-393) Profile/Review size management of MagnoliaShell, viewports, tabsheet and forms.
Profile/Review size management of MagnoliaShell, viewports, tabsheet and forms. --- Key: MGNLUI-393 URL: http://jira.magnolia-cms.com/browse/MGNLUI-393 Project: Magnolia UI Issue Type: Task Security Level: Public Affects Versions: 5.0 Alpha2 s011 Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev Priority: Major Fix For: 5.0 Alpha2 s011 -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLUI-392) Allow tree view to keep the JCR order of nodes
Allow tree view to keep the JCR order of nodes -- Key: MGNLUI-392 URL: http://jira.magnolia-cms.com/browse/MGNLUI-392 Project: Magnolia UI Issue Type: Improvement Security Level: Public Components: configuration, content app Affects Versions: 5.0 Alpha1 Reporter: Jozef Chocholacek Priority: Major In the Config App, the nodes are sorted alphabetically - but e.g. for filters, the native JCR order is needed to be clear in which order are they applied. And there are more places where the order (the JCR one) of nodes is important. So the TreeView in workbench must allow to be turned to keep JCR order mode. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLUI-393) Profile/Review size management of MagnoliaShell, viewports, tabsheet and forms.
[ http://jira.magnolia-cms.com/browse/MGNLUI-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Espen Jervidalo updated MGNLUI-393: --- Attachment: Screen Shot 2012-12-11 at 1.41.25 PM.png Screen Shot 2012-12-11 at 1.41.42 PM.png Profile/Review size management of MagnoliaShell, viewports, tabsheet and forms. --- Key: MGNLUI-393 URL: http://jira.magnolia-cms.com/browse/MGNLUI-393 Project: Magnolia UI Issue Type: Task Security Level: Public Affects Versions: 5.0 Alpha2 s011 Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev Priority: Major Fix For: 5.0 Alpha2 s011 Attachments: Screen Shot 2012-12-11 at 1.41.25 PM.png, Screen Shot 2012-12-11 at 1.41.42 PM.png An example in the tabsheet an a simple hello world app. Opening a subApp and switching to another app, e.g. contacts, and back will make the current tab set the height to 0 and the content will not be visible anymore. See screenshots. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLUI-393) Profile/Review size management of MagnoliaShell, viewports, tabsheet and forms.
[ http://jira.magnolia-cms.com/browse/MGNLUI-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Espen Jervidalo updated MGNLUI-393: --- Description: An example in the tabsheet an a simple hello world app. Opening a subApp and switching to another app, e.g. contacts, and back will make the current tab set the height to 0 and the content will not be visible anymore. See screenshots. Profile/Review size management of MagnoliaShell, viewports, tabsheet and forms. --- Key: MGNLUI-393 URL: http://jira.magnolia-cms.com/browse/MGNLUI-393 Project: Magnolia UI Issue Type: Task Security Level: Public Affects Versions: 5.0 Alpha2 s011 Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev Priority: Major Fix For: 5.0 Alpha2 s011 Attachments: Screen Shot 2012-12-11 at 1.41.25 PM.png, Screen Shot 2012-12-11 at 1.41.42 PM.png An example in the tabsheet an a simple hello world app. Opening a subApp and switching to another app, e.g. contacts, and back will make the current tab set the height to 0 and the content will not be visible anymore. See screenshots. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLUI-394) Metadata properties (mgnl:*) are editable
Metadata properties (mgnl:*) are editable - Key: MGNLUI-394 URL: http://jira.magnolia-cms.com/browse/MGNLUI-394 Project: Magnolia UI Issue Type: Bug Security Level: Public Components: configuration Affects Versions: 5.0 Alpha1 Reporter: Jozef Chocholacek The metadata properties like mgnl:created, mgnl:lastModifiedBy etc. are editable - that shouldn't be possible, IMO. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLUI-395) Allow to show/hide metadata properties
Allow to show/hide metadata properties -- Key: MGNLUI-395 URL: http://jira.magnolia-cms.com/browse/MGNLUI-395 Project: Magnolia UI Issue Type: New Feature Security Level: Public Components: configuration, tree/list Reporter: Jozef Chocholacek It'd be nice to have a Show Metadata button in the Config App (or in a JCR Browser kind of apps), that will turn on/off the (read-only!) display of metadata properties like mgnl:created, mgnl:template, ... maybe even jcr:* properties. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLUI-396) AbstractSubApp: getCurrentLocation should return DefaultLocation
[ http://jira.magnolia-cms.com/browse/MGNLUI-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Espen Jervidalo updated MGNLUI-396: --- Summary: AbstractSubApp: getCurrentLocation should return DefaultLocation (was: AbstractSubApp: make it return DefaultLocation) AbstractSubApp: getCurrentLocation should return DefaultLocation Key: MGNLUI-396 URL: http://jira.magnolia-cms.com/browse/MGNLUI-396 Project: Magnolia UI Issue Type: Task Security Level: Public Affects Versions: 5.0 Alpha1 Reporter: Espen Jervidalo Fix For: 5.0 Alpha2 s011 This will ease location handling in implementers of this Class. Currently the Location-Interface is returned and one has to cast to get the right getters. moving the DefaultLocations getters to the interface may also be a solution. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLUI-396) AbstractSubApp: make it return DefaultLocation
AbstractSubApp: make it return DefaultLocation -- Key: MGNLUI-396 URL: http://jira.magnolia-cms.com/browse/MGNLUI-396 Project: Magnolia UI Issue Type: Task Security Level: Public Affects Versions: 5.0 Alpha1 Reporter: Espen Jervidalo Fix For: 5.0 Alpha2 s011 This will ease location handling in implementers of this Class. Currently the Location-Interface is returned and one has to cast to get the right getters. moving the DefaultLocations getters to the interface may also be a solution. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4713) When sharing a page in Facebook, cached pages are working, while uncached pages cannot be retrieved by Facebook
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka updated MAGNOLIA-4713: -- Assignee: (was: Philipp Bärfuss) Fix Version/s: 4.5.8 When sharing a page in Facebook, cached pages are working, while uncached pages cannot be retrieved by Facebook --- Key: MAGNOLIA-4713 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4713 Project: Magnolia Issue Type: Bug Security Level: Public Components: cache Affects Versions: 4.4.9, 4.5.6 Environment: Tomcat 7 Reporter: Tom Wespi Priority: Major Fix For: 4.5.8 Attachments: Screen Shot 2012-12-05 at 18.00.33.png, Screen Shot 2012-12-05 at 18.01.08.png Try to share http://demopublic.magnolia-cms.com/demo-project.html?test=test in your Facebook status - doesen't work http://demopublic.magnolia-cms.com/demo-project.html is 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLUI-397) Configuration app: selecting a property results in malfunctioning
Configuration app: selecting a property results in malfunctioning
-
Key: MGNLUI-397
URL: http://jira.magnolia-cms.com/browse/MGNLUI-397
Project: Magnolia UI
Issue Type: Bug
Security Level: Public
Components: content app
Affects Versions: 5.0 Alpha1
Reporter: Federico Grilli
Assignee: Espen Jervidalo
Priority: Major
Fix For: 5.0 Alpha2 s011
To reproduce it
* Expand {{server}} node and select {{mgnl:created}} property
* A WARN as the one pasted below will display
* From now on, the app no longer reacts to events, i.e. URI fragment or action
availability in action bar do not change if a different item is selected
* Closing the app results in a Vaadin's out-of-synch error
{code}
2012-12-11 14:24:28,702 WARN info.magnolia.ui.framework.event.SimpleEventBus
: Exception caught when dispatching event: No view type could be found for
[created]
java.lang.IllegalArgumentException: No view type could be found for [created]
at
info.magnolia.ui.admincentral.content.view.ContentView$ViewType.fromString(ContentView.java:83)
at
info.magnolia.ui.admincentral.app.content.location.ContentLocation.extractView(ContentLocation.java:101)
at
info.magnolia.ui.admincentral.app.content.location.ContentLocation.init(ContentLocation.java:55)
at
info.magnolia.ui.admincentral.app.content.location.ContentLocation.wrap(ContentLocation.java:131)
at
info.magnolia.ui.admincentral.app.content.AbstractContentSubApp.getCurrentLocation(AbstractContentSubApp.java:171)
at
info.magnolia.ui.admincentral.app.content.AbstractContentSubApp$1.onItemSelected(AbstractContentSubApp.java:188)
at
info.magnolia.ui.admincentral.event.ItemSelectedEvent.dispatch(ItemSelectedEvent.java:78)
at
info.magnolia.ui.admincentral.event.ItemSelectedEvent.dispatch(ItemSelectedEvent.java:1)
at
info.magnolia.ui.framework.event.SimpleEventBus.fireEvent(SimpleEventBus.java:76)
at
info.magnolia.ui.admincentral.content.view.ContentPresenter.onItemSelection(ContentPresenter.java:132)
at
info.magnolia.ui.admincentral.tree.view.TreeViewImpl.presenterOnItemSelection(TreeViewImpl.java:258)
at
info.magnolia.ui.admincentral.tree.view.TreeViewImpl.access$4(TreeViewImpl.java:256)
at
info.magnolia.ui.admincentral.tree.view.TreeViewImpl$2.valueChange(TreeViewImpl.java:132)
at sun.reflect.GeneratedMethodAccessor177.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.vaadin.event.ListenerMethod.receiveEvent(ListenerMethod.java:510)
at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:164)
at
com.vaadin.ui.AbstractComponent.fireEvent(AbstractComponent.java:1219)
at com.vaadin.ui.AbstractField.fireValueChange(AbstractField.java:897)
at com.vaadin.ui.AbstractField.setValue(AbstractField.java:529)
at com.vaadin.ui.AbstractSelect.setValue(AbstractSelect.java:670)
at com.vaadin.ui.Table.handleSelectedItems(Table.java:2391)
at com.vaadin.ui.Table.changeVariables(Table.java:2440)
at com.vaadin.ui.TreeTable.changeVariables(TreeTable.java:390)
at
info.magnolia.ui.vaadin.grid.MagnoliaTreeTable.changeVariables(MagnoliaTreeTable.java:61)
at
com.vaadin.terminal.gwt.server.AbstractCommunicationManager.changeVariables(AbstractCommunicationManager.java:1460)
at
com.vaadin.terminal.gwt.server.AbstractCommunicationManager.handleVariableBurst(AbstractCommunicationManager.java:1404)
at
com.vaadin.terminal.gwt.server.AbstractCommunicationManager.handleVariables(AbstractCommunicationManager.java:1329)
at
com.vaadin.terminal.gwt.server.AbstractCommunicationManager.doHandleUidlRequest(AbstractCommunicationManager.java:761)
at
com.vaadin.terminal.gwt.server.CommunicationManager.handleUidlRequest(CommunicationManager.java:323)
...
{code}
--
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
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLUI-397) Configuration app: selecting a property results in malfunctioning
[
http://jira.magnolia-cms.com/browse/MGNLUI-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Federico Grilli updated MGNLUI-397:
---
Description:
To reproduce it
* Expand {{server}} node and select {{mgnl:created}} property
* A WARN as the one pasted below will show up in the logs
* From now on, the app no longer reacts to events, i.e. URI fragment or action
availability in action bar do not change if a different item is selected
* Closing the app sometimes results in a Vaadin's out-of-synch error
{code}
2012-12-11 14:24:28,702 WARN info.magnolia.ui.framework.event.SimpleEventBus
: Exception caught when dispatching event: No view type could be found for
[created]
java.lang.IllegalArgumentException: No view type could be found for [created]
at
info.magnolia.ui.admincentral.content.view.ContentView$ViewType.fromString(ContentView.java:83)
at
info.magnolia.ui.admincentral.app.content.location.ContentLocation.extractView(ContentLocation.java:101)
at
info.magnolia.ui.admincentral.app.content.location.ContentLocation.init(ContentLocation.java:55)
at
info.magnolia.ui.admincentral.app.content.location.ContentLocation.wrap(ContentLocation.java:131)
at
info.magnolia.ui.admincentral.app.content.AbstractContentSubApp.getCurrentLocation(AbstractContentSubApp.java:171)
at
info.magnolia.ui.admincentral.app.content.AbstractContentSubApp$1.onItemSelected(AbstractContentSubApp.java:188)
at
info.magnolia.ui.admincentral.event.ItemSelectedEvent.dispatch(ItemSelectedEvent.java:78)
at
info.magnolia.ui.admincentral.event.ItemSelectedEvent.dispatch(ItemSelectedEvent.java:1)
at
info.magnolia.ui.framework.event.SimpleEventBus.fireEvent(SimpleEventBus.java:76)
at
info.magnolia.ui.admincentral.content.view.ContentPresenter.onItemSelection(ContentPresenter.java:132)
at
info.magnolia.ui.admincentral.tree.view.TreeViewImpl.presenterOnItemSelection(TreeViewImpl.java:258)
at
info.magnolia.ui.admincentral.tree.view.TreeViewImpl.access$4(TreeViewImpl.java:256)
at
info.magnolia.ui.admincentral.tree.view.TreeViewImpl$2.valueChange(TreeViewImpl.java:132)
at sun.reflect.GeneratedMethodAccessor177.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.vaadin.event.ListenerMethod.receiveEvent(ListenerMethod.java:510)
at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:164)
at
com.vaadin.ui.AbstractComponent.fireEvent(AbstractComponent.java:1219)
at com.vaadin.ui.AbstractField.fireValueChange(AbstractField.java:897)
at com.vaadin.ui.AbstractField.setValue(AbstractField.java:529)
at com.vaadin.ui.AbstractSelect.setValue(AbstractSelect.java:670)
at com.vaadin.ui.Table.handleSelectedItems(Table.java:2391)
at com.vaadin.ui.Table.changeVariables(Table.java:2440)
at com.vaadin.ui.TreeTable.changeVariables(TreeTable.java:390)
at
info.magnolia.ui.vaadin.grid.MagnoliaTreeTable.changeVariables(MagnoliaTreeTable.java:61)
at
com.vaadin.terminal.gwt.server.AbstractCommunicationManager.changeVariables(AbstractCommunicationManager.java:1460)
at
com.vaadin.terminal.gwt.server.AbstractCommunicationManager.handleVariableBurst(AbstractCommunicationManager.java:1404)
at
com.vaadin.terminal.gwt.server.AbstractCommunicationManager.handleVariables(AbstractCommunicationManager.java:1329)
at
com.vaadin.terminal.gwt.server.AbstractCommunicationManager.doHandleUidlRequest(AbstractCommunicationManager.java:761)
at
com.vaadin.terminal.gwt.server.CommunicationManager.handleUidlRequest(CommunicationManager.java:323)
...
{code}
was:
To reproduce it
* Expand {{server}} node and select {{mgnl:created}} property
* A WARN as the one pasted below will display
* From now on, the app no longer reacts to events, i.e. URI fragment or action
availability in action bar do not change if a different item is selected
* Closing the app results in a Vaadin's out-of-synch error
{code}
2012-12-11 14:24:28,702 WARN info.magnolia.ui.framework.event.SimpleEventBus
: Exception caught when dispatching event: No view type could be found for
[created]
java.lang.IllegalArgumentException: No view type could be found for [created]
at
info.magnolia.ui.admincentral.content.view.ContentView$ViewType.fromString(ContentView.java:83)
at
info.magnolia.ui.admincentral.app.content.location.ContentLocation.extractView(ContentLocation.java:101)
at
info.magnolia.ui.admincentral.app.content.location.ContentLocation.init(ContentLocation.java:55)
at
info.magnolia.ui.admincentral.app.content.location.ContentLocation.wrap(ContentLocation.java:131)
at
[magnolia-dev] [JIRA] Created: (MGNLUI-398) Add TwinColSelect field to the Showcase App
Add TwinColSelect field to the Showcase App --- Key: MGNLUI-398 URL: http://jira.magnolia-cms.com/browse/MGNLUI-398 Project: Magnolia UI Issue Type: Task Security Level: Public Reporter: Jozef Chocholacek Priority: Minor TwinColSelect field created in the Sprint 009 is not in the Showcase App yet. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLUI-397) Selecting a prefixed item results in malfunctioning
[
http://jira.magnolia-cms.com/browse/MGNLUI-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Federico Grilli updated MGNLUI-397:
---
Summary: Selecting a prefixed item results in malfunctioning (was:
Configuration app: selecting a property results in malfunctioning)
Description:
To reproduce it
* Open config app
* Expand {{server}} node and select {{mgnl:created}} property (okay, it should
not be there in the first place, anyways...)
* A WARN as the one pasted below will show up in the logs
* From now on, the app no longer reacts to events, i.e. URI fragment or action
availability in action bar do not change if a different item is selected
* Closing the app sometimes results in a Vaadin's out-of-synch error
{code}
2012-12-11 14:24:28,702 WARN info.magnolia.ui.framework.event.SimpleEventBus
: Exception caught when dispatching event: No view type could be found for
[created]
java.lang.IllegalArgumentException: No view type could be found for [created]
at
info.magnolia.ui.admincentral.content.view.ContentView$ViewType.fromString(ContentView.java:83)
at
info.magnolia.ui.admincentral.app.content.location.ContentLocation.extractView(ContentLocation.java:101)
at
info.magnolia.ui.admincentral.app.content.location.ContentLocation.init(ContentLocation.java:55)
at
info.magnolia.ui.admincentral.app.content.location.ContentLocation.wrap(ContentLocation.java:131)
at
info.magnolia.ui.admincentral.app.content.AbstractContentSubApp.getCurrentLocation(AbstractContentSubApp.java:171)
at
info.magnolia.ui.admincentral.app.content.AbstractContentSubApp$1.onItemSelected(AbstractContentSubApp.java:188)
at
info.magnolia.ui.admincentral.event.ItemSelectedEvent.dispatch(ItemSelectedEvent.java:78)
at
info.magnolia.ui.admincentral.event.ItemSelectedEvent.dispatch(ItemSelectedEvent.java:1)
at
info.magnolia.ui.framework.event.SimpleEventBus.fireEvent(SimpleEventBus.java:76)
at
info.magnolia.ui.admincentral.content.view.ContentPresenter.onItemSelection(ContentPresenter.java:132)
at
info.magnolia.ui.admincentral.tree.view.TreeViewImpl.presenterOnItemSelection(TreeViewImpl.java:258)
at
info.magnolia.ui.admincentral.tree.view.TreeViewImpl.access$4(TreeViewImpl.java:256)
at
info.magnolia.ui.admincentral.tree.view.TreeViewImpl$2.valueChange(TreeViewImpl.java:132)
at sun.reflect.GeneratedMethodAccessor177.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.vaadin.event.ListenerMethod.receiveEvent(ListenerMethod.java:510)
at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:164)
at
com.vaadin.ui.AbstractComponent.fireEvent(AbstractComponent.java:1219)
at com.vaadin.ui.AbstractField.fireValueChange(AbstractField.java:897)
at com.vaadin.ui.AbstractField.setValue(AbstractField.java:529)
at com.vaadin.ui.AbstractSelect.setValue(AbstractSelect.java:670)
at com.vaadin.ui.Table.handleSelectedItems(Table.java:2391)
at com.vaadin.ui.Table.changeVariables(Table.java:2440)
at com.vaadin.ui.TreeTable.changeVariables(TreeTable.java:390)
at
info.magnolia.ui.vaadin.grid.MagnoliaTreeTable.changeVariables(MagnoliaTreeTable.java:61)
at
com.vaadin.terminal.gwt.server.AbstractCommunicationManager.changeVariables(AbstractCommunicationManager.java:1460)
at
com.vaadin.terminal.gwt.server.AbstractCommunicationManager.handleVariableBurst(AbstractCommunicationManager.java:1404)
at
com.vaadin.terminal.gwt.server.AbstractCommunicationManager.handleVariables(AbstractCommunicationManager.java:1329)
at
com.vaadin.terminal.gwt.server.AbstractCommunicationManager.doHandleUidlRequest(AbstractCommunicationManager.java:761)
at
com.vaadin.terminal.gwt.server.CommunicationManager.handleUidlRequest(CommunicationManager.java:323)
...
{code}
was:
To reproduce it
* Expand {{server}} node and select {{mgnl:created}} property
* A WARN as the one pasted below will show up in the logs
* From now on, the app no longer reacts to events, i.e. URI fragment or action
availability in action bar do not change if a different item is selected
* Closing the app sometimes results in a Vaadin's out-of-synch error
{code}
2012-12-11 14:24:28,702 WARN info.magnolia.ui.framework.event.SimpleEventBus
: Exception caught when dispatching event: No view type could be found for
[created]
java.lang.IllegalArgumentException: No view type could be found for [created]
at
info.magnolia.ui.admincentral.content.view.ContentView$ViewType.fromString(ContentView.java:83)
at
info.magnolia.ui.admincentral.app.content.location.ContentLocation.extractView(ContentLocation.java:101)
at
[magnolia-dev] [JIRA] Updated: (MGNLUI-394) Metadata properties (mgnl:*) are displayed and editable
[ http://jira.magnolia-cms.com/browse/MGNLUI-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MGNLUI-394: --- Priority: Major (was: Neutral) Metadata properties (mgnl:*) are displayed and editable --- Key: MGNLUI-394 URL: http://jira.magnolia-cms.com/browse/MGNLUI-394 Project: Magnolia UI Issue Type: Bug Security Level: Public Components: configuration Affects Versions: 5.0 Alpha1 Reporter: Jozef Chocholacek Priority: Major Fix For: 5.0 Alpha2 s011 The metadata properties like mgnl:created, mgnl:lastModifiedBy etc. are displayed (which is not the case in the 4.* series) and editable - that shouldn't be possible, IMO. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLUI-394) Metadata properties (mgnl:*) are displayed and editable
[ http://jira.magnolia-cms.com/browse/MGNLUI-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MGNLUI-394: --- Summary: Metadata properties (mgnl:*) are displayed and editable (was: Metadata properties (mgnl:*) are editable) Fix Version/s: 5.0 Alpha2 s011 Description: The metadata properties like mgnl:created, mgnl:lastModifiedBy etc. are displayed (which is not the case in the 4.* series) and editable - that shouldn't be possible, IMO. was:The metadata properties like mgnl:created, mgnl:lastModifiedBy etc. are editable - that shouldn't be possible, IMO. Metadata properties (mgnl:*) are displayed and editable --- Key: MGNLUI-394 URL: http://jira.magnolia-cms.com/browse/MGNLUI-394 Project: Magnolia UI Issue Type: Bug Security Level: Public Components: configuration Affects Versions: 5.0 Alpha1 Reporter: Jozef Chocholacek Fix For: 5.0 Alpha2 s011 The metadata properties like mgnl:created, mgnl:lastModifiedBy etc. are displayed (which is not the case in the 4.* series) and editable - that shouldn't be possible, IMO. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-4724) Node2Bean: improvements for transformer specification via annotation
Node2Bean: improvements for transformer specification via annotation Key: MAGNOLIA-4724 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4724 Project: Magnolia Issue Type: Improvement Security Level: Public Components: core Reporter: Jaroslav Simak Assignee: Jaroslav Simak Priority: Minor Fix For: 5.0 Alpha2 s011 Things that needs to be improved: - Annotation name avoid spelling out transformer=MyTransformer.class - Use component provider to instantiate transformer - Better javadoc for annotation See MAGNOLIA-4648 comments for more info. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLUI-399) Commented and unnecessary code in ItemViewImpl should be removed
Commented and unnecessary code in ItemViewImpl should be removed Key: MGNLUI-399 URL: http://jira.magnolia-cms.com/browse/MGNLUI-399 Project: Magnolia UI Issue Type: Task Security Level: Public Components: content app Reporter: Tobias Mattsson Priority: Minor Fix For: 5.0 Alpha2 s011 Remove commented code and unnecessary double assignment of the field itemView in info.magnolia.ui.admincentral.content.item.ItemViewImpl#setItemView. Remove the unused field viewType. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLDATA-162) CLONE -Subtype dialog reload incorrectly after validation error.
[ http://jira.magnolia-cms.com/browse/MGNLDATA-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Simak updated MGNLDATA-162: Fix Version/s: 1.8.0 Alpha1 (was: 1.7.4) CLONE -Subtype dialog reload incorrectly after validation error. Key: MGNLDATA-162 URL: http://jira.magnolia-cms.com/browse/MGNLDATA-162 Project: Magnolia Data Module Issue Type: Bug Affects Versions: 1.6.3 Reporter: Jaroslav Simak Assignee: Jaroslav Simak Priority: Critical Fix For: 1.8.0 Alpha1 Steps to reproduce the problem: - Create a new type in Data module (I will reference it as myType) - Create a subtype for the new type (I will reference it as mySubType) - Define a simple dialog for myType - Define another dialog for mySubType, adding a new edit control - Mark the edit control of the subtype as required - Go to the tree and create a new instance of myType, and save it - Select the instance and click on new, the dialog of mySubType will show - Try to save the empty dialog The validation stop the saving process, and the error message for the required field is shown correctly. But the dialog behind now is the myType one, and not the mySubType I would expect. Saving that dialog may cause a real mess in some cases... You will have then a node of myType under another node of myType even if your configuration would not allow it, the user is expecting some data to edit at that level but opening the faulty node will show another dialog (myType instead of mySubType), and obviously xpath queries may have unexpected results. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLDATA-162) CLONE -Subtype dialog reload incorrectly after validation error.
CLONE -Subtype dialog reload incorrectly after validation error. Key: MGNLDATA-162 URL: http://jira.magnolia-cms.com/browse/MGNLDATA-162 Project: Magnolia Data Module Issue Type: Bug Affects Versions: 1.6.3 Reporter: Jaroslav Simak Assignee: Jaroslav Simak Priority: Critical Fix For: 1.7.4 Steps to reproduce the problem: - Create a new type in Data module (I will reference it as myType) - Create a subtype for the new type (I will reference it as mySubType) - Define a simple dialog for myType - Define another dialog for mySubType, adding a new edit control - Mark the edit control of the subtype as required - Go to the tree and create a new instance of myType, and save it - Select the instance and click on new, the dialog of mySubType will show - Try to save the empty dialog The validation stop the saving process, and the error message for the required field is shown correctly. But the dialog behind now is the myType one, and not the mySubType I would expect. Saving that dialog may cause a real mess in some cases... You will have then a node of myType under another node of myType even if your configuration would not allow it, the user is expecting some data to edit at that level but opening the faulty node will show another dialog (myType instead of mySubType), and obviously xpath queries may have unexpected results. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLUI-400) Contact app: editing a folder throws NPE
Contact app: editing a folder throws NPE
Key: MGNLUI-400
URL: http://jira.magnolia-cms.com/browse/MGNLUI-400
Project: Magnolia UI
Issue Type: Bug
Security Level: Public
Affects Versions: 5.0 Alpha1
Reporter: Federico Grilli
Priority: Major
Fix For: 5.0 Alpha2 s011
{code}
2012-12-11 15:21:52,470 WARN info.magnolia.ui.framework.event.SimpleEventBus
: Exception caught when dispatching event: null
java.lang.NullPointerException
at
info.magnolia.ui.admincentral.form.FormPresenterImpl.initActions(FormPresenterImpl.java:76)
at
info.magnolia.ui.admincentral.form.FormPresenterImpl.init(FormPresenterImpl.java:72)
at
info.magnolia.ui.admincentral.form.FormPresenterFactoryImpl.createFormPresenterByDefinition(FormPresenterFactoryImpl.java:72)
at
info.magnolia.ui.admincentral.dialog.FormDialogPresenterImpl.start(FormDialogPresenterImpl.java:96)
at
info.magnolia.ui.admincentral.dialog.action.EditDialogAction.execute(EditDialogAction.java:85)
at
info.magnolia.ui.admincentral.actionbar.ActionbarPresenter.createAndExecuteAction(ActionbarPresenter.java:278)
at
info.magnolia.ui.admincentral.workbench.ContentWorkbenchPresenter$2.onActionbarItemClicked(ContentWorkbenchPresenter.java:155)
at
info.magnolia.ui.admincentral.event.ActionbarItemClickedEvent.dispatch(ActionbarItemClickedEvent.java:66)
at
info.magnolia.ui.admincentral.event.ActionbarItemClickedEvent.dispatch(ActionbarItemClickedEvent.java:1)
at
info.magnolia.ui.framework.event.SimpleEventBus.fireEvent(SimpleEventBus.java:76)
at
info.magnolia.ui.admincentral.actionbar.ActionbarPresenter.onActionbarItemClicked(ActionbarPresenter.java:172)
{code}
--
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
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSOLR-8) Tika 0.4 index problems
[ http://jira.magnolia-cms.com/browse/MGNLSOLR-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MGNLSOLR-8: --- Fix Version/s: (was: 3.0) Tika 0.4 index problems --- Key: MGNLSOLR-8 URL: http://jira.magnolia-cms.com/browse/MGNLSOLR-8 Project: Magnolia Apache Solr integration Issue Type: Bug Affects Versions: 1.0 Environment: Windows server 2008 Reporter: Hans Ardon Assignee: Federico Grilli Priority: Blocker We're running Magnolia 4.4.4. and we're making use of the solr module. When indexing the DMS we're running into problems as described in this article: http://www.mail-archive.com/solr-user@lucene.apache.org/msg38617.html I know this is more a SOLR issue but I'm wondering whether you're familiar with the problem? Do you have any idea how to coop with this problem? I guess Magnolia 4.4.4. is not able to make use of Solr 3.5? -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLUI-401) Rich-text field should use absolute path with context path when linking to plugin
Rich-text field should use absolute path with context path when linking to plugin -- Key: MGNLUI-401 URL: http://jira.magnolia-cms.com/browse/MGNLUI-401 Project: Magnolia UI Issue Type: Bug Security Level: Public Components: dialogs, forms Reporter: Tobias Mattsson Fix For: 5.0 Alpha2 s011 Currently it uses a link with parent references (..) in it which means that its dependent on the number of directories in the current URL. A better solution would generate an absolute link taking the context path (magnoliaAuthor / magnoliaPublic for instance) into account. If there is a convenient way in Vaadin to generate such links this should be used otherwise build the URL yourself using the current HttpRequest object. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSOLR-8) Tika 0.4 index problems
[ http://jira.magnolia-cms.com/browse/MGNLSOLR-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MGNLSOLR-8: --- Fix Version/s: 3.0 Affects Version/s: 1.0 Tika 0.4 index problems --- Key: MGNLSOLR-8 URL: http://jira.magnolia-cms.com/browse/MGNLSOLR-8 Project: Magnolia Apache Solr integration Issue Type: Bug Affects Versions: 1.0 Environment: Windows server 2008 Reporter: Hans Ardon Assignee: Federico Grilli Priority: Blocker We're running Magnolia 4.4.4. and we're making use of the solr module. When indexing the DMS we're running into problems as described in this article: http://www.mail-archive.com/solr-user@lucene.apache.org/msg38617.html I know this is more a SOLR issue but I'm wondering whether you're familiar with the problem? Do you have any idea how to coop with this problem? I guess Magnolia 4.4.4. is not able to make use of Solr 3.5? -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLUI-402) Rename ContentWorkbenchView#resynch method
Rename ContentWorkbenchView#resynch method -- Key: MGNLUI-402 URL: http://jira.magnolia-cms.com/browse/MGNLUI-402 Project: Magnolia UI Issue Type: Task Security Level: Public Components: content app Reporter: Tobias Mattsson Fix For: 5.0 Alpha2 s011 The method should be renamed from resynch to resync. Or even better find a more descriptive name. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSOLR-10) Remove dependency on solr-core
[ http://jira.magnolia-cms.com/browse/MGNLSOLR-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MGNLSOLR-10: Parent: MGNLSOLR-9 Issue Type: Sub-task (was: Task) Remove dependency on solr-core -- Key: MGNLSOLR-10 URL: http://jira.magnolia-cms.com/browse/MGNLSOLR-10 Project: Magnolia Apache Solr integration Issue Type: Sub-task Reporter: Federico Grilli Assignee: Christian Ringele Priority: Critical Fix For: 3.0 The dependency on solr-core should be removed so to avoid pulling in libraries incompatible with those brought in by Magnolia and JCR 2.0, most notably Lucene. The only reason for having solr-core ws the support for Solr embedded server (http://wiki.apache.org/solr/EmbeddedSolr) which we're going to drop. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLSOLR-10) Remove dependency on solr-core
Remove dependency on solr-core -- Key: MGNLSOLR-10 URL: http://jira.magnolia-cms.com/browse/MGNLSOLR-10 Project: Magnolia Apache Solr integration Issue Type: Task Reporter: Federico Grilli Assignee: Christian Ringele Priority: Critical Fix For: 3.0 The dependency on solr-core should be removed so to avoid pulling in libraries incompatible with those brought in by Magnolia and JCR 2.0, most notably Lucene. The only reason for having solr-core ws the support for Solr embedded server (http://wiki.apache.org/solr/EmbeddedSolr) which we're going to drop. . -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSOLR-10) Remove dependency on solr-core
[ http://jira.magnolia-cms.com/browse/MGNLSOLR-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MGNLSOLR-10: Description: The dependency on solr-core should be removed so to avoid pulling in libraries incompatible with those brought in by Magnolia and JCR 2.0, most notably Lucene. The only reason for having solr-core ws the support for Solr embedded server (http://wiki.apache.org/solr/EmbeddedSolr) which we're going to drop. (was: The dependency on solr-core should be removed so to avoid pulling in libraries incompatible with those brought in by Magnolia and JCR 2.0, most notably Lucene. The only reason for having solr-core ws the support for Solr embedded server (http://wiki.apache.org/solr/EmbeddedSolr) which we're going to drop. . ) Remove dependency on solr-core -- Key: MGNLSOLR-10 URL: http://jira.magnolia-cms.com/browse/MGNLSOLR-10 Project: Magnolia Apache Solr integration Issue Type: Task Reporter: Federico Grilli Assignee: Christian Ringele Priority: Critical Fix For: 3.0 The dependency on solr-core should be removed so to avoid pulling in libraries incompatible with those brought in by Magnolia and JCR 2.0, most notably Lucene. The only reason for having solr-core ws the support for Solr embedded server (http://wiki.apache.org/solr/EmbeddedSolr) which we're going to drop. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLUI-403) AppContext exposes functionality internal to AppContextImpl and AppControllerImpl
AppContext exposes functionality internal to AppContextImpl and AppControllerImpl -- Key: MGNLUI-403 URL: http://jira.magnolia-cms.com/browse/MGNLUI-403 Project: Magnolia UI Issue Type: Task Security Level: Public Components: app framework Reporter: Tobias Mattsson Priority: Major Fix For: 5.0 Alpha2 s011 The idea of AppContext is to expose functionality to the App. That is, to an instance of an app. It should not expose methods that are only used by AppControllerImpl. These should be hidden from all other classes. If necessary AppControllerImpl#runningApps should be changed to String, AppContextImpl. Also if the intention of AppContextImpl is unclear it should be renamed to reflect the fact that is not just the default implementation of AppContext, it does much more and in fact fullfils much of the contract defined by AppController. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSOLR-9) Upgrade to Solr 3.6 and Magnolia 4.5
[ http://jira.magnolia-cms.com/browse/MGNLSOLR-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MGNLSOLR-9: --- Attachment: (was: magnolia-module-solr-3.0.zip) Upgrade to Solr 3.6 and Magnolia 4.5 Key: MGNLSOLR-9 URL: http://jira.magnolia-cms.com/browse/MGNLSOLR-9 Project: Magnolia Apache Solr integration Issue Type: Task Reporter: Federico Grilli Assignee: Federico Grilli Fix For: 3.0 Initial commit is already on svn at http://svn.magnolia-cms.com/svn/forge/magnolia-module-solr/branches/magnolia-module-solr-3.x/ Attaching here a zipped folder with sources as a user on forum would like to try it but for some reason he's unable to connect to our svn (http://forum.magnolia-cms.com/forum/thread.html?threadId=88707c16-2a3a-440d-b7f2-bfee5541c570). -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSOLR-9) Upgrade to Solr 3.6 and Magnolia 4.5
[ http://jira.magnolia-cms.com/browse/MGNLSOLR-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MGNLSOLR-9: --- Release notes required: [Yes] Description: Initial commit is already on svn at http://svn.magnolia-cms.com/svn/forge/magnolia-module-solr/branches/magnolia-module-solr-3.x/ -Attaching here a zipped folder with sources as a user on forum would like to try it but for some reason he's unable to connect to our svn (http://forum.magnolia-cms.com/forum/thread.html?threadId=88707c16-2a3a-440d-b7f2-bfee5541c570).- was: Initial commit is already on svn at http://svn.magnolia-cms.com/svn/forge/magnolia-module-solr/branches/magnolia-module-solr-3.x/ Attaching here a zipped folder with sources as a user on forum would like to try it but for some reason he's unable to connect to our svn (http://forum.magnolia-cms.com/forum/thread.html?threadId=88707c16-2a3a-440d-b7f2-bfee5541c570). Upgrade to Solr 3.6 and Magnolia 4.5 Key: MGNLSOLR-9 URL: http://jira.magnolia-cms.com/browse/MGNLSOLR-9 Project: Magnolia Apache Solr integration Issue Type: Task Reporter: Federico Grilli Assignee: Federico Grilli Fix For: 3.0 Initial commit is already on svn at http://svn.magnolia-cms.com/svn/forge/magnolia-module-solr/branches/magnolia-module-solr-3.x/ -Attaching here a zipped folder with sources as a user on forum would like to try it but for some reason he's unable to connect to our svn (http://forum.magnolia-cms.com/forum/thread.html?threadId=88707c16-2a3a-440d-b7f2-bfee5541c570).- -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLSOLR-11) Remove Solr embedded server support
Remove Solr embedded server support --- Key: MGNLSOLR-11 URL: http://jira.magnolia-cms.com/browse/MGNLSOLR-11 Project: Magnolia Apache Solr integration Issue Type: Sub-task Reporter: Federico Grilli Assignee: Christian Ringele Priority: Critical Fix For: 3.0 It pulls in unwanted/conflicting deps and it's not even considered best-practice see http://wiki.apache.org/solr/EmbeddedSolr -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSOLR-9) Upgrade to Solr 3.6 and Magnolia 4.5
[ http://jira.magnolia-cms.com/browse/MGNLSOLR-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MGNLSOLR-9: --- Description: Initial commit is already on svn at http://svn.magnolia-cms.com/svn/forge/magnolia-module-solr/branches/magnolia-module-solr-3.x/ was: Initial commit is already on svn at http://svn.magnolia-cms.com/svn/forge/magnolia-module-solr/branches/magnolia-module-solr-3.x/ -Attaching here a zipped folder with sources as a user on forum would like to try it but for some reason he's unable to connect to our svn (http://forum.magnolia-cms.com/forum/thread.html?threadId=88707c16-2a3a-440d-b7f2-bfee5541c570).- Upgrade to Solr 3.6 and Magnolia 4.5 Key: MGNLSOLR-9 URL: http://jira.magnolia-cms.com/browse/MGNLSOLR-9 Project: Magnolia Apache Solr integration Issue Type: Task Reporter: Federico Grilli Assignee: Federico Grilli Fix For: 3.0 Initial commit is already on svn at http://svn.magnolia-cms.com/svn/forge/magnolia-module-solr/branches/magnolia-module-solr-3.x/ -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSOLR-11) Remove Solr embedded server support
[ http://jira.magnolia-cms.com/browse/MGNLSOLR-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MGNLSOLR-11: Description: Needs solr-core which pulls in unwanted/conflicting deps and it's not even considered best-practice see http://wiki.apache.org/solr/EmbeddedSolr (was: It pulls in unwanted/conflicting deps and it's not even considered best-practice see http://wiki.apache.org/solr/EmbeddedSolr) Remove Solr embedded server support --- Key: MGNLSOLR-11 URL: http://jira.magnolia-cms.com/browse/MGNLSOLR-11 Project: Magnolia Apache Solr integration Issue Type: Sub-task Reporter: Federico Grilli Assignee: Christian Ringele Priority: Critical Fix For: 3.0 Needs solr-core which pulls in unwanted/conflicting deps and it's not even considered best-practice see http://wiki.apache.org/solr/EmbeddedSolr -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] Initiate Workflow programatically
Hi,
We are trying to initiate a worklfow programatically and we have configured
a workflow.xml in such a way that once a worklfow is initiate it will
automatically publish the item without waiting in the inbox.
Please find the xml configuration below
process-definition name=publish revision=j0.0.2 sequence set
field=activator field-value=userName/ !-- if the last action was
proceed: activate-- activate/ /sequenceprocess-definition
name=activate sequence!-- wait if scheduled --if defined
field-value=startDate/ sleep until=${f:startDate}/ /if !--
activate -- participant ref=command-activate/ if defined
field-value=exception/ !-- restart again -- activation/ break/
/if !-- deactivate (if scheduled)--ifdefined
field-value=endDate/ sequence sleep until=${f:endDate}/
participant ref=command-deactivate/ /sequence /if /sequence
/process-definition /process-definition
We are trying to launchItem using the code shown below
public static void launchFlow(LaunchItem li, String flowName,
boolean isAsync) throws FlowDefinitionException {
try {
FlowDefinitionManager configurator = WorkflowModule
.getFlowDefinitionManager();
configurator.configure(li, flowName);
launchFlow(li, isAsync);
} catch (Exception e) {
LOGGER.error(Launching flow failed in public
launchFlow() : , e);
}
}
The problem here is sometimes the child node is getting published before the
parent node and hence we are getting some exception because of this.Is there a
way using which I can handle this issue either programatically or using the
worklfow config.xml
--
Context is everything:
http://forum.magnolia-cms.com/forum/thread.html?threadId=16a31133-aec4-48cc-a45f-289789edb08a
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLUI-367) Regression: apps are no longer bookmarkable
[ http://jira.magnolia-cms.com/browse/MGNLUI-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MGNLUI-367: --- Description: I don't know since when this is broken. For sure I remember searches being bookmarkable in sprint 7. The issue concerns all types of views. (was: I don't know since how long this is broken. For sure I remember searches being bookmarkable in sprint 7. The issue concerns all types of views. ) Regression: apps are no longer bookmarkable - Key: MGNLUI-367 URL: http://jira.magnolia-cms.com/browse/MGNLUI-367 Project: Magnolia UI Issue Type: Bug Security Level: Public Components: content app Affects Versions: 5.0 Alpha1 Reporter: Federico Grilli Assignee: Espen Jervidalo Priority: Blocker Fix For: 5.0 Alpha1 I don't know since when this is broken. For sure I remember searches being bookmarkable in sprint 7. The issue concerns all types of views. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLUI-404) Configuration often using the implementation instead of the interface
[ http://jira.magnolia-cms.com/browse/MGNLUI-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Espen Jervidalo updated MGNLUI-404: --- Description: see subappDescriptor, imageprovider, appDescriptor This will also need some re-configuration of the componentProvider, putting the mappings into the right spot to make sure it can actually get resolved. was: see subappDescriptor, imageprovider, appDescriptor This will also need some re-configuration of the componentProvider, putting the mappings into the right spot. Configuration often using the implementation instead of the interface - Key: MGNLUI-404 URL: http://jira.magnolia-cms.com/browse/MGNLUI-404 Project: Magnolia UI Issue Type: Task Security Level: Public Components: configuration Affects Versions: 5.0 Alpha1 Reporter: Espen Jervidalo Fix For: 5.0 Alpha2 s011 see subappDescriptor, imageprovider, appDescriptor This will also need some re-configuration of the componentProvider, putting the mappings into the right spot to make sure it can actually get resolved. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLUI-404) Configuration often using the implementation instead of the interface
Configuration often using the implementation instead of the interface - Key: MGNLUI-404 URL: http://jira.magnolia-cms.com/browse/MGNLUI-404 Project: Magnolia UI Issue Type: Task Security Level: Public Components: configuration Affects Versions: 5.0 Alpha1 Reporter: Espen Jervidalo Fix For: 5.0 Alpha2 s011 see subappDescriptor, imageprovider, appDescriptor This will also need some re-configuration of the componentProvider, putting the mappings into the right spot. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSTK-1048) Some image links are no longer properly generated
[ http://jira.magnolia-cms.com/browse/MGNLSTK-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Lipp updated MGNLSTK-1048: - Summary: Some image links are no longer properly generated (was: Previewing Demo-Project doesn't render Magnolia Logo in the upper left anymore) Description: Most obvious example: Previewing Demo-Project doesn't render Magnolia Logo in the upper left anymore. Trying to use the Asset chooser and pick another Asset doesn't work either. Component/s: demoproject Some image links are no longer properly generated - Key: MGNLSTK-1048 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1048 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: demoproject Affects Versions: 2.5 Alpha1 Reporter: Daniel Lipp Priority: Critical Fix For: 2.5 Alpha2 s011 Attachments: Screen Shot 2012-12-06 at 11.22.51.jpg Most obvious example: Previewing Demo-Project doesn't render Magnolia Logo in the upper left anymore. Trying to use the Asset chooser and pick another Asset doesn't work either. -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4702) CE bundle: update category name in log4j config
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Lipp updated MAGNOLIA-4702: -- Fix Version/s: 5.0 Alpha1 (was: 5.0 Alpha2 s011) CE bundle: update category name in log4j config --- Key: MAGNOLIA-4702 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4702 Project: Magnolia Issue Type: Bug Security Level: Public Components: build Affects Versions: 5.0 Alpha1 Reporter: Federico Grilli Assignee: Federico Grilli Priority: Major Fix For: 5.0 Alpha1 -- 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 Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
