[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 ] Daniel Lipp updated MGNLDATA-162: - Fix Version/s: 1.8.0 Alpha2 s011 (was: 1.8.0 Alpha1) 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 Alpha2 s011 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] 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 Alpha2 s011 (was: 2.5) 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 Alpha2 s011 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] Code unfreeze of 4.5.7
Hi list, release 4.5.7 almost done. So we are unfreezing 4.5.x branch of main project and bundles. Also every module included in this release MGNLSTK 2.0.7, MGNLETK 2.0.7, MGNLPUR 1.4.2, MGNLFORM 1.4.4, MGNLDIFF 1.1.3, MGNLWEBDAV 1.1.1, MGNLJNDI 1.0.2, MGNLCMNT 1.2.3, MGNLCAT 1.2.4, MGNLFORUM 1.3.2, MGNLDMS 1.6.5, MGNLRES 1.5.5, MGNLRSSAGG 1.3.4, MGNLIMG 2.2.2, MGNLADVCACHE 1.4, MGNLSCH 1.5.4, MGNLINTEMPL 1.3.1, MGNLXAA 1.3.5, MGNLMIGRATION 1.2, MGNLBACKUP 1.2.2, MGNLGROOVY 1.2.4 Happy push Milan 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-4725) ItemNotFoundException thrown by DelegateNodeWrapper
ItemNotFoundException thrown by DelegateNodeWrapper
Key: MAGNOLIA-4725
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4725
Project: Magnolia
Issue Type: Bug
Security Level: Public
Components: core
Affects Versions: 4.5.6
Reporter: Tomas Brimor
{code}
2012-12-12 11:04:27,008 ERROR
magnolia.templating.jsp.taglib.SimpleNavigationTag: Failed to obtain parent
page for /XXX/CCC/content/02
javax.jcr.ItemNotFoundException: Root node doesn't have a parent
at org.apache.jackrabbit.core.NodeImpl$6.perform(NodeImpl.java:1712)
at org.apache.jackrabbit.core.NodeImpl$6.perform(NodeImpl.java:1705)
at
org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216)
at org.apache.jackrabbit.core.ItemImpl.perform(ItemImpl.java:91)
at org.apache.jackrabbit.core.NodeImpl.getParent(NodeImpl.java:1705)
at
info.magnolia.jcr.wrapper.DelegateNodeWrapper.getParent(DelegateNodeWrapper.java:484)
at
info.magnolia.jcr.decoration.ContentDecoratorNodeWrapper.getParent(ContentDecoratorNodeWrapper.java:89)
at
info.magnolia.jcr.wrapper.DelegateNodeWrapper.getParent(DelegateNodeWrapper.java:484)
at
info.magnolia.jcr.wrapper.I18nNodeWrapper.getParent(I18nNodeWrapper.java:87)
at
info.magnolia.cms.core.DefaultContent.getParent(DefaultContent.java:343)
at
info.magnolia.templating.jsp.taglib.SimpleNavigationTag.doEndTag(SimpleNavigationTag.java:360)
at
freemarker.ext.jsp.TagTransformModel$TagWriter.endEvaluation(TagTransformModel.java:430)
at
freemarker.ext.jsp.TagTransformModel$TagWriter.onStart(TagTransformModel.java:369)
at freemarker.core.Environment.visit(Environment.java:307)
at freemarker.core.UnifiedCall.accept(UnifiedCall.java:130)
at freemarker.core.Environment.visit(Environment.java:221)
at freemarker.core.MixedContent.accept(MixedContent.java:92)
at freemarker.core.Environment.visit(Environment.java:221)
at freemarker.core.Environment.process(Environment.java:199)
at freemarker.template.Template.process(Template.java:237)
at
info.magnolia.freemarker.FreemarkerHelper.render(FreemarkerHelper.java:155)
at
info.magnolia.rendering.renderer.FreemarkerRenderer.onRender(FreemarkerRenderer.java:85)
at
info.magnolia.rendering.renderer.AbstractRenderer.render(AbstractRenderer.java:139)
at
info.magnolia.rendering.engine.DefaultRenderingEngine.render(DefaultRenderingEngine.java:97)
at
info.magnolia.rendering.engine.DefaultRenderingEngine$$EnhancerByCGLIB$$584c3508.render(generated)
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)
at freemarker.core.IteratorBlock$Context.runLoop(IteratorBlock.java:179)
at freemarker.core.Environment.visit(Environment.java:428)
{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] Created: (MAGNOLIA-4726) Array-Style GET Parameters break rendering
Array-Style GET Parameters break rendering -- Key: MAGNOLIA-4726 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4726 Project: Magnolia Issue Type: Bug Security Level: Public Environment: Magnolia 4.5 EE, CE running under Linux, but I doubt this affects the problem. Reporter: Richard Unger Priority: Major Any request containing array-style GET parameters causes rendering to fail. Try it out using: http://demopublic.magnolia-cms.com/demo-project.html?checkbox[]=1 For example, parameters are normally sent in this syntax when a form contains multiple checkboxes belonging to the same group. The Problem does not occur in Magnolia 4.4.8 The Problem occurs in Magnolia 4.5.x (I didn't test all versions) -- 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-4725) ItemNotFoundException thrown by DelegateNodeWrapper
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Haderka updated MAGNOLIA-4725:
--
Fix Version/s: 4.5.8
ItemNotFoundException thrown by DelegateNodeWrapper
Key: MAGNOLIA-4725
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4725
Project: Magnolia
Issue Type: Bug
Security Level: Public
Components: core
Affects Versions: 4.5.6
Reporter: Tomas Brimor
Fix For: 4.5.8
{code}
2012-12-12 11:04:27,008 ERROR
magnolia.templating.jsp.taglib.SimpleNavigationTag: Failed to obtain parent
page for /XXX/CCC/content/02
javax.jcr.ItemNotFoundException: Root node doesn't have a parent
at org.apache.jackrabbit.core.NodeImpl$6.perform(NodeImpl.java:1712)
at org.apache.jackrabbit.core.NodeImpl$6.perform(NodeImpl.java:1705)
at
org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216)
at org.apache.jackrabbit.core.ItemImpl.perform(ItemImpl.java:91)
at org.apache.jackrabbit.core.NodeImpl.getParent(NodeImpl.java:1705)
at
info.magnolia.jcr.wrapper.DelegateNodeWrapper.getParent(DelegateNodeWrapper.java:484)
at
info.magnolia.jcr.decoration.ContentDecoratorNodeWrapper.getParent(ContentDecoratorNodeWrapper.java:89)
at
info.magnolia.jcr.wrapper.DelegateNodeWrapper.getParent(DelegateNodeWrapper.java:484)
at
info.magnolia.jcr.wrapper.I18nNodeWrapper.getParent(I18nNodeWrapper.java:87)
at
info.magnolia.cms.core.DefaultContent.getParent(DefaultContent.java:343)
at
info.magnolia.templating.jsp.taglib.SimpleNavigationTag.doEndTag(SimpleNavigationTag.java:360)
at
freemarker.ext.jsp.TagTransformModel$TagWriter.endEvaluation(TagTransformModel.java:430)
at
freemarker.ext.jsp.TagTransformModel$TagWriter.onStart(TagTransformModel.java:369)
at freemarker.core.Environment.visit(Environment.java:307)
at freemarker.core.UnifiedCall.accept(UnifiedCall.java:130)
at freemarker.core.Environment.visit(Environment.java:221)
at freemarker.core.MixedContent.accept(MixedContent.java:92)
at freemarker.core.Environment.visit(Environment.java:221)
at freemarker.core.Environment.process(Environment.java:199)
at freemarker.template.Template.process(Template.java:237)
at
info.magnolia.freemarker.FreemarkerHelper.render(FreemarkerHelper.java:155)
at
info.magnolia.rendering.renderer.FreemarkerRenderer.onRender(FreemarkerRenderer.java:85)
at
info.magnolia.rendering.renderer.AbstractRenderer.render(AbstractRenderer.java:139)
at
info.magnolia.rendering.engine.DefaultRenderingEngine.render(DefaultRenderingEngine.java:97)
at
info.magnolia.rendering.engine.DefaultRenderingEngine$$EnhancerByCGLIB$$584c3508.render(generated)
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)
at freemarker.core.IteratorBlock$Context.runLoop(IteratorBlock.java:179)
at freemarker.core.Environment.visit(Environment.java:428)
{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: (MGNLGROOVY-63) XSS scripting vulnerability
[ http://jira.magnolia-cms.com/browse/MGNLGROOVY-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kovařík updated MGNLGROOVY-63: Fix Version/s: 1.1.3 (was: 1.2.4) Affects Version/s: 1.1.2 (was: 1.2.2) XSS scripting vulnerability --- Key: MGNLGROOVY-63 URL: http://jira.magnolia-cms.com/browse/MGNLGROOVY-63 Project: Magnolia Groovy Module Issue Type: Bug Affects Versions: 1.1.2 Reporter: Roman Kovařík Assignee: Roman Kovařík Priority: Blocker Fix For: 1.1.3 add 21) Ability to run XSS from console -- 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: (MGNLGROOVY-63) XSS scripting vulnerability
XSS scripting vulnerability --- Key: MGNLGROOVY-63 URL: http://jira.magnolia-cms.com/browse/MGNLGROOVY-63 Project: Magnolia Groovy Module Issue Type: Bug Affects Versions: 1.2.2 Reporter: Roman Kovařík Assignee: Roman Kovařík Priority: Blocker Fix For: 1.2.4 add 21) Ability to run XSS from console -- 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: (MGNLWORKFLOW-17) Initiate Workflow programatically
Initiate Workflow programatically
-
Key: MGNLWORKFLOW-17
URL: http://jira.magnolia-cms.com/browse/MGNLWORKFLOW-17
Project: Magnolia Workflow Module
Issue Type: Support Request
Components: OpenWFE
Affects Versions: 1.0
Environment: Windows 7 with Magnolia 4.5.3 using Mysql as the DB
Reporter: SenthilNathan
Assignee: Jozef Chocholacek
Priority: Critical
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/ /sequence process-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)-- if
defined 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
--
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-4727) Getting ItemNotFoundException continuously
Getting ItemNotFoundException continuously -- Key: MAGNOLIA-4727 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4727 Project: Magnolia Issue Type: Bug Security Level: Public Affects Versions: 4.5.4 Environment: Windows 7 with Magnolia 4.5.3 using Mysql as the DB Reporter: SenthilNathan Priority: Critical We are having two webapps (Author and public) in two seperate boxes with mysql as the primary repository in each box. The application was running good. we will backup the repository (both DB and the folder under webapps) on a daily basis in each instance. We got the following exception suddenly in our author instance. WARN jackrabbit.core.query.lucene.DocOrderScoreNodeIterator: Node 98f3cd64-d449-4faa-8a16-e0de49384d87 does not exist anymore: javax.jcr.ItemNotFoundException: 98f3cd64-d449-4faa-8a16-e0de49384d87 . We got this exception continuously in the console with different uuid values. Of course this filled up the memory of log files. Work Around we Tried: We stopped the server and we cleaned up the repository and replaced both DB and repository folder with the previous one (backed up on yesterday). Again we got the same exception continuously with different uuid values. It stopped only when we cleaned the repository fully and started the server. Whenever this exception occurs, our old repository backup is not helping us. We have to let the server create a new repository everytime. Please provide us any solution for this. -- 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-262) Do not use hardcoded captions for apps
[
http://jira.magnolia-cms.com/browse/MGNLUI-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Federico Grilli updated MGNLUI-262:
---
Assignee: Federico Grilli
Fix Version/s: 5.0 Alpha2 s011
(was: 5.0)
Affects Version/s: 5.0 Alpha1
Do not use hardcoded captions for apps
--
Key: MGNLUI-262
URL: http://jira.magnolia-cms.com/browse/MGNLUI-262
Project: Magnolia UI
Issue Type: Improvement
Security Level: Public
Components: content app
Affects Versions: 5.0 Alpha1
Reporter: Federico Grilli
Assignee: Federico Grilli
Priority: Major
Fix For: 5.0 Alpha2 s011
In many content apps, i.e. info.magnolia.ui.app.contacts.ContactsMainSubApp I
am seeing overriding {{AbstractContentSubApp#getCaption()}} method and return
an hardcoded string with (sub)app name. Since sub and app descriptors already
provide us with this info, it would make coding an Content App even simpler
and cleaner if we'd just used that caption in the default impl of
{{AbstractContentSubApp#getCaption()}}. Something like the following. Notice
that if the subAppDescriptor#getLabel() is blank we fallback to the
appDescriptor()#getLabel(). If the latter is blank too we warn the user with
a message.
{code}
@Override
public String getCaption() {
String label = subAppContext.getSubAppDescriptor().getLabel();
if(StringUtils.isNotBlank(label)) {
return label;
}
label = subAppContext.getAppContext().getAppDescriptor().getLabel();
return StringUtils.isNotBlank(label) ? label : missing App label;
}
{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: (MAGNOLIA-4726) Array-Style GET Parameters break rendering
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka updated MAGNOLIA-4726: -- Fix Version/s: 4.5.8 Affects Version/s: 4.5 Array-Style GET Parameters break rendering -- Key: MAGNOLIA-4726 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4726 Project: Magnolia Issue Type: Bug Security Level: Public Affects Versions: 4.5 Environment: Magnolia 4.5 EE, CE running under Linux, but I doubt this affects the problem. Reporter: Richard Unger Priority: Major Fix For: 4.5.8 Any request containing array-style GET parameters causes rendering to fail. Try it out using: http://demopublic.magnolia-cms.com/demo-project.html?checkbox[]=1 For example, parameters are normally sent in this syntax when a form contains multiple checkboxes belonging to the same group. The Problem does not occur in Magnolia 4.4.8 The Problem occurs in Magnolia 4.5.x (I didn't test all versions) -- 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: (MGNLWORKFLOW-18) Empty nodes of finished workflow still exist (Expressions workspace)
Empty nodes of finished workflow still exist (Expressions workspace) Key: MGNLWORKFLOW-18 URL: http://jira.magnolia-cms.com/browse/MGNLWORKFLOW-18 Project: Magnolia Workflow Module Issue Type: Bug Environment: Magnolia EE 4.5.6, Tomcat 7, Java 6, OS X Reporter: Andreas Antener Assignee: Jozef Chocholacek Priority: Minor Attachments: expressions.txt, libs.txt, magnolia-debug.log The nodes in the Expressions workspace won't get deleted after a finished workflow. Steps to reproduce: - Start Magnolia (public and author) with workflow module, no repositories yet - Login with superuser - Create a page - Activate that page - Go to inbox and proceed with the activation - Check the Expressions workspace under /owfe/activation There I have 2 empty nodes now. See attachments for debug-log, libs and listing from JCR query. -- 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: (MGNLMIGRATION-69) Create RunGroovyScriptTask
[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grégory Joseph updated MGNLMIGRATION-69: Fix Version/s: (was: 1.2) Affects Version/s: 1.2 If an issue is obsolete, it's not fixed, and shouldn't have a fix version, IMO. (unsetting the fix version field to generate release-participants list) Create RunGroovyScriptTask -- Key: MGNLMIGRATION-69 URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-69 Project: Magnolia Migration Issue Type: Improvement Affects Versions: 1.2 Reporter: Jozef Chocholacek A general task to run Groovy script (specified on creation). -- 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-4449) Protected Page does not redirect to the login page
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grégory Joseph updated MAGNOLIA-4449:
-
Fix Version/s: (was: 4.5.7)
Affects Version/s: 4.5.7
If an issue is obsolete, it's not fixed, and shouldn't have a fix version,
IMO.
(unsetting the fix version field to generate release-participants list)
Protected Page does not redirect to the login page
--
Key: MAGNOLIA-4449
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4449
Project: Magnolia
Issue Type: Bug
Security Level: Public
Components: security
Affects Versions: 4.4.6, 4.5, 4.5.7
Reporter: Christian Ringele
Priority: Critical
Anonymous role has deny access to /demo-project/members-area/protected* ,
this rule should be used in
{{info.magnolia.cms.security.URISecurityFilter.isAuthorized(HttpServletRequest)}},
but this doesn't happen due to this rule pattern doesn't match with current
uri. {{info.magnolia.cms.core.AggregationState.getCurrentURI()}} has value
/members-area/protected because
{{info.magnolia.module.extendedtemplatingkit.filters.MultiSiteFilter}}
removes site definition name from uri.
--
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-4449) Protected Page does not redirect to the login page
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grégory Joseph updated MAGNOLIA-4449:
-
Comment: was deleted
(was: If an issue is obsolete, it's not fixed, and shouldn't have a fix
version, IMO.
(unsetting the fix version field to generate release-participants list))
Protected Page does not redirect to the login page
--
Key: MAGNOLIA-4449
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4449
Project: Magnolia
Issue Type: Bug
Security Level: Public
Components: security
Affects Versions: 4.4.6, 4.5, 4.5.7
Reporter: Christian Ringele
Assignee: Ondřej Chytil
Priority: Critical
Fix For: 4.5.7
Anonymous role has deny access to /demo-project/members-area/protected* ,
this rule should be used in
{{info.magnolia.cms.security.URISecurityFilter.isAuthorized(HttpServletRequest)}},
but this doesn't happen due to this rule pattern doesn't match with current
uri. {{info.magnolia.cms.core.AggregationState.getCurrentURI()}} has value
/members-area/protected because
{{info.magnolia.module.extendedtemplatingkit.filters.MultiSiteFilter}}
removes site definition name from uri.
--
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] Reopened: (MAGNOLIA-4449) Protected Page does not redirect to the login page
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grégory Joseph reopened MAGNOLIA-4449:
--
Assignee: Ondřej Chytil
reopening to set resolution
Protected Page does not redirect to the login page
--
Key: MAGNOLIA-4449
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4449
Project: Magnolia
Issue Type: Bug
Security Level: Public
Components: security
Affects Versions: 4.4.6, 4.5, 4.5.7
Reporter: Christian Ringele
Assignee: Ondřej Chytil
Priority: Critical
Fix For: 4.5.7
Anonymous role has deny access to /demo-project/members-area/protected* ,
this rule should be used in
{{info.magnolia.cms.security.URISecurityFilter.isAuthorized(HttpServletRequest)}},
but this doesn't happen due to this rule pattern doesn't match with current
uri. {{info.magnolia.cms.core.AggregationState.getCurrentURI()}} has value
/members-area/protected because
{{info.magnolia.module.extendedtemplatingkit.filters.MultiSiteFilter}}
removes site definition name from uri.
--
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-4449) Protected Page does not redirect to the login page
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grégory Joseph updated MAGNOLIA-4449:
-
Comment: was deleted
(was: reopening to set resolution)
Protected Page does not redirect to the login page
--
Key: MAGNOLIA-4449
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4449
Project: Magnolia
Issue Type: Bug
Security Level: Public
Components: security
Affects Versions: 4.4.6, 4.5, 4.5.7
Reporter: Christian Ringele
Assignee: Ondřej Chytil
Priority: Critical
Fix For: 4.5.7
Anonymous role has deny access to /demo-project/members-area/protected* ,
this rule should be used in
{{info.magnolia.cms.security.URISecurityFilter.isAuthorized(HttpServletRequest)}},
but this doesn't happen due to this rule pattern doesn't match with current
uri. {{info.magnolia.cms.core.AggregationState.getCurrentURI()}} has value
/members-area/protected because
{{info.magnolia.module.extendedtemplatingkit.filters.MultiSiteFilter}}
removes site definition name from uri.
--
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
