[magnolia-dev] Hudson build is still unstable: magnolia_main-trunk #1087
See http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1087/changes For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] Hudson build became unstable: ma gnolia_main-trunk » magnolia-module-exchange-si mple #1087
See http://hudson.magnolia-cms.com/job/magnolia_main-trunk/info.magnolia$magnolia-module-exchange-simple/1087/ For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] Hudson build is back to stable: magnolia_main-trunk » magnolia-module-templati ng #1087
See http://hudson.magnolia-cms.com/job/magnolia_main-trunk/info.magnolia$magnolia-module-templating/1087/changes For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2931) templating: the renderer should not only wrap the content for the template but for the model too
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=24780#action_24780 ] Hudson CI server commented on MAGNOLIA-2931: Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/yellow.gif! [magnolia_main-trunk #1087|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1087/] : fixed tests : - made the two wrapping methods (for template and model) independent as this makes things easier for the JSP subclasses - fixed tests templating: the renderer should not only wrap the content for the template but for the model too Key: MAGNOLIA-2931 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2931 Project: Magnolia Issue Type: Improvement Components: templating Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss Fix For: 4.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] Hudson build is back to stable: magnolia_main-trunk » magnolia-module-exchange -simple #1088
See http://hudson.magnolia-cms.com/job/magnolia_main-trunk/info.magnolia$magnolia-module-exchange-simple/1088/changes For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] Hudson build became unstable: ma gnolia_main-trunk » magnolia-module-cache #10 88
See http://hudson.magnolia-cms.com/job/magnolia_main-trunk/info.magnolia$magnolia-module-cache/1088/ For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] Hudson build is still unstable: magnolia_main-trunk #1088
See http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1088/changes For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2903) activation: users having only write permission in a subpart of the hierarchy are not able to activate
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=24781#action_24781 ] Hudson CI server commented on MAGNOLIA-2903: Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/yellow.gif! [magnolia_main-trunk #1088|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1088/] Store the temporary node at the same level as the currently activated node. activation: users having only write permission in a subpart of the hierarchy are not able to activate -- Key: MAGNOLIA-2903 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2903 Project: Magnolia Issue Type: Bug Components: activation Affects Versions: 4.1.1 Reporter: Philipp Bärfuss Assignee: Jan Haderka Priority: Critical Fix For: 4.1.x, 4.2 In the following line a temporary node is created in the root of the workspace (the node name is the uuid) -- ReceiveFilter.importOnExisting(ReceiveFilter.java:420) If a user cannot write to the root, but only to a sub hierarchy, he cannot create this temporary 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/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-2932) update: task to boostrap a single module bootstrap file
update: task to boostrap a single module bootstrap file --- Key: MAGNOLIA-2932 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2932 Project: Magnolia Issue Type: Improvement Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss Priority: Minor Fix For: 4.2 It is very annoying that we have always to pass the full path to the current BootstrapSingleResource task. A specialized task taking only the relative path to the module's bootstrap file would make the code more readable and less error prone. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] Hudson build became unstable: ma gnolia_main-trunk » magnolia-module-exchange-si mple #1089
See http://hudson.magnolia-cms.com/job/magnolia_main-trunk/info.magnolia$magnolia-module-exchange-simple/1089/ For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] Hudson build is back to stable: magnolia_main-trunk » magnolia-module-cache #1089
See http://hudson.magnolia-cms.com/job/magnolia_main-trunk/info.magnolia$magnolia-module-cache/1089/ For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] Hudson build is still unstable: magnolia_main-trunk #1089
See http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1089/changes For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2932) update: task to boostrap a single module bootstrap file
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=24782#action_24782 ] Hudson CI server commented on MAGNOLIA-2932: Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/yellow.gif! [magnolia_main-trunk #1089|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1089/] : task to boostrap a single module bootstrap file by passing a relative path update: task to boostrap a single module bootstrap file --- Key: MAGNOLIA-2932 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2932 Project: Magnolia Issue Type: Improvement Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss Priority: Minor Fix For: 4.2 It is very annoying that we have always to pass the full path to the current BootstrapSingleResource task. A specialized task taking only the relative path to the module's bootstrap file would make the code more readable and less error prone. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] Hudson build is still unstable: magnolia_main-trunk #1090
See http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1090/ For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] Hudson build is still unstable: magnolia_main-trunk » magnolia-module-exchange -simple #1090
See http://hudson.magnolia-cms.com/job/magnolia_main-trunk/info.magnolia$magnolia-module-exchange-simple/1090/ For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] Hudson build is back to stable: magnolia_main-trunk » magnolia-module-exchange -simple #1091
See http://hudson.magnolia-cms.com/job/magnolia_main-trunk/info.magnolia$magnolia-module-exchange-simple/1091/ For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] Hudson build is back to stable: magnolia_main-trunk #1091
See http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1091/ For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2897) Introduce a simpler api to build nodes/properties
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=24784#action_24784 ] Hudson CI server commented on MAGNOLIA-2897: Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! [standard-templating-kit #2140|http://hudson.magnolia-cms.com/job/standard-templating-kit/2140/] : - dropped the duplicates working on the context itself (they were confusing) - extracted the recursive operations Introduce a simpler api to build nodes/properties - Key: MAGNOLIA-2897 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2897 Project: Magnolia Issue Type: New Feature Components: core Reporter: Grégory Joseph Assignee: Grégory Joseph Fix For: 4.2 We've had the need several times for a simple node building api - especially in version handlers - to construct relatively simple nodes (couple of nodes, couple of properties) without having to maintain complex bootstrap or properties file, and verbose/long code. We'll introduce a simple DSL/API similar to the one used to build tasks and deltas for this. Hopefully this will be easy-to-use and follow some of the fluent principles. A starting point was proposed at MAGNOLIA-2828; after some discussion we've adapted it and came up with a slightly different implementation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2897) Introduce a simpler api to build nodes/properties
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=24785#action_24785 ] Hudson CI server commented on MAGNOLIA-2897: Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! [magnolia_main-trunk #1093|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1093/] : - dropped the duplicates working on the context itself (they were confusing) - extracted the recursive operations Introduce a simpler api to build nodes/properties - Key: MAGNOLIA-2897 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2897 Project: Magnolia Issue Type: New Feature Components: core Reporter: Grégory Joseph Assignee: Grégory Joseph Fix For: 4.2 We've had the need several times for a simple node building api - especially in version handlers - to construct relatively simple nodes (couple of nodes, couple of properties) without having to maintain complex bootstrap or properties file, and verbose/long code. We'll introduce a simple DSL/API similar to the one used to build tasks and deltas for this. Hopefully this will be easy-to-use and follow some of the fluent principles. A starting point was proposed at MAGNOLIA-2828; after some discussion we've adapted it and came up with a slightly different implementation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Work started: (MAGNOLIA-2903) activation: users having only write permission in a subpart of the hierarchy are not able to activate
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MAGNOLIA-2903 started by Jan Haderka. activation: users having only write permission in a subpart of the hierarchy are not able to activate -- Key: MAGNOLIA-2903 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2903 Project: Magnolia Issue Type: Bug Components: activation Affects Versions: 4.1.1 Reporter: Philipp Bärfuss Assignee: Jan Haderka Priority: Critical Fix For: 4.1.x, 4.2 In the following line a temporary node is created in the root of the workspace (the node name is the uuid) -- ReceiveFilter.importOnExisting(ReceiveFilter.java:420) If a user cannot write to the root, but only to a sub hierarchy, he cannot create this temporary 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/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Work started: (MAGNOLIA-2901) Moving nodes in adminCentral shows moved node content as parent node content
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MAGNOLIA-2901 started by Jan Haderka. Moving nodes in adminCentral shows moved node content as parent node content Key: MAGNOLIA-2901 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2901 Project: Magnolia Issue Type: Bug Components: admininterface Affects Versions: 4.1.1 Environment: Browsers I tested on: Firefox Safari Reporter: Christian Ringele Assignee: Jan Haderka Priority: Critical Fix For: 4.1.2, 4.2 Attachments: MAGNOLIA-2901-after-move.png, MAGNOLIA-2901-before-move.png When moving a node in admin central to a different parent node, the tree only shows the content of the moved node (subnodes) instead of the whole tree. The move occurs properly, and this is only a visual issue. It doesn't seem to be specific to any workspace (reproduced on config, website, dms, ...) nor instance (reproduced on several local ones, demoauthor, ...) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Assigned: (MAGNOLIA-2901) Moving nodes in adminCentral shows moved node content as parent node content
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka reassigned MAGNOLIA-2901: - Assignee: Jan Haderka (was: Philipp Bärfuss) Moving nodes in adminCentral shows moved node content as parent node content Key: MAGNOLIA-2901 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2901 Project: Magnolia Issue Type: Bug Components: admininterface Affects Versions: 4.1.1 Environment: Browsers I tested on: Firefox Safari Reporter: Christian Ringele Assignee: Jan Haderka Priority: Critical Fix For: 4.1.2, 4.2 Attachments: MAGNOLIA-2901-after-move.png, MAGNOLIA-2901-before-move.png When moving a node in admin central to a different parent node, the tree only shows the content of the moved node (subnodes) instead of the whole tree. The move occurs properly, and this is only a visual issue. It doesn't seem to be specific to any workspace (reproduced on config, website, dms, ...) nor instance (reproduced on several local ones, demoauthor, ...) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLRES-21) Nice editor
[ http://jira.magnolia-cms.com/browse/MGNLRES-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MGNLRES-21: --- Fix Version/s: 1.2 Nice editor --- Key: MGNLRES-21 URL: http://jira.magnolia-cms.com/browse/MGNLRES-21 Project: Magnolia Resources Module Issue Type: Improvement Reporter: Federico Grilli Assignee: Federico Grilli Fix For: 1.2 Improve current editor by adding syntax highlighting, line numbers, etc. Use the codepress component. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Work started: (MGNLRES-21) Nice editor
[ http://jira.magnolia-cms.com/browse/MGNLRES-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MGNLRES-21 started by Federico Grilli. Nice editor --- Key: MGNLRES-21 URL: http://jira.magnolia-cms.com/browse/MGNLRES-21 Project: Magnolia Resources Module Issue Type: Improvement Reporter: Federico Grilli Assignee: Federico Grilli Fix For: 1.2 Improve current editor by adding syntax highlighting, line numbers, etc. Use the codepress component. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Resolved: (MAGNOLIA-2901) Moving nodes in adminCentral shows moved node content as parent node content
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka resolved MAGNOLIA-2901. --- Resolution: Fixed Done on trunk as of r29199 and on 4.1 branch as of r29345. Moving nodes in adminCentral shows moved node content as parent node content Key: MAGNOLIA-2901 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2901 Project: Magnolia Issue Type: Bug Components: admininterface Affects Versions: 4.1.1 Environment: Browsers I tested on: Firefox Safari Reporter: Christian Ringele Assignee: Jan Haderka Priority: Critical Fix For: 4.1.2, 4.2 Attachments: MAGNOLIA-2901-after-move.png, MAGNOLIA-2901-before-move.png When moving a node in admin central to a different parent node, the tree only shows the content of the moved node (subnodes) instead of the whole tree. The move occurs properly, and this is only a visual issue. It doesn't seem to be specific to any workspace (reproduced on config, website, dms, ...) nor instance (reproduced on several local ones, demoauthor, ...) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2901) Moving nodes in adminCentral shows moved node content as parent node content
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=24796#action_24796 ] Hudson CI server commented on MAGNOLIA-2901: Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! [magnolia_main-4.1-branch #4|http://hudson.magnolia-cms.com/job/magnolia_main-4.1-branch/4/] Do not modify the path after move/rename as it is also used during initialization to replace the rootPath. Backport of r29199. Moving nodes in adminCentral shows moved node content as parent node content Key: MAGNOLIA-2901 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2901 Project: Magnolia Issue Type: Bug Components: admininterface Affects Versions: 4.1.1 Environment: Browsers I tested on: Firefox Safari Reporter: Christian Ringele Assignee: Jan Haderka Priority: Critical Fix For: 4.1.2, 4.2 Attachments: MAGNOLIA-2901-after-move.png, MAGNOLIA-2901-before-move.png When moving a node in admin central to a different parent node, the tree only shows the content of the moved node (subnodes) instead of the whole tree. The move occurs properly, and this is only a visual issue. It doesn't seem to be specific to any workspace (reproduced on config, website, dms, ...) nor instance (reproduced on several local ones, demoauthor, ...) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] Build failed in Hudson: magnolia-module-public-user-registration #24
See http://hudson.magnolia-cms.com/job/magnolia-module-public-user-registration/24/changes Changes: [pbaerfuss] PUR: ready to be released -- A SCM change trigger started this job Updating http://svn.magnolia-cms.com/svn/community/modules/magnolia-module-public-user-registration/trunk U pom.xml At revision 29349 Parsing POMs [trunk] $ java -cp /usr/local/hudson/data/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.324.jar:/usr/local/hudson/maven/apache-maven-2.0.10/boot/classworlds-1.1.jar hudson.maven.agent.Main /usr/local/hudson/maven/apache-maven-2.0.10 /Library/Tomcat/work/Catalina/hudson.magnolia-cms.com/_/WEB-INF/lib/remoting-1.324.jar /usr/local/hudson/data/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.324.jar 52106 ===[HUDSON REMOTING CAPACITY]=== channel started Executing Maven: -B -f http://hudson.magnolia-cms.com/job/magnolia-module-public-user-registration/ws/trunk/pom.xml clean install [INFO] Scanning for projects... [INFO] [INFO] Building magnolia-module-public-user-registration [INFO]task-segment: [clean, install] [INFO] [INFO] [clean:clean] [INFO] Deleting directory http://hudson.magnolia-cms.com/job/magnolia-module-public-user-registration/ws/trunk/target [TASKS] Scanning folder 'http://hudson.magnolia-cms.com/job/magnolia-module-public-user-registration/ws/trunk/src/main/java' for tasks ... log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.converters.BooleanConverter). log4j:WARN Please initialize the log4j system properly. [TASKS] Found 15. [TASKS] Scanning folder 'http://hudson.magnolia-cms.com/job/magnolia-module-public-user-registration/ws/trunk/src/main/resources' for tasks ... [TASKS] Found 0. [TASKS] Scanning folder 'http://hudson.magnolia-cms.com/job/magnolia-module-public-user-registration/ws/trunk/src/main/resources' for tasks ... [TASKS] Found 0. [TASKS] File encoding has not been set in pom.xml, using platform encoding MacRoman, i.e. build is platform dependent (see a href=http://docs.codehaus.org/display/MAVENUSER/POM+Element+for+Source+File+Encoding;Maven FAQ/a). Downloading: http://repo.magnolia-cms.com/m2/info/magnolia/magnolia-core/4.2-beta1/magnolia-core-4.2-beta1.pom 5K downloaded Downloading: http://repo.magnolia-cms.com/m2/info/magnolia/magnolia-project/4.2-beta1/magnolia-project-4.2-beta1.pom 20K downloaded Downloading: http://repo.magnolia-cms.com/m2/info/magnolia/magnolia-module-admininterface/4.2-beta1/magnolia-module-admininterface-4.2-beta1.pom 3K downloaded Downloading: http://repo.magnolia-cms.com/m2/info/magnolia/magnolia-module-exchange-simple/4.2-beta1/magnolia-module-exchange-simple-4.2-beta1.pom 2K downloaded Downloading: http://repo.magnolia-cms.com/m2/info/magnolia/magnolia-gui/4.2-beta1/magnolia-gui-4.2-beta1.pom 2K downloaded Downloading: http://repo.magnolia-cms.com/m2/info/magnolia/magnolia-jaas/4.2-beta1/magnolia-jaas-4.2-beta1.pom 1K downloaded Downloading: http://repo.magnolia-cms.com/m2/info/magnolia/magnolia-module-templating/4.2-beta1/magnolia-module-templating-4.2-beta1.pom 2K downloaded Downloading: http://repo.magnolia-cms.com/m2/info/magnolia/magnolia-module-mail/4.2-beta1/magnolia-module-mail-4.2-beta1.pom 3K downloaded Downloading: http://repo.magnolia-cms.com/m2/info/magnolia/magnolia-module-form/1.1-m1/magnolia-module-form-1.1-m1.pom Downloading: http://repo.magnolia-cms.com/enterprise/info/magnolia/magnolia-module-form/1.1-m1/magnolia-module-form-1.1-m1.pom Downloading: http://repo.magnolia-cms.com/internal/info/magnolia/magnolia-module-form/1.1-m1/magnolia-module-form-1.1-m1.pom Downloading: http://repo.magnolia-cms.com/projects/info/magnolia/magnolia-module-form/1.1-m1/magnolia-module-form-1.1-m1.pom Downloading: http://repo.magnolia-cms.com/restricted/info/magnolia/magnolia-module-form/1.1-m1/magnolia-module-form-1.1-m1.pom Downloading: http://repo1.maven.org/maven2/info/magnolia/magnolia-module-form/1.1-m1/magnolia-module-form-1.1-m1.pom Downloading: http://repo.magnolia-cms.com/m2/info/magnolia/magnolia-core/4.2-beta1/magnolia-core-4.2-beta1.jar 866K downloaded Downloading: http://repo.magnolia-cms.com/m2/info/magnolia/magnolia-module-admininterface/4.2-beta1/magnolia-module-admininterface-4.2-beta1.jar 1084K downloaded Downloading: http://repo.magnolia-cms.com/m2/info/magnolia/magnolia-module-exchange-simple/4.2-beta1/magnolia-module-exchange-simple-4.2-beta1.jar 49K downloaded Downloading: http://repo.magnolia-cms.com/m2/info/magnolia/magnolia-gui/4.2-beta1/magnolia-gui-4.2-beta1.jar 166K downloaded Downloading: http://repo.magnolia-cms.com/m2/info/magnolia/magnolia-jaas/4.2-beta1/magnolia-jaas-4.2-beta1.jar 19K downloaded Downloading:
[magnolia-dev] [JIRA] Updated: (MGNLDATA-85) Sample content for hierarchical types
[ http://jira.magnolia-cms.com/browse/MGNLDATA-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka updated MGNLDATA-85: Fix Version/s: 1.4.1-rc1 (was: 1.4) Sample content for hierarchical types - Key: MGNLDATA-85 URL: http://jira.magnolia-cms.com/browse/MGNLDATA-85 Project: Magnolia Data Module Issue Type: Task Affects Versions: 1.4-m1 Reporter: Jan Haderka Assignee: Jan Haderka Fix For: 1.4.1-rc1 Provide simple sample content of using the hierarchical types. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLDATA-84) Type icons are not displayed properly
[ http://jira.magnolia-cms.com/browse/MGNLDATA-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka updated MGNLDATA-84: Fix Version/s: 1.4.1-rc1 (was: 1.4) Type icons are not displayed properly - Key: MGNLDATA-84 URL: http://jira.magnolia-cms.com/browse/MGNLDATA-84 Project: Magnolia Data Module Issue Type: Bug Affects Versions: 1.4-m1 Reporter: Jan Haderka Assignee: Jan Haderka Fix For: 1.4.1-rc1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLDATA-80) when workflow module is not installed, the following warning appears
[ http://jira.magnolia-cms.com/browse/MGNLDATA-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka updated MGNLDATA-80: Fix Version/s: 1.4.1-rc1 (was: 1.4) when workflow module is not installed, the following warning appears Key: MGNLDATA-80 URL: http://jira.magnolia-cms.com/browse/MGNLDATA-80 Project: Magnolia Data Module Issue Type: Bug Reporter: Zdenek Skodik Assignee: Jan Haderka Fix For: 1.4.1-rc1 WARN gnolia.content2bean.impl.Content2BeanProcessorImpl: can't resolve class for node /modules/data/commands/data/activate/startFlow java.lang.ClassNotFoundException: info.magnolia.module.workflow.commands.ActivationFlowCommand at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1386) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1232) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:242) at info.magnolia.cms.util.ClassUtil.classForName(ClassUtil.java:78) at info.magnolia.content2bean.impl.Content2BeanTransformerImpl.resolveType(Content2BeanTransformerImpl.java:106) at info.magnolia.content2bean.impl.Content2BeanProcessorImpl.toBean(Content2BeanProcessorImpl.java:78) at info.magnolia.content2bean.impl.Content2BeanProcessorImpl.toMap(Content2BeanProcessorImpl.java:167) at info.magnolia.content2bean.impl.Content2BeanProcessorImpl.toBean(Content2BeanProcessorImpl.java:95) at info.magnolia.content2bean.impl.Content2BeanProcessorImpl.toMap(Content2BeanProcessorImpl.java:167) at info.magnolia.content2bean.impl.Content2BeanProcessorImpl.toBean(Content2BeanProcessorImpl.java:95) at info.magnolia.content2bean.impl.Content2BeanProcessorImpl.toBean(Content2BeanProcessorImpl.java:69) at info.magnolia.content2bean.Content2BeanUtil.toBean(Content2BeanUtil.java:151) at info.magnolia.commands.CommandsManager.registerCatalog(CommandsManager.java:93) at info.magnolia.commands.CommandsManager.onRegister(CommandsManager.java:82) at info.magnolia.commands.CommandsManager.onRegister(CommandsManager.java:86) at info.magnolia.cms.beans.config.ObservedManager.register(ObservedManager.java:85) at info.magnolia.module.ModuleLifecycleContextImpl.initEntry(ModuleLifecycleContextImpl.java:88) at info.magnolia.module.ModuleLifecycleContextImpl.start(ModuleLifecycleContextImpl.java:80) at info.magnolia.module.ModuleManagerImpl.startModules(ModuleManagerImpl.java:355) at info.magnolia.module.ui.ModuleManagerWebUI$1.exec(ModuleManagerWebUI.java:104) at info.magnolia.context.MgnlContext.doInSystemContext(MgnlContext.java:377) at info.magnolia.module.ui.ModuleManagerWebUI.execute(ModuleManagerWebUI.java:101) at info.magnolia.cms.filters.InstallFilter.doFilter(InstallFilter.java:95) at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:70) at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:82) at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:84) at info.magnolia.cms.filters.CompositeFilter.doFilter(CompositeFilter.java:64) at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:70) at info.magnolia.cms.filters.MgnlMainFilter.doFilter(MgnlMainFilter.java:96) at info.magnolia.cms.filters.MgnlMainFilter.doFilter(MgnlMainFilter.java:199) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:875) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at
[magnolia-dev] [JIRA] Updated: (MGNLDATA-83) Don't create extra menu items for subtypes
[ http://jira.magnolia-cms.com/browse/MGNLDATA-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka updated MGNLDATA-83: Fix Version/s: 1.4.1-rc1 (was: 1.4) Don't create extra menu items for subtypes -- Key: MGNLDATA-83 URL: http://jira.magnolia-cms.com/browse/MGNLDATA-83 Project: Magnolia Data Module Issue Type: Bug Affects Versions: 1.4-m1 Reporter: Jan Haderka Assignee: Jan Haderka Fix For: 1.4.1-rc1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-2903) activation: users having only write permission in a subpart of the hierarchy are not able to activate
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Bärfuss updated MAGNOLIA-2903: -- Fix Version/s: 4.2-beta1 (was: 4.2) (was: 4.1.x) activation: users having only write permission in a subpart of the hierarchy are not able to activate -- Key: MAGNOLIA-2903 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2903 Project: Magnolia Issue Type: Bug Components: activation Affects Versions: 4.1.1 Reporter: Philipp Bärfuss Assignee: Jan Haderka Priority: Critical Fix For: 4.2-beta1 In the following line a temporary node is created in the root of the workspace (the node name is the uuid) -- ReceiveFilter.importOnExisting(ReceiveFilter.java:420) If a user cannot write to the root, but only to a sub hierarchy, he cannot create this temporary 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/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-2901) Moving nodes in adminCentral shows moved node content as parent node content
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Bärfuss updated MAGNOLIA-2901: -- Fix Version/s: 4.2-beta1 (was: 4.2) Moving nodes in adminCentral shows moved node content as parent node content Key: MAGNOLIA-2901 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2901 Project: Magnolia Issue Type: Bug Components: admininterface Affects Versions: 4.1.1 Environment: Browsers I tested on: Firefox Safari Reporter: Christian Ringele Assignee: Jan Haderka Priority: Critical Fix For: 4.1.2, 4.2-beta1 Attachments: MAGNOLIA-2901-after-move.png, MAGNOLIA-2901-before-move.png When moving a node in admin central to a different parent node, the tree only shows the content of the moved node (subnodes) instead of the whole tree. The move occurs properly, and this is only a visual issue. It doesn't seem to be specific to any workspace (reproduced on config, website, dms, ...) nor instance (reproduced on several local ones, demoauthor, ...) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-2903) activation: users having only write permission in a subpart of the hierarchy are not able to activate
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Bärfuss updated MAGNOLIA-2903: -- Fix Version/s: 4.1.2 activation: users having only write permission in a subpart of the hierarchy are not able to activate -- Key: MAGNOLIA-2903 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2903 Project: Magnolia Issue Type: Bug Components: activation Affects Versions: 4.1.1 Reporter: Philipp Bärfuss Assignee: Jan Haderka Priority: Critical Fix For: 4.1.2, 4.2-beta1 In the following line a temporary node is created in the root of the workspace (the node name is the uuid) -- ReceiveFilter.importOnExisting(ReceiveFilter.java:420) If a user cannot write to the root, but only to a sub hierarchy, he cannot create this temporary 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/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] Hudson build is back to normal: magnolia-module-public-user-registration #25
See http://hudson.magnolia-cms.com/job/magnolia-module-public-user-registration/25/changes For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLFORM-37) cleanup bootstrap files: remove wrong namespaces
cleanup bootstrap files: remove wrong namespaces Key: MGNLFORM-37 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-37 Project: Magnolia Form Module Issue Type: Bug Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss Fix For: 1.1-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/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Resolved: (MGNLFORM-37) cleanup bootstrap files: remove wrong namespaces
[ http://jira.magnolia-cms.com/browse/MGNLFORM-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Bärfuss resolved MGNLFORM-37. - Resolution: Fixed cleanup bootstrap files: remove wrong namespaces Key: MGNLFORM-37 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-37 Project: Magnolia Form Module Issue Type: Bug Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss Fix For: 1.1-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/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Resolved: (MAGNOLIA-2903) activation: users having only write permission in a subpart of the hierarchy are not able to activate
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka resolved MAGNOLIA-2903. --- Resolution: Fixed Done as of r29318 on trunk and as of r29342 on 4.1 branch. activation: users having only write permission in a subpart of the hierarchy are not able to activate -- Key: MAGNOLIA-2903 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2903 Project: Magnolia Issue Type: Bug Components: activation Affects Versions: 4.1.1 Reporter: Philipp Bärfuss Assignee: Jan Haderka Priority: Critical Fix For: 4.1.x, 4.2 In the following line a temporary node is created in the root of the workspace (the node name is the uuid) -- ReceiveFilter.importOnExisting(ReceiveFilter.java:420) If a user cannot write to the root, but only to a sub hierarchy, he cannot create this temporary 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/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLPUR-32) The original sample pages using the templates from sample module should be removed
[ http://jira.magnolia-cms.com/browse/MGNLPUR-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Bärfuss updated MGNLPUR-32: --- Fix Version/s: 1.1-alpha1 (was: 1.1) The original sample pages using the templates from sample module should be removed -- Key: MGNLPUR-32 URL: http://jira.magnolia-cms.com/browse/MGNLPUR-32 Project: Magnolia Public User Registration Issue Type: Task Affects Versions: 1.1-m2 Reporter: Zdenek Skodik Assignee: Zdenek Skodik Fix For: 1.1-alpha1 when the PUR sample pages will be stored directly in STK there is no need to hold the initial PUR samples -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
Re: [magnolia-dev] making PUR module more flexible
Just on a side note - instead of using the whole magnolia PUR process to register users, we opted for our own process outside of PUR and then just use some callbacks into PUR to create the account. That made the whole process a bit easier, allowes us to log users in with username/password or email address/password, etc. Works nice and makes it way more customizable. Ruben Bert Leunis wrote: Thanks Grégory! See my answers below. If you can see any advantage in my idea’s I’m happy to help with some code, but if not, no problem either. We would spend too much time on a matter that is not interesting for you. Regards, Bert -Original Message- From: dev-list-ow...@magnolia-cms.com [mailto:dev-list-ow...@magnolia- cms.com] On Behalf Of Grégory Joseph Sent: vrijdag 6 november 2009 16:16 To: Magnolia Dev-List Subject: Re: [magnolia-dev] making PUR module more flexible Hi Bert, Thanks for the taking the time to write this! Now I think I understand your requests! ;) On Nov 6, 2009, at 10:40 AM, Bert Leunis wrote: Hello Grégory (and others), I will give it one more go to see if I can get my points across! Our client will use PUR in a slightly different way than the standard scenario that PUR presumes/implies. When adapting the different scenario I saw two points in the code that can make PUR more flexible quite easily. With more flexible I mean: it does not hinder the standard scenario but it helps you when your scenario is different (like mine). This is the new scenario we use: 1. The webeditor will register the Public User, it wil not be the User itself. (a Public User is created, and a node in the datamodule to store the users data). 2. The User gets an e-mail with its user name and a validation link. 3. The User clicks on the link to validate himself. (The Public User is enabled). 4. The User gets an e-mail with a generated password and a link to the login page. In your scenario, is the self registration *also* needed? No, the users in our case will never register themselves. To keep them in a specific group as Public Users soots us very much, as well as the 'forgot your password' service. I need some changes in PUR to make this possible. Next to the registrationStrategy and the passwordRetrievalStrategy I need a new sendPasswordStrategy. I can store that at config/modules/public-user- registration/config next to the other two, no problem at all. But, if I want to retrieve that strategy in my code, I cannot use the info .magnolia .module.publicuserregistration.PublicUserRegistrationConfig, because it doesn't have a private field and getters/setters to store my new strategy. Now I need to change the code of that class. And here is my proposal: if all strategies were stored in the config and in the PublicUserRegistrationConfig class in a list or Map, then everybody who wants to add strategies of their own can add them, without having to change the code. Config instead of coding. See the picture to get my idea: image002.jpg You would get the strategy you want by its name. They're different interfaces with different use-cases; if multiple implementations of either are needed, we could imagine something like this but with a map for each (i.e they're not two strategies they are one PasswordRetrievalStrategy (impl of the mechanism for users to retrieve their passwords) and one RegistrationStrategy (impl of the mechanism used to register and validate users) I see. To me their all 'actions to perform in regard to the Public User', and as such can be grouped together. Second idea comes from the wish to send a slightly different e-mail than the ones that are used in a standard situation. The class info.magnolia.module.publicuserregistration.strategy.Mail is used to send the e-mail. This class has all the properties you need to send an e-mail (fromName, fromEmail, subject, emailTemplate etc). Unfortunately, in the emailTemplate you can only use one variable, which is “pagePath”. The method validateRegistration(User user) sets only that one variable. Now, if there was an extra method with this signature: public void validateRegistration(User user, MapString, Object templateValues), then every strategy wanting to send e-mails to the Public User would be able to apply all the variables they wanted. A very easy change of the code, which makes it much more usable. Where would these values come from, who (what code) would set them ? In the PUR module there's the class info.magnolia.module.publicuserregistration.frontend.EnableByUuid. I created my own version of that, because except enableing the Public User, we have to send him a password too. Here I use my sendPasswordStrategy: Cheers, -g Happy to apply any patch, if you can see the benefit. Lots of regards,
[magnolia-dev] Hudson build is back to stable: magnolia_main-trunk-forked-tests » magnolia-mo dule-templating #387
See http://hudson.magnolia-cms.com/job/magnolia_main-trunk-forked-tests/info.magnolia$magnolia-module-templating/387/changes For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] Hudson build is back to stable: magnolia_main-trunk-forked-tests #387
See http://hudson.magnolia-cms.com/job/magnolia_main-trunk-forked-tests/387/changes For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Commented: (MGNLRES-21) Nice editor
[ http://jira.magnolia-cms.com/browse/MGNLRES-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=24798#action_24798 ] Hudson CI server commented on MGNLRES-21: - Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! [magnolia_main-trunk #1095|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1095/] : added CodePress js library to turn a textarea into a basic code editor with syntax highlighting and line numbers. Used a custom js function (added to the CodePress namespace) to handle the submit of a Magnolia dialog, which otherwise caused troubles when saving or updating the text. Tested on FF 3.x and IE7, it works decently. Nice editor --- Key: MGNLRES-21 URL: http://jira.magnolia-cms.com/browse/MGNLRES-21 Project: Magnolia Resources Module Issue Type: Improvement Reporter: Federico Grilli Assignee: Federico Grilli Fix For: 1.2 Improve current editor by adding syntax highlighting, line numbers, etc. Use the codepress component. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Commented: (MGNLWEBDAV-11) Verify behaviour of move and rename operations
[ http://jira.magnolia-cms.com/browse/MGNLWEBDAV-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=24799#action_24799 ] Grégory Joseph commented on MGNLWEBDAV-11: -- Since the above log logs from as the request URI and to as the repository path as massaged by the ResourceLocator, it is not surprising that the extension is gone, since that's essentially what our ResourceLocator does. Verify behaviour of move and rename operations -- Key: MGNLWEBDAV-11 URL: http://jira.magnolia-cms.com/browse/MGNLWEBDAV-11 Project: Magnolia WebDAV Module Issue Type: Task Reporter: Grégory Joseph Assignee: Jan Haderka Fix For: 1.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Assigned: (MGNLWEBDAV-18) Unicode support
[ http://jira.magnolia-cms.com/browse/MGNLWEBDAV-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grégory Joseph reassigned MGNLWEBDAV-18: Assignee: Grégory Joseph (was: Jan Haderka) Unicode support --- Key: MGNLWEBDAV-18 URL: http://jira.magnolia-cms.com/browse/MGNLWEBDAV-18 Project: Magnolia WebDAV Module Issue Type: Improvement Affects Versions: 1.0 Reporter: Grégory Joseph Assignee: Grégory Joseph Fix For: 1.1 We currently can't support non-ascii node names. See http://confluence.magnolia-cms.com/display/DEV/Unicode+support+status -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLWEBDAV-18) Unicode support
Unicode support --- Key: MGNLWEBDAV-18 URL: http://jira.magnolia-cms.com/browse/MGNLWEBDAV-18 Project: Magnolia WebDAV Module Issue Type: Improvement Affects Versions: 1.0 Reporter: Grégory Joseph Assignee: Jan Haderka Fix For: 1.1 We currently can't support non-ascii node names. See http://confluence.magnolia-cms.com/display/DEV/Unicode+support+status -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Commented: (MGNLWEBDAV-15) Node names aren't validated before creation
[
http://jira.magnolia-cms.com/browse/MGNLWEBDAV-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=24800#action_24800
]
Hudson CI server commented on MGNLWEBDAV-15:
Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif!
[magnolia-module-webdav
#603|http://hudson.magnolia-cms.com/job/magnolia-module-webdav/603/]
now strictly limit the accepted range of chars in paths for webdav...
Node names aren't validated before creation
---
Key: MGNLWEBDAV-15
URL: http://jira.magnolia-cms.com/browse/MGNLWEBDAV-15
Project: Magnolia WebDAV Module
Issue Type: Bug
Affects Versions: 1.0-m2
Reporter: Grégory Joseph
Assignee: Grégory Joseph
Fix For: 1.0
When trying to create a folder with non-ascii characters (from a fs-mounted
WebDAV), {{pascaläöü}} in this case:
{code}
2009-10-27 19:16:59,826 INFO info.magnolia.cms.beans.config.MIMEMapping
: Cannot find MIME type for extension _pascale%CC%80u%CC%88
2009-10-27 19:17:00.416::WARN:
/magnolia-snapshot-demo/.webdav/resources/folders/
java.lang.RuntimeException: info.magnolia.cms.security.AccessDeniedException:
User not allowed to Read path [/folders/pascale?u?]
at
info.magnolia.module.webdav.LocatorFactory.getResourcePath(LocatorFactory.java:76)
at
org.apache.jackrabbit.webdav.AbstractLocatorFactory.createResourceLocator(AbstractLocatorFactory.java:170)
at
org.apache.jackrabbit.webdav.simple.DavResourceImpl.getMembers(DavResourceImpl.java:564)
at
org.apache.jackrabbit.webdav.MultiStatus.addResourceProperties(MultiStatus.java:64)
at
org.apache.jackrabbit.webdav.server.AbstractWebdavServlet.doPropFind(AbstractWebdavServlet.java:447)
at
org.apache.jackrabbit.webdav.server.AbstractWebdavServlet.execute(AbstractWebdavServlet.java:235)
{code}
The exception reminds of MAGNOLIA-2098. (this happened while logged in as
superuser)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Commented: (MGNLWEBDAV-15) Node names aren't validated before creation
[
http://jira.magnolia-cms.com/browse/MGNLWEBDAV-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=24801#action_24801
]
Grégory Joseph commented on MGNLWEBDAV-15:
--
Since we can't rename nodes on the fly like we do in the AdminCentral tree
(at least not without digging much further in the Jackrabbit WebDAV code and
the protocol), the only option is currently to prohibit such names.
Node names aren't validated before creation
---
Key: MGNLWEBDAV-15
URL: http://jira.magnolia-cms.com/browse/MGNLWEBDAV-15
Project: Magnolia WebDAV Module
Issue Type: Bug
Affects Versions: 1.0-m2
Reporter: Grégory Joseph
Assignee: Grégory Joseph
Fix For: 1.0
When trying to create a folder with non-ascii characters (from a fs-mounted
WebDAV), {{pascaläöü}} in this case:
{code}
2009-10-27 19:16:59,826 INFO info.magnolia.cms.beans.config.MIMEMapping
: Cannot find MIME type for extension _pascale%CC%80u%CC%88
2009-10-27 19:17:00.416::WARN:
/magnolia-snapshot-demo/.webdav/resources/folders/
java.lang.RuntimeException: info.magnolia.cms.security.AccessDeniedException:
User not allowed to Read path [/folders/pascale?u?]
at
info.magnolia.module.webdav.LocatorFactory.getResourcePath(LocatorFactory.java:76)
at
org.apache.jackrabbit.webdav.AbstractLocatorFactory.createResourceLocator(AbstractLocatorFactory.java:170)
at
org.apache.jackrabbit.webdav.simple.DavResourceImpl.getMembers(DavResourceImpl.java:564)
at
org.apache.jackrabbit.webdav.MultiStatus.addResourceProperties(MultiStatus.java:64)
at
org.apache.jackrabbit.webdav.server.AbstractWebdavServlet.doPropFind(AbstractWebdavServlet.java:447)
at
org.apache.jackrabbit.webdav.server.AbstractWebdavServlet.execute(AbstractWebdavServlet.java:235)
{code}
The exception reminds of MAGNOLIA-2098. (this happened while logged in as
superuser)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-2929) Enhance unicode support
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grégory Joseph updated MAGNOLIA-2929:
-
Fix Version/s: 4.3
(was: 4.2)
The above has been done for 4.2; for actual support in AdminCentral, there's
more work involved, which might not entirely possible before we have our new ui
framework in place:
http://confluence.magnolia-cms.com/display/DEV/Unicode+support+status
Enhance unicode support
---
Key: MAGNOLIA-2929
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2929
Project: Magnolia
Issue Type: Improvement
Components: core
Reporter: Grégory Joseph
Assignee: Grégory Joseph
Fix For: 4.3
In light of MGNLWEBDAV-15, we need Magnolia to be a little more lax with
unicode names.
There are two sides to this issue:
* the current {{SimpleUrlPattern}} implementation chokes on paths with
unicode characters in the decomposed form.
* Jackrabbit does no unicode normalization for node names, thus a node
created with a name in the composed form can not be retrieved by using the
decomposed form of the exact same name.
Since clients tend to use one or the other form arbitrarily (Firefox 3.0 on
MacOSX sends GET parameters in the NFD form, Safari in NFC; while the Linux
OS tends to favor NFC and OSX tends to favor NFD, for instance).
Node name normalization unfortunately requires using either Java 6
([{{java.text.Normalizer}}|http://java.sun.com/javase/6/docs/api/java/text/Normalizer.html]),
the [ICU4J library|http://www.icu-project.org/]; there might be other
implementations out there, so we should leave the option open to swap for
another one.
See http://en.wikipedia.org/wiki/Unicode_equivalence#Normal_forms for
background information.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Resolved: (MGNLWEBDAV-15) Node names aren't validated before creation
[
http://jira.magnolia-cms.com/browse/MGNLWEBDAV-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grégory Joseph resolved MGNLWEBDAV-15.
--
Resolution: Fixed
Node names aren't validated before creation
---
Key: MGNLWEBDAV-15
URL: http://jira.magnolia-cms.com/browse/MGNLWEBDAV-15
Project: Magnolia WebDAV Module
Issue Type: Bug
Affects Versions: 1.0-m2
Reporter: Grégory Joseph
Assignee: Grégory Joseph
Fix For: 1.0
When trying to create a folder with non-ascii characters (from a fs-mounted
WebDAV), {{pascaläöü}} in this case:
{code}
2009-10-27 19:16:59,826 INFO info.magnolia.cms.beans.config.MIMEMapping
: Cannot find MIME type for extension _pascale%CC%80u%CC%88
2009-10-27 19:17:00.416::WARN:
/magnolia-snapshot-demo/.webdav/resources/folders/
java.lang.RuntimeException: info.magnolia.cms.security.AccessDeniedException:
User not allowed to Read path [/folders/pascale?u?]
at
info.magnolia.module.webdav.LocatorFactory.getResourcePath(LocatorFactory.java:76)
at
org.apache.jackrabbit.webdav.AbstractLocatorFactory.createResourceLocator(AbstractLocatorFactory.java:170)
at
org.apache.jackrabbit.webdav.simple.DavResourceImpl.getMembers(DavResourceImpl.java:564)
at
org.apache.jackrabbit.webdav.MultiStatus.addResourceProperties(MultiStatus.java:64)
at
org.apache.jackrabbit.webdav.server.AbstractWebdavServlet.doPropFind(AbstractWebdavServlet.java:447)
at
org.apache.jackrabbit.webdav.server.AbstractWebdavServlet.execute(AbstractWebdavServlet.java:235)
{code}
The exception reminds of MAGNOLIA-2098. (this happened while logged in as
superuser)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2805) Can't deploy webapp from a directory that has a + symbol in its path
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=24803#action_24803
]
Hudson CI server commented on MAGNOLIA-2805:
Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif!
[magnolia-bundle_trunk
#581|http://hudson.magnolia-cms.com/job/magnolia-bundle_trunk/581/]
: setting the tmp direcotry explicitely in the cargo configuration solves
the problem for the bundle
Can't deploy webapp from a directory that has a + symbol in its path
--
Key: MAGNOLIA-2805
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2805
Project: Magnolia
Issue Type: Bug
Components: core
Affects Versions: 3.6.6, 4.0.2, 4.1.1
Environment: OSX 10.5.57 - tomcat, jetty, ...
Reporter: Grégory Joseph
Assignee: Philipp Bärfuss
Fix For: 4.1.x
While this is probably not a very common use-case, we ran into this problem
with integration tests on osx 10.5.7
Indeed, tmp files are now going to {{/var/folders/some-unique-path}} - and
(sometimes?) this path contains {{+}}'s:
{noformat}
2009-06-30 16:23:23.200::INFO: Extract
jar:file:/Users/gjoseph/Dev/magnolia/svn-branches/magnolia-bundle-3.6/magnolia-bundled-webapp/target/magnolia-bundled-webapp-3.6.6-SNAPSHOT.war!/
to
/var/folders/Ca/Cay4JfEtFGyfVhgQhPjJ4U+++TI/-Tmp-/Jetty_0_0_0_0_9345_magnolia-bundled-webapp-3.6.6-SNAPSHOT.war__magnoliaAuthor__ovqsl9/webapp
D
DEBUG info.magnolia.cms.servlets.MgnlServletContextListener
MgnlServletContextListener.java(contextInitialized:164) 30.06.2009 16:23:26
rootPath is
/private/var/folders/Ca/Cay4JfEtFGyfVhgQhPjJ4U+++TI/-Tmp-/Jetty_0_0_0_0_9345_magnolia-bundled-webapp-3.6.6-SNAPSHOT.war__magnoliaAuthor__ovqsl9/webapp,
webapp is webapp
{noformat}
({{rootPath}} is set correctly here)
Somewhere along the road, this path gets url-decoded, resulting in such
warnings:
{noformat}
WARN info.magnolia.cms.util.ClasspathResourcesUtil
ClasspathResourcesUtil.java(collectFiles:160) 30.06.2009 16:23:26 missing
file: /private/var/folders/Ca/Cay4JfEtFGyfVhgQhPjJ4U
TI/-Tmp-/Jetty_0_0_0_0_9345_magnolia-bundled-webapp-3.6.6-SNAPSHOT.war__magnoliaAuthor__ovqsl9/webapp/WEB-INF/classes
{noformat}
Still, the repository *seems* to be correctly loaded:
{noformat}
INFO info.magnolia.jackrabbit.ProviderImpl ProviderImpl.java(init:176)
30.06.2009 16:23:26 Loading repository at
/private/var/folders/Ca/Cay4JfEtFGyfVhgQhPjJ4U+++TI/-Tmp-/Jetty_0_0_0_0_9345_magnolia-bundled-webapp-3.6.6-SNAPSHOT.war__magnoliaAuthor__ovqsl9/webapp/repositories/magnolia
(config file:
/private/var/folders/Ca/Cay4JfEtFGyfVhgQhPjJ4U+++TI/-Tmp-/Jetty_0_0_0_0_9345_magnolia-bundled-webapp-3.6.6-SNAPSHOT.war__magnoliaAuthor__ovqsl9/webapp/WEB-INF/config/repo-conf/jackrabbit-bundle-derby-search.xml)
{noformat} but the startup ends up failing with {noformat}
2009-06-30 16:23:33.035::WARN: Failed startup of context
org.mortbay.jetty.webapp.webappcont...@d816d6{/magnoliaAuthor,jar:file:/Users/gjoseph/Dev/magnolia/svn-branches/magnolia-bundle-3.6/magnolia-bundled-webapp/target/magnolia-bundled-webapp-3.6.6-SNAPSHOT.war!/}
java.lang.RuntimeException: javax.jcr.PathNotFoundException: modules
at
info.magnolia.module.ModuleManagerImpl.startModules(ModuleManagerImpl.java:346)
at
info.magnolia.module.ui.ModuleManagerWebUI.onStartup(ModuleManagerWebUI.java:80)
at
info.magnolia.cms.beans.config.ConfigLoader.load(ConfigLoader.java:138)
at
info.magnolia.cms.beans.config.ConfigLoader.init(ConfigLoader.java:107)
at
info.magnolia.cms.servlets.MgnlServletContextListener$1.exec(MgnlServletContextListener.java:178)
{noformat}
Verified this isn't test or jetty specific by simply renaming my
{{apache-tomcat-5.5.27}} folder to {{apache+tomcat-5.5.27}} and saw exactly
the same symptoms.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] Fwd: Magnolia 4.2 beta 1 released
Hi, We have released 4.2 beta1 (not yet applied any QA on that). The releases are currently only available in our maven repositories. Community Edition: http://repo.magnolia-cms.com/m2/info/magnolia/magnolia-tomcat-bundle/4.2-beta1 STK 1.2: http://repo.magnolia-cms.com/m2/info/magnolia/magnolia-standard-templating-kit-bundle/1.2-beta1 Enterprise Edition: http://files.magnolia-cms.com/4.2-beta1 Some of the modules have not be re-released and still have a milestone version because we have avoided releases where no changes have been made. The modules released as alpha or beta are not yet ready for being a release candidate but close to. These are: - form - public user registration - STK - WebDAV We strive to release a first release candidate Wednesday. Thanks! - Philipp Bärfuss For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLPUR-33) Can't create any user - system claims The username already exists
Can't create any user - system claims The username already exists --- Key: MGNLPUR-33 URL: http://jira.magnolia-cms.com/browse/MGNLPUR-33 Project: Magnolia Public User Registration Issue Type: Bug Environment: osx, safari 4.0.3 Reporter: Boris Kraft Assignee: Grégory Joseph Priority: Blocker Just installed the 4.2 beta 1 with WebDAV support, now trying to create a public user from the http://localhost:8080/magnoliaPublic/demo-features/modules/public-user-registration/PURRegistration.html No matter what I try, it always complains that Username:: The username already exists. The logs do not say anything, and I confirmed that no user exists that possibly matches the usernames or emails I tried (not sure if the system checks if emails already exist) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLPUR-35) PUR STK examples claim superuser is logged in (no, he is not)
PUR STK examples claim superuser is logged in (no, he is not) - Key: MGNLPUR-35 URL: http://jira.magnolia-cms.com/browse/MGNLPUR-35 Project: Magnolia Public User Registration Issue Type: Bug Reporter: Boris Kraft Assignee: Grégory Joseph http://localhost:8080/magnoliaPublic/demo-features/modules/public-user-registration/PURPassword.html claims that You are logged in, superuser. even though nobody is logged in. Same is true for * http://localhost:8080/magnoliaPublic/demo-features/modules/public-user-registration/PURLogout.html * http://localhost:8080/magnoliaPublic/demo-features/modules/public-user-registration/PURUpdate.html It should not claim that superuser is logged in if that is not in fact the case. As a side note, if superuser is in fact logged in, it should say You are logged in as superuser (not You are logged in, superuser) and it should probably say so above the form, not below. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
