[magnolia-dev] [JIRA] Updated: (MGNLFORM-126) Back button should not be implemented with a Javascript history(-1) link!
[ http://jira.magnolia-cms.com/browse/MGNLFORM-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MGNLFORM-126: --- Fix Version/s: 1.4.2 Thanks for reporting Will, added for next release. Back button should not be implemented with a Javascript history(-1) link! - Key: MGNLFORM-126 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-126 Project: Magnolia Form Module Issue Type: Bug Affects Versions: 1.4.1 Reporter: Will Scheidegger Priority: Major Fix For: 1.4.2 The current implementation of the back button is useless. As soon as a validation error occurs, the user is not taken back to the previous step but rather to the same step before the validation. The form engine should always know all its steps and be able to navigation from one step to the next and back. To cope with the new condition-feature the engine should keep track of the previous steps in its own history-stack. -- 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] AUTO: Marc Bechtiger is out of the office. (returning 28.05.2012)
I am out of the office until 28.05.2012. I will respond to your message when I return. Note: This is an automated response to your message [magnolia-dev] [JIRA] Updated: (MGNLFORM-126) Back button should not be implemented with a Javascript history(-1) link! sent on 04.05.2012 08:39:43. This is the only notification you will receive while this person is away. 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-4401) Simplify EditorLinkTransformer
Simplify EditorLinkTransformer -- Key: MAGNOLIA-4401 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4401 Project: Magnolia Issue Type: Improvement Security Level: Public Affects Versions: 4.5.2, 4.4.7 Reporter: Daniel Lipp Fix For: 4.4.8, 4.5.3 Current implementation of EditorLinkTransformer keeps two identically configured LinkTransformers (binaryTransformer, linkTransformer) where one should do it. In addition it looks like in 4.5.x EditorLinkTransformer is no longer used at all so I'd recommend @deprecate it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/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: (MGNLFORM-127) Display only first value of Selection Form field
Display only first value of Selection Form field Key: MGNLFORM-127 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-127 Project: Magnolia Form Module Issue Type: Bug Affects Versions: 1.4.1 Reporter: Sven Damm See http://demoauthor.magnolia-cms.com/demo-features/special-templates/multi-step-form/enter-topic.html Try to select Track. Only one radio button is displayed -- 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-948) multiselect doesn't show saved data
multiselect doesn't show saved data --- Key: MGNLSTK-948 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-948 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: controls Environment: Firefox 12 Reporter: Robert Assignee: Philipp Bärfuss Attachments: Auswahl_004.png, Auswahl_005.png, Auswahl_006.png when you use multiselect control in a dialog, as shown in the screenshots (screen 005) you can save data - no problem here (screen 004). but if you wana edit the data, none is shown in the dialog (screen 006). it might be a wrong dialog setup, but i think it could as well be a bug. -- 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: (BLOSSOM-88) info.magnolia.module.blossom.annotation.Paragraph and Spring Security doesn't work together
info.magnolia.module.blossom.annotation.Paragraph and Spring Security doesn't
work together
---
Key: BLOSSOM-88
URL: http://jira.magnolia-cms.com/browse/BLOSSOM-88
Project: Magnolia Blossom Module
Issue Type: Bug
Affects Versions: 1.2.2
Environment: OS X 10.7.3, JRE 1.6.0_31-b04-415-11M3635, Tomcat 6.0.32
Reporter: Angel Gerdzhikov
Assignee: Tobias Mattsson
Priority: Major
If you have something like this:
{code:title=ContentSection.java|borderStyle=solid}
@Controller
@Paragraph(ContentSection)
@ParagraphDescription(Displays substructure of a section and enables creating
and deleting pages and folders)
public class ContentSection
{
@PreAuthorize(hasPermission('nodeUUID', 'uuid',
T(info.magnolia.cms.security.Permission).WRITE))
@RequestMapping(/contentSection)
public
ModelAndView
handleRequest(Content page, Content paragraph) throws
RepositoryException
{
...
}
}
{code}
and Spring Security is activated, the Blossom-Paragraph is not registered and
can't be found. The reason is, that the Spring Security creates a CGLIB proxy
and the Paragraph annotation is not inherited. The problem is in
info.magnolia.module.blossom.paragraph.ParagraphExporter.postProcessHandler().
I guess I'll have the same problem when I use the Template annotation and
Spring security.
Is there any workaround to handle this issue?
--
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-151) ItemTypes cannot be deleted when their rootPath is not on the top level
ItemTypes cannot be deleted when their rootPath is not on the top level - Key: MGNLDATA-151 URL: http://jira.magnolia-cms.com/browse/MGNLDATA-151 Project: Magnolia Data Module Issue Type: Bug Affects Versions: 1.6.4 Reporter: Will Scheidegger Assignee: Philipp Bärfuss Attachments: itemsExist.patch If you have defined a data node type which has its root on level 1 you'll get a NPE when trying to delete the item type. 2012-05-05 07:04:18,637 ERROR fo.magnolia.module.data.commands.TypeDeleteCommand: cannot do delete java.lang.NullPointerException at info.magnolia.module.data.commands.TypeDeleteCommand.itemsExist(TypeDeleteCommand.java:119) This is caused by the use of (deprecated) .getChildByName() which of course does not work for something like /customer/products. The attached patch uses ContentUtil.getContent(repository, path) instead and therefore also works with nested root nodes. -- 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
