[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4723) Trying to choose Node when editing ACL for workspace 'users' causes RuntimeException, manual ACL doesn't work as expected
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Kutschke updated MAGNOLIA-4723: - Attachment: users_tree-config.png Adding a data node 'rootPath' with value '/' to the configuration of 'adminInterface/trees/users' solves the exception issue. > Trying to choose Node when editing ACL for workspace 'users' causes > RuntimeException, manual ACL doesn't work as expected > - > > Key: MAGNOLIA-4723 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4723 > Project: Magnolia > Issue Type: Bug > Security Level: Public > Components: security >Affects Versions: 4.5.6 >Reporter: Christian Kutschke >Priority: Critical > Attachments: superuser_acl.png, users_tree-config.png > > > Hi, > when trying to edit the ACL for workspace 'users' for any role (i. e. > superuser), a java.lang.RuntimeException occurs, causing the container to > respond with HTTP 500. > This can be reproduced arbitrary on the Public Demo Instance. > Furthermore, when I configure an ACL-Rule for this workspace manually, say > with path '/admin' and permission 'Read only', users with this role assigned > can edit and create users, too. > Beside the mentioned Exception: Is there any way to configure read/write - > Permissions on the 'users' workspace, as it is possible for the other > workspaces? -- 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:
[magnolia-dev] [JIRA] Created: (MGNLUI-382) Contacts App: No items are displayed in Thumbnail view
Contacts App: No items are displayed in Thumbnail view -- Key: MGNLUI-382 URL: http://jira.magnolia-cms.com/browse/MGNLUI-382 Project: Magnolia UI Issue Type: Bug Security Level: Public Affects Versions: 5.0 Alpha1 s010 Reporter: Christopher Zimmermann Priority: Critical Fix For: 5.0 Alpha1 s010 -- 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:
[magnolia-dev] [JIRA] Updated: (MGNLUI-382) Contacts App: No items are displayed in Thumbnail view
[ http://jira.magnolia-cms.com/browse/MGNLUI-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Zimmermann updated MGNLUI-382: -- Priority: Blocker (was: Critical) > Contacts App: No items are displayed in Thumbnail view > -- > > Key: MGNLUI-382 > URL: http://jira.magnolia-cms.com/browse/MGNLUI-382 > Project: Magnolia UI > Issue Type: Bug > Security Level: Public >Affects Versions: 5.0 Alpha1 s010 >Reporter: Christopher Zimmermann >Assignee: Aleksandr Pchelintcev >Priority: Blocker > Fix For: 5.0 Alpha1 s010 > > -- 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:
[magnolia-dev] [JIRA] Updated: (MGNLUI-253) Add file type icons to apps
[ http://jira.magnolia-cms.com/browse/MGNLUI-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MGNLUI-253: --- Summary: Add file type icons to apps (was: Add an icon to user/group/role nodes) Issue Type: Improvement (was: Task) Fix Version/s: 5.0 Alpha1 s010 (was: 5.0 Alpha2 s011) Priority: Critical (was: Major) Description: (was: In the Security app, add an icon indicating "this is an user/group/role" and not a folder to the user/group/role records in the workbench.) Component/s: content app pages app tree/list > Add file type icons to apps > --- > > Key: MGNLUI-253 > URL: http://jira.magnolia-cms.com/browse/MGNLUI-253 > Project: Magnolia UI > Issue Type: Improvement > Security Level: Public > Components: content app, design, pages app, security app, tree/list >Reporter: Jozef Chocholacek >Assignee: Federico Grilli >Priority: Critical > Fix For: 5.0 Alpha1 s010 > > -- 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:
[magnolia-dev] [JIRA] Created: (MGNLUI-383) "select asset" button is cut off in dialogs.
"select asset" button is cut off in dialogs. Key: MGNLUI-383 URL: http://jira.magnolia-cms.com/browse/MGNLUI-383 Project: Magnolia UI Issue Type: Bug Security Level: Public Affects Versions: 5.0 Alpha2 s011 Reporter: Christopher Zimmermann Assignee: Christopher Zimmermann Priority: Major Fix For: 5.0 Alpha2 s011 Only "select a" is visible. -- 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:
[magnolia-dev] [JIRA] Updated: (MGNLUI-253) Add content/folder type icons to apps
[ http://jira.magnolia-cms.com/browse/MGNLUI-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MGNLUI-253: --- Summary: Add content/folder type icons to apps (was: Add file type icons to apps) > Add content/folder type icons to apps > - > > Key: MGNLUI-253 > URL: http://jira.magnolia-cms.com/browse/MGNLUI-253 > Project: Magnolia UI > Issue Type: Improvement > Security Level: Public > Components: content app, design, pages app, security app, tree/list >Reporter: Jozef Chocholacek >Assignee: Federico Grilli >Priority: Critical > Fix For: 5.0 Alpha1 s010 > > -- 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:
[magnolia-dev] [JIRA] Created: (MGNLUI-384) AssetLinkField and TextAndButtonField should handle a variety of button text lengths
AssetLinkField and TextAndButtonField should handle a variety of button text lengths Key: MGNLUI-384 URL: http://jira.magnolia-cms.com/browse/MGNLUI-384 Project: Magnolia UI Issue Type: Bug Security Level: Public Reporter: Christopher Zimmermann These field types have a text field with a button on the right side. These two field types both use the same css class to set the width on the text field: "small-textfield". As the width is "hard coded" there can be a problem if the button text width is very wide, in which case it will be cut-off as it leaves the form and not be readable. Either these types of field should have a variable button and text field widths, or if the button is a fixed width, then there should be a tooltip on button hover to indicate what is in the button. And the text should perhaps be cropped. -- 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:
[magnolia-dev] [JIRA] Updated: (MGNLUI-383) "select asset" button is cut off in dialogs.
[ http://jira.magnolia-cms.com/browse/MGNLUI-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Zimmermann updated MGNLUI-383: -- Fix Version/s: 5.0 Alpha1 s010 (was: 5.0 Alpha2 s011) Affects Version/s: 5.0 Alpha1 s010 (was: 5.0 Alpha2 s011) > "select asset" button is cut off in dialogs. > > > Key: MGNLUI-383 > URL: http://jira.magnolia-cms.com/browse/MGNLUI-383 > Project: Magnolia UI > Issue Type: Bug > Security Level: Public >Affects Versions: 5.0 Alpha1 s010 >Reporter: Christopher Zimmermann >Assignee: Christopher Zimmermann >Priority: Major > Fix For: 5.0 Alpha1 s010 > > > Only "select a" is visible. -- 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:
[magnolia-dev] [JIRA] Updated: (MGNLUI-384) AssetLinkField and TextAndButtonField should handle a variety of button text lengths
[ http://jira.magnolia-cms.com/browse/MGNLUI-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Zimmermann updated MGNLUI-384: -- Fix Version/s: 5.0 Affects Version/s: 5.0 > AssetLinkField and TextAndButtonField should handle a variety of button text > lengths > > > Key: MGNLUI-384 > URL: http://jira.magnolia-cms.com/browse/MGNLUI-384 > Project: Magnolia UI > Issue Type: Bug > Security Level: Public >Affects Versions: 5.0 >Reporter: Christopher Zimmermann > Fix For: 5.0 > > > These field types have a text field with a button on the right side. > These two field types both use the same css class to set the width on the > text field: "small-textfield". > As the width is "hard coded" there can be a problem if the button text width > is very wide, in which case it will be cut-off as it leaves the form and not > be readable. > Either these types of field should have a variable button and text field > widths, or if the button is a fixed width, then there should be a tooltip on > button hover to indicate what is in the button. And the text should perhaps > be cropped. -- 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:
[magnolia-dev] [JIRA] Updated: (MGNLUI-385) Description in dialogs/forms is missing bottom border
[ http://jira.magnolia-cms.com/browse/MGNLUI-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MGNLUI-385: --- Description: Okay, maybe it's a bit overkill to set this as critical, however it is an annoying regression which can be fixed easily. See also http://wiki.magnolia-cms.com/display/UX/Style+guides+for+forms+and+dialogs+in+Magnolia (was: Okay, maybe it's a bit overkill to set this as critical however, it is an annoying regression which can be fixed easily.) > Description in dialogs/forms is missing bottom border > - > > Key: MGNLUI-385 > URL: http://jira.magnolia-cms.com/browse/MGNLUI-385 > Project: Magnolia UI > Issue Type: Bug > Security Level: Public > Components: dialogs, forms >Affects Versions: 5.0 Alpha1 s009 >Reporter: Federico Grilli >Assignee: Federico Grilli >Priority: Critical > Fix For: 5.0 Alpha1 s010 > > Attachments: missing-border.png > > > Okay, maybe it's a bit overkill to set this as critical, however it is an > annoying regression which can be fixed easily. See also > http://wiki.magnolia-cms.com/display/UX/Style+guides+for+forms+and+dialogs+in+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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLUI-385) Description in dialogs/forms is missing bottom border
Description in dialogs/forms is missing bottom border - Key: MGNLUI-385 URL: http://jira.magnolia-cms.com/browse/MGNLUI-385 Project: Magnolia UI Issue Type: Bug Security Level: Public Components: dialogs, forms Affects Versions: 5.0 Alpha1 s009 Reporter: Federico Grilli Assignee: Federico Grilli Priority: Critical Fix For: 5.0 Alpha1 s010 Attachments: missing-border.png Okay, maybe it's a bit overkill to set this as critical however, it is an annoying regression which can be fixed easily. -- 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:
[magnolia-dev] [JIRA] Created: (MGNLUI-386) Contact apps: actions availability is wrong
Contact apps: actions availability is wrong --- Key: MGNLUI-386 URL: http://jira.magnolia-cms.com/browse/MGNLUI-386 Project: Magnolia UI Issue Type: Bug Security Level: Public Affects Versions: 5.0 Alpha1 s009 Reporter: Federico Grilli Assignee: Federico Grilli Priority: Blocker Fix For: 5.0 Alpha2 s011 Attachments: contacts-actionbar.png Given the initial state, only "new folder" and "new contact" should be available. Once a contact is selected only edit/delete actions should be available. -- 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:
[magnolia-dev] [JIRA] Created: (MGNLSTK-1051) TemplateCategoryUtil should use NodeTypes.Renderable.getTemplate(Node)
TemplateCategoryUtil should use NodeTypes.Renderable.getTemplate(Node) -- Key: MGNLSTK-1051 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1051 Project: Magnolia Standard Templating Kit Issue Type: Task Components: templates Reporter: Tobias Mattsson Priority: Trivial Fix For: 2.5 Alpha1 s011 It's currently using PropertyUtil probably to avoid exception handling. It should use NodeTypes.Renderable.getTemplate(Node) and perform exception handling on its own. -- 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:
[magnolia-dev] [JIRA] Updated: (MGNLUI-386) Contact apps: actions availability is wrong
[ http://jira.magnolia-cms.com/browse/MGNLUI-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Bärfuss updated MGNLUI-386: --- Fix Version/s: 5.0 Alpha1 s010 (was: 5.0 Alpha2 s011) Priority: Critical (was: Blocker) > Contact apps: actions availability is wrong > --- > > Key: MGNLUI-386 > URL: http://jira.magnolia-cms.com/browse/MGNLUI-386 > Project: Magnolia UI > Issue Type: Bug > Security Level: Public >Affects Versions: 5.0 Alpha1 s009 >Reporter: Federico Grilli >Assignee: Federico Grilli >Priority: Critical > Fix For: 5.0 Alpha1 s010 > > Attachments: contacts-actionbar.png > > > Given the initial state, only "new folder" and "new contact" should be > available. Once a contact is selected only edit/delete actions should be > available. -- 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:
[magnolia-dev] [JIRA] Created: (MGNLUI-387) TemplateSelectorField queries for available templates using the wrong node
TemplateSelectorField queries for available templates using the wrong node -- Key: MGNLUI-387 URL: http://jira.magnolia-cms.com/browse/MGNLUI-387 Project: Magnolia UI Issue Type: Bug Security Level: Public Reporter: Tobias Mattsson Priority: Critical Fix For: 5.0 Alpha2 s011 In 4.5 the node was created and assigned the default template, only afterwards did the user make a selection by changing the template in the template column. In 5.0 we're instead presenting a dialog first where the user can select the template to assign to the node once its created. This has produced a bug in the current code base where TemplateSelectorField queries for available templates using the parent node. info.magnolia.rendering.template.assignment.TemplateDefinitionAssignment#getAvailableTemplates(Node) is not supposed to be used to test for available nodes in _children_ of the passed node. -- 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:
[magnolia-dev] [JIRA] Created: (MGNLSTK-1052) Template availability expects to be passed the parent node
Template availability expects to be passed the parent node -- Key: MGNLSTK-1052 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1052 Project: Magnolia Standard Templating Kit Issue Type: Bug Reporter: Tobias Mattsson Fix For: 2.5 Alpha1 s011 This was introduced in MGNLSTK-1050 to compensate for the bug reported as MGNLUI-387. We should revert the changes made in MGNLSTK-1050. -- 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:
[magnolia-dev] [JIRA] Reopened: (MGNLINTEMPL-21) Automatic versioning on save.
[ http://jira.magnolia-cms.com/browse/MGNLINTEMPL-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kovařík reopened MGNLINTEMPL-21: -- Missing file config.modules.inplace-templating.pages.xml and its bootstrap task. > Automatic versioning on save. > - > > Key: MGNLINTEMPL-21 > URL: http://jira.magnolia-cms.com/browse/MGNLINTEMPL-21 > Project: Magnolia In-place templating Module > Issue Type: New Feature >Affects Versions: 1.3 >Reporter: Jan Haderka >Assignee: Jan Haderka > Fix For: 1.3.1 > > -- 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:
[magnolia-dev] [JIRA] Created: (MGNLRES-54) IllegalStateException when trying to edit new item
IllegalStateException when trying to edit new item -- Key: MGNLRES-54 URL: http://jira.magnolia-cms.com/browse/MGNLRES-54 Project: Magnolia Resources Module Issue Type: Bug Affects Versions: 1.5.3 Reporter: Roman Kovařík Assignee: Federico Grilli Fix For: 1.5.x Steps to reproduce: Create new item in Templating Kit/resources, click Edit item: Caused by: java.lang.IllegalStateException: No resource type selected. at info.magnolia.module.resources.dialogs.ResourcesEditDialog.getDialogUsedByResourceType(ResourcesEditDialog.java:111) at info.magnolia.module.resources.dialogs.ResourcesEditDialog.(ResourcesEditDialog.java:82) (The resource type is missing when new item is created.) -- 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:
[magnolia-dev] [JIRA] Updated: (MGNLUI-386) Contact apps: actions availability is wrong
[ http://jira.magnolia-cms.com/browse/MGNLUI-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MGNLUI-386: --- Description: To summarize: * initial state (root selected) -- can create folder or contact * folder selected -- can create/edit/delete folder or create contact * contact selected -- can only edit/delete contact was:Given the initial state, only "new folder" and "new contact" should be available. Once a contact is selected only edit/delete actions should be available. > Contact apps: actions availability is wrong > --- > > Key: MGNLUI-386 > URL: http://jira.magnolia-cms.com/browse/MGNLUI-386 > Project: Magnolia UI > Issue Type: Bug > Security Level: Public >Affects Versions: 5.0 Alpha1 s009 >Reporter: Federico Grilli >Assignee: Federico Grilli >Priority: Critical > Fix For: 5.0 Alpha1 s010 > > Attachments: contacts-actionbar.png > > > To summarize: > * initial state (root selected) > -- can create folder or contact > * folder selected > -- can create/edit/delete folder or create contact > * contact selected > -- can only edit/delete contact -- 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:
[magnolia-dev] [JIRA] Updated: (BLOSSOM-103) No contextAttributes set in renderer when executing web flow component
[
http://jira.magnolia-cms.com/browse/BLOSSOM-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Brimor updated BLOSSOM-103:
-
Priority: Trivial (was: Neutral)
Description: Issue was that we had not updated our spring-webflow.xml
configuration file. We had not added the contextAttributes property. (was: We
have a class ExtendedFreemarkerTemplateViewRenderer extends
FreemarkerTemplateViewRenderer which we have configured to render freemarker
templates in blossom-servlet.xml:
{code}
{code}
When rendering a webflow component the contextAttributes are not set (which
works for regular components). The call stack up to
info.magnolia.rendering.renderer.AbstractRenderer#setupContext is as follow for
this case is as follows:
{code}
http-bio-131.116.79.105-41680-exec-24@20105 daemon, prio=5, in group 'main',
status: 'RUNNING'
at
info.magnolia.rendering.renderer.AbstractRenderer.setupContext(AbstractRenderer.java:249)
at
info.magnolia.module.blossom.view.FreemarkerTemplateViewRenderer.setupContext(FreemarkerTemplateViewRenderer.java:53)
at
com.teliasonera.agora.core.presentationfw.magnolia.blossom.view.ExtendedFreemarkerTemplateViewRenderer.setupContext(ExtendedFreemarkerTemplateViewRenderer.java:18)
at
info.magnolia.rendering.renderer.AbstractRenderer.render(AbstractRenderer.java:133)
at
info.magnolia.module.blossom.view.TemplateView.renderMergedOutputModel(TemplateView.java:74)
at
org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:250)
at
org.springframework.webflow.mvc.servlet.ServletMvcView.doRender(ServletMvcView.java:50)
at
org.springframework.webflow.mvc.view.AbstractMvcView.render(AbstractMvcView.java:187)
at
org.springframework.webflow.engine.ViewState.render(ViewState.java:296)
at
org.springframework.webflow.engine.ViewState.doEnter(ViewState.java:186)
at org.springframework.webflow.engine.State.enter(State.java:194)
at
org.springframework.webflow.engine.Transition.execute(Transition.java:227)
at
org.springframework.webflow.engine.DecisionState.doEnter(DecisionState.java:51)
at org.springframework.webflow.engine.State.enter(State.java:194)
at org.springframework.webflow.engine.Flow.start(Flow.java:535)
at
org.springframework.webflow.engine.impl.FlowExecutionImpl.start(FlowExecutionImpl.java:366)
at
org.springframework.webflow.engine.impl.FlowExecutionImpl.start(FlowExecutionImpl.java:225)
at
org.springframework.webflow.executor.FlowExecutorImpl.launchExecution(FlowExecutorImpl.java:140)
at
org.springframework.webflow.mvc.servlet.FlowHandlerAdapter.handle(FlowHandlerAdapter.java:193)
at
org.springframework.webflow.mvc.servlet.FlowController.handleRequest(FlowController.java:174)
at
com.teliasonera.agora.core.presentationfw.magnolia.blossom.AbstractSingleFlowController.handleRequest(AbstractSingleFlowController.java:57)
at
com.teliasonera.agora.modules.serviceassurance.presentation.magnolia.impl.blossom.BlossomErrorServiceAssuranceFlow.handleRequest(BlossomErrorServiceAssuranceFlow.java:49)
at
org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
at
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:790)
at
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:719)
at
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:644)
at
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:549)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:621)
at
info.magnolia.module.blossom.render.BlossomDispatcherServlet.include(BlossomDispatcherServlet.java:138)
at
info.magnolia.module.blossom.render.BlossomTemplateRenderer.render(BlossomTemplateRenderer.java:76)
at
info.magnolia.rendering.engine.DefaultRenderingEngine.render(DefaultRenderingEngine.java:97)
at
info.magnolia.rendering.engine.DefaultRenderingEngine$$EnhancerByCGLIB$$1ad5a6a3.render(:-1)
at
info.magnolia.templating.elements.ComponentElement.begin(ComponentElement.java:151)
at
info.magnolia.templating.freemarker.AbstractDirective.execute(AbstractDirective.java:93)
at freemarker.core.Environment.visit(Environment.java:274)
at freemarker.core.UnifiedCall.accept(UnifiedCall.java:126)
at freemarker.core.Environment.visit(Environment.java:221)
[magnolia-dev] [JIRA] Updated: (MGNLDATA-127) Subtype dialog reload incorrectly after validation error.
[ http://jira.magnolia-cms.com/browse/MGNLDATA-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka updated MGNLDATA-127: - Fix Version/s: 1.6.6 (was: 1.6.x) > Subtype dialog reload incorrectly after validation error. > - > > Key: MGNLDATA-127 > URL: http://jira.magnolia-cms.com/browse/MGNLDATA-127 > Project: Magnolia Data Module > Issue Type: Bug >Affects Versions: 1.6.3 >Reporter: Danilo Ghirardelli >Assignee: Philipp Bärfuss >Priority: Critical > Fix For: 1.7.4 > > Attachments: rename.patch > > > 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:
[magnolia-dev] [JIRA] Updated: (MGNLDATA-127) Subtype dialog reload incorrectly after validation error.
[ http://jira.magnolia-cms.com/browse/MGNLDATA-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milan Divilek updated MGNLDATA-127: --- Assignee: Jaroslav Simak (was: Philipp Bärfuss) Fix Version/s: 1.7.4 (was: 1.6.6) > Subtype dialog reload incorrectly after validation error. > - > > Key: MGNLDATA-127 > URL: http://jira.magnolia-cms.com/browse/MGNLDATA-127 > Project: Magnolia Data Module > Issue Type: Bug >Affects Versions: 1.6.3 >Reporter: Danilo Ghirardelli >Assignee: Jaroslav Simak >Priority: Critical > Fix For: 1.7.4 > > Attachments: rename.patch > > > 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:
[magnolia-dev] [JIRA] Created: (MGNLUI-388) Config app: missing the possibility to add an "mgnl:content"
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 s009 Reporter: Federico Grilli Assignee: Federico Grilli Priority: Critical Fix For: 5.0 Alpha1 s010 fix ready locally -- 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:
[magnolia-dev] [JIRA] Updated: (MGNLDATA-157) Mark as deleted don't work for data
[
http://jira.magnolia-cms.com/browse/MGNLDATA-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frank Sommer updated MGNLDATA-157:
--
Description:
There are some issues with a configured mark as deleted feature in the data
module.
# there is no deleted icon in front of the marked as deleted data node
# the delete pop-up message is still the old delete message
# the 'delete-all' action is not covered by the extended delete behavior
# typo in the german confirmation message
(x)
{noformat}
tree.references.confirm.text.js=Warnung: Der Knoten wird zum Löschen markiert
(diese Operation kann rückgängig gemacht werden), aber es wurden Abhängigkeiten
zum ihm gefunden. Falls Sie Löschen bestätigen, werden die folgenden Seiten
ungültige Referenzen enthalten. Wirklich fortfahren?
{noformat}
(/)
{noformat}
tree.references.confirm.text.js=Warnung: Der Knoten wird zum Löschen markiert
(diese Operation kann rückgängig gemacht werden), aber es wurden Abhängigkeiten
zu ihm gefunden. Falls Sie Löschen bestätigen, werden die folgenden Seiten
ungültige Referenzen enthalten. Wirklich fortfahren?
{noformat}
was:
There are some issues with a configured mark as deleted feature in the data
module.
# there is no deleted icon in front of the marked as deleted data node
# the delete pop-up message is still the old delete message
# the 'delete-all' action is not covered by the extended delete behavior
> Mark as deleted don't work for data
> ---
>
> Key: MGNLDATA-157
> URL: http://jira.magnolia-cms.com/browse/MGNLDATA-157
> Project: Magnolia Data Module
> Issue Type: Improvement
>Affects Versions: 1.7.3
>Reporter: Frank Sommer
>Assignee: Philipp Bärfuss
>
> There are some issues with a configured mark as deleted feature in the data
> module.
> # there is no deleted icon in front of the marked as deleted data node
> # the delete pop-up message is still the old delete message
> # the 'delete-all' action is not covered by the extended delete behavior
> # typo in the german confirmation message
> (x)
> {noformat}
> tree.references.confirm.text.js=Warnung: Der Knoten wird zum Löschen markiert
> (diese Operation kann rückgängig gemacht werden), aber es wurden
> Abhängigkeiten zum ihm gefunden. Falls Sie Löschen bestätigen, werden die
> folgenden Seiten ungültige Referenzen enthalten. Wirklich fortfahren?
> {noformat}
> (/)
> {noformat}
> tree.references.confirm.text.js=Warnung: Der Knoten wird zum Löschen markiert
> (diese Operation kann rückgängig gemacht werden), aber es wurden
> Abhängigkeiten zu ihm gefunden. Falls Sie Löschen bestätigen, werden die
> folgenden Seiten ungültige Referenzen enthalten. Wirklich fortfahren?
> {noformat}
--
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:
[magnolia-dev] [JIRA] Created: (MGNLUI-389) Tree bouble click configuration
Tree bouble click configuration --- Key: MGNLUI-389 URL: http://jira.magnolia-cms.com/browse/MGNLUI-389 Project: Magnolia UI Issue Type: Task Security Level: Public Components: configuration, design, dialogs Affects Versions: 5.0 Alpha1 s009 Reporter: Eric Hechinger Priority: Major Fix For: 5.0 Alpha2 s011 When double clicking on an tree element we should be able to configure the dialog to open: For example in the asset App: Double click on a folder should open the folder dialog Double click on a asset should open the asset sub app dialog. -- 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:
[magnolia-dev] [JIRA] Created: (MGNLUI-390) Users are created under root after a deletion happens
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 Alpha1 s010 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:
[magnolia-dev] Re: mgnl 4.5.x how to use MyMessagesManager instead of DefaultMessagesManager?
Hi Tobias, tested adding [code] system info.magnolia.cms.i18n.MessagesManager net.sourceforge.openutils.mgnlmessages.i18n.MultiBundleMgnlMessagesManager [/code] but the behavior doesn't change. The new messageManager is used but init() gets never called. -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=23d7fd89-dedd-450e-9e77-c741088713fd 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:
