[magnolia-dev] [JIRA] (DOCU-538) Links in examples don't work
Jozef Chocholacek created DOCU-538 Links in examples don't work Issue Type: Bug Assignee: Antti Hietala Created: 16/Oct/14 8:36 AM Description: Example links in http://documentation.magnolia-cms.com/display/DOCS/Module+management#Modulemanagement-Servletinitializationparameters don't work - because they point to SVN, and the sources are now in Git. Project: Documentation Priority: Neutral Reporter: Jozef Chocholacek Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] We referring to pretty much guys
We referring to pretty much guys were you ever miss Olympia didn’t at 4:45 morning don't car around all for 531 his way I don't think [url=http://www.x4facts.com/my-review-about-xtreme-antler/]Xtreme Antler[/url] I've ever known as they did you know settling for a good 30 minutes going to treadmill are by for the 70 that mean average into half hours all fiftyeight years they have is wrong with my fairytale guy I get power back to work out four times a week compression twice I don't think twice I had only increases if I actually have a nagging injury or something like that shoulder back here whatever it may be I got it motorcycle cops called for someone within also tagged like magazine over different you know I plans for the year I actually have a hole in my own home only website so got we always on the phone talking before you know time distributors you internationally grand over there as well and is Mike Davis in so Columbia probably not so it now so it behavior between that time I love you live with me when you swing you know you know it doesn't like five dollars why you should take a nap in sometime car or train console for me is his I'm pretty fortunate to have that I don't like to believe you know what my schedule the rally 34 clickers taking all good 45 to our room and out you know training and didn't like I said my so you know 11:30 a.m. to midnight when you have a relationship she wants to know I'm sorry…… For more information, visit this site >>> http://www.x4facts.com/my-review-about-xtreme-antler/ -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=e56f39a3-1f14-4eb1-ab78-61989e468ad0 For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (BUILD-153) Update dependency plugin to 2.9.2
Grégory Joseph created BUILD-153 Update dependency plugin to 2.9.2 Issue Type: New Feature Assignee: Grégory Joseph Created: 15/Oct/14 6:57 PM Fix Versions: POMs 30 Project: Build Priority: Neutral Reporter: Grégory Joseph Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLGROOVY-15) Support multi-line scripts in console
Federico Grilli updated MGNLGROOVY-15 Support multi-line scripts in console Change By: Federico Grilli (15/Oct/14 6:56 PM) Fix Version/s: 2.3.1 Fix Version/s: Backlog This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (BUILD-152) Add profile to purge local repo of a project's dependencies
Grégory Joseph created BUILD-152 Add profile to purge local repo of a project's dependencies Issue Type: New Feature Assignee: Grégory Joseph Created: 15/Oct/14 6:54 PM Description: Will add profile such that doing mvn -P purge-magnolia-from-local-repo clean removes the current project's Magnolia dependencies from the local repo. http://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html If one wants to purge all versions of artifacts the current project depends on: mvn -DresolutionFuzziness=artifactId -P purge-magnolia-from-local-repo clean If one wants to purge all artifacts and versions of any groupIDs that the current project depends on: mvn -DresolutionFuzziness=groupId -P purge-magnolia-from-local-repo clean The above makes no sense, since the profile configures includes to be info.magnolia* star. So one also needs to use the -Dinclude flag. e.g.: mvn -Dinclude=commons-lang -DresolutionFuzziness=groupId -P purge-magnolia-from-local-repo clean One can also use the -DmanualInclude flag, which will then remove artifacts even if the current project doesn't depend on them (and in this case I think resolutionFuzziness makes no sense and is ignored) Fix Versions: POMs 30 Project: Build Priority: Neutral Reporter: Grégory Joseph Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (BUILD-151) Add staging configuration
Grégory Joseph created BUILD-151 Add staging configuration Issue Type: New Feature Assignee: Grégory Joseph Created: 15/Oct/14 6:39 PM Description: We're enabling release staging with SYS-444. Parent poms need some additions for this to work smoothly. We'll probably add a profile to enable the feature "on demand" when releasing. In this first version, it'll be working for community and enterprise poms, but we might open it up for forge, projects and internal later. Fix Versions: POMs 30 Project: Build Priority: Neutral Reporter: Grégory Joseph Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (TASKMGMT-13) Update artifactId with "magnolia"-prefix
Grégory Joseph updated TASKMGMT-13 Update artifactId with "magnolia"-prefix Change By: Grégory Joseph (15/Oct/14 6:12 PM) Summary: Update articactId artifactId with "magnolia"-prefix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3191) EditElementAction should not be available when the template is set to not be editable
Christopher Zimmermann reopened MGNLUI-3191 EditElementAction should not be available when the template is set to not be editable Change By: Christopher Zimmermann (15/Oct/14 2:58 PM) Resolution: Fixed Status: In QA Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3191) EditElementAction should not be available when the template is set to not be editable
Christopher Zimmermann updated MGNLUI-3191 EditElementAction should not be available when the template is set to not be editable Change By: Christopher Zimmermann (15/Oct/14 2:53 PM) Description: Setting enabled editable =false at template definition (or cms.) hides the editing option at the corresponding green bar of pages' detail subapp, but an editor can edit it via the action bar still available though. The other actions grouped together with, e.g. the one for moving, should apparently be disabled as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3208) Actions in dialogs are only clickable once – afterwards they are disabled
Andreas Weder updated MGNLUI-3208 Actions in dialogs are only clickable once – afterwards they are disabled Change By: Andreas Weder (15/Oct/14 1:51 PM) Labels: next quickwin ux This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3208) Actions in dialogs are only clickable once – afterwards they are disabled
Philip Mundt updated MGNLUI-3208 Actions in dialogs are only clickable once – afterwards they are disabled Change By: Philip Mundt (15/Oct/14 1:51 PM) Description: To reproduce:h5. In PagesApp* Goto article and edit page header* "Select another..." image* Select a folder in chooser dialog* Hit "Upload & edit"* Cancel* *Action should be disabled* (see: [^asset_chooser-pages_app-upload+edit-disabled.png])h5. In AssetsAppRequires: MGNLDAM-515* Create version of asset* "Show versions" and select one* In view hit "Download" and abort download* *Action should be disabled* (see: [^asset_app-view_version-download-disabled.png]) This behavior in the AssetApp can also be reproduced by just editing a non-versioned asset and trying to download it twice (once MGNLDAM-515) is in. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3208) Actions in dialogs are only clickable once – afterwards they are disabled
Andreas Weder updated MGNLUI-3208 Actions in dialogs are only clickable once – afterwards they are disabled Change By: Andreas Weder (15/Oct/14 1:51 PM) Fix Version/s: 5.3.x This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLFORUM-281) Forum migration is failed when migrate 4.5 to 5.2.x
Peili Liang created MGNLFORUM-281 Forum migration is failed when migrate 4.5 to 5.2.x Issue Type: Bug Assignee: Unassigned Components: VersionHandler Created: 15/Oct/14 1:46 PM Description: When migrate 4.5 to 5.2.x, The forum module exists a line difference. Fix Versions: 3.3.5 Project: Magnolia Forum Module Priority: Neutral Reporter: Peili Liang Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLFORUM-281) Forum migration is failed when migrate 4.5 to 5.2.x
Peili Liang updated MGNLFORUM-281 Forum migration is failed when migrate 4.5 to 5.2.x Change By: Peili Liang (15/Oct/14 1:46 PM) Assignee: Peili Liang This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3208) Actions in dialogs are only clickable once – afterwards they are disabled
Philip Mundt created MGNLUI-3208 Actions in dialogs are only clickable once – afterwards they are disabled Issue Type: Bug Assignee: Unassigned Attachments: asset_app-view_version-download-disabled.png, asset_chooser-pages_app-upload+edit-disabled.png Created: 15/Oct/14 1:33 PM Description: To reproduce: In PagesApp Goto article and edit page header "Select another..." image Select a folder in chooser dialog Hit "Upload & edit" Cancel Action should be disabled In AssetsApp (requires: MGNLDAM-515) Create version of asset "Show versions" and select one In view hit "Download" and abort download Action should be disabled Project: Magnolia UI Priority: Neutral Reporter: Philip Mundt Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3208) Actions in dialogs are only clickable once – afterwards they are disabled
Philip Mundt updated MGNLUI-3208 Actions in dialogs are only clickable once – afterwards they are disabled Change By: Philip Mundt (15/Oct/14 1:36 PM) Description: To reproduce:h5. In PagesApp* Goto article and edit page header* "Select another..." image* Select a folder in chooser dialog* Hit "Upload & edit"* Cancel* *Action should be disabled* (see: [^asset_chooser-pages_app-upload %2Bedit +edit -disabled.png])h5. In AssetsAppRequires: MGNLDAM-515* Create version of asset* "Show versions" and select one* In view hit "Download" and abort download* *Action should be disabled* (see: [^asset_app-view_version-download-disabled.png]) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3208) Actions in dialogs are only clickable once – afterwards they are disabled
Philip Mundt updated MGNLUI-3208 Actions in dialogs are only clickable once – afterwards they are disabled Change By: Philip Mundt (15/Oct/14 1:34 PM) Description: To reproduce:h5. In PagesApp* Goto article and edit page header* "Select another..." image* Select a folder in chooser dialog* Hit "Upload & edit"* Cancel* *Action should be disabled*h5. In AssetsApp (requires Requires : MGNLDAM-515 ) * Create version of asset* "Show versions" and select one* In view hit "Download" and abort download* *Action should be disabled* This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3208) Actions in dialogs are only clickable once – afterwards they are disabled
Philip Mundt updated MGNLUI-3208 Actions in dialogs are only clickable once – afterwards they are disabled Change By: Philip Mundt (15/Oct/14 1:35 PM) Attachment: asset_app-view_version-download-disabled.png Attachment: asset_chooser-pages_app-upload+edit-disabled.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3208) Actions in dialogs are only clickable once – afterwards they are disabled
Philip Mundt updated MGNLUI-3208 Actions in dialogs are only clickable once – afterwards they are disabled Change By: Philip Mundt (15/Oct/14 1:36 PM) Description: To reproduce:h5. In PagesApp* Goto article and edit page header* "Select another..." image* Select a folder in chooser dialog* Hit "Upload & edit"* Cancel* *Action should be disabled* (see: [^asset_chooser-pages_app-upload%2Bedit-disabled.png]) h5. In AssetsAppRequires: MGNLDAM-515* Create version of asset* "Show versions" and select one* In view hit "Download" and abort download* *Action should be disabled* (see: [^asset_app-view_version-download-disabled.png]) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] Re: Redirect after success action
Hi
Take a look at info.magnolia.pages.app.action.EditPageAction#EditPageAction:
This action opens a new tab in the pages app for editing using the
LocationController.
DetailLocation loc = new DetailLocation("pages", "detail",
DetailView.ViewType.EDIT, pageNode.getPath(), "");
locationController.goTo(loc);
You might be able to reuse that action, by defining it as a callback to the
preceding action, or just put that piece of code where you already figured out.
Espen
--
Context is everything:
http://forum.magnolia-cms.com/forum/thread.html?threadId=63e40ab3-a851-442b-b276-04f342e78109
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3207) Edit action for footer area is disabled on actionbar in page app
Diana Racho created MGNLUI-3207 Edit action for footer area is disabled on actionbar in page app Issue Type: Bug Affects Versions: 5.3.4 Assignee: Unassigned Attachments: edit_action_disabled.jpg Components: pages app Created: 15/Oct/14 12:30 PM Environment: http://demoauthor.magnolia-cms.com Project: Magnolia UI Priority: Neutral Reporter: Diana Racho Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLMAIL-64) Removed unused dependencies
Roman Kovařík updated MGNLMAIL-64 Removed unused dependencies Change By: Roman Kovařík (15/Oct/14 12:07 PM) Summary: Check if freemarker dependency is still needed Removed unused dependencies This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLMAIL-64) Check if freemarker dependency is still needed
Roman Kovařík created MGNLMAIL-64 Check if freemarker dependency is still needed Issue Type: Bug Affects Versions: 5.2.1 Assignee: Roman Kovařík Created: 15/Oct/14 11:50 AM Fix Versions: 5.2.x Project: Magnolia Mail Module Priority: Neutral Reporter: Roman Kovařík This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3200) Peter cannot publish anymore in CE and EE
Roman Kovařík updated MGNLUI-3200 Peter cannot publish anymore in CE and EE Change By: Roman Kovařík (15/Oct/14 11:52 AM) Fix Version/s: 5.2.x Fix Version/s: 5.2.10 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3200) Peter cannot publish anymore in CE and EE
Espen Jervidalo updated MGNLUI-3200 Peter cannot publish anymore in CE and EE Change By: Espen Jervidalo (15/Oct/14 11:35 AM) Description: Peter cannot publish pages in Community Edition. MGNLUI-2939 added a new availability constraint writePermissionRequired=true to activate and activateRecursive actions. This has the side effect that Peter, whose demo-project-publisher role doesn't permit him to write to the website workspace, cannot publish pages either.This issue is specific to CE since it doesn't have workflow.(In EE, Peter can approve a workitem. The new action availability constraint was not added to /modules/workflow/messageViews/publish/actions/approve.)Update:This was introduced with: MAGNOLIA-5795In 4.5 we had workflow as part of CE and peter was never able to 'activate' anything on a workspace. He was only able to publish from workItems from the inbox. As we changed this in 5.0 by removing workflow from CE, peter should now be able to publish in CE (which conflicts with his readOnly permission on the workspace).One possible solution is to change the writePermissionRequired to 'false' in CE and switching it to 'true' when installing workflow for that app. which IMO is only an ugly workaround to a conceptual problem we're facing.OTOH, why should peter be able to push something to a public instance (which is a much more harmful action) and not be able to publish (activate) something which is more likely do much less harm, than pushing it to public. My vote goes for reverting or at least change the default of the writePermssionRequired to 'false'. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3200) Peter cannot publish anymore in CE and EE
Espen Jervidalo updated MGNLUI-3200 Peter cannot publish anymore in CE and EE Change By: Espen Jervidalo (15/Oct/14 11:29 AM) Description: Peter cannot publish pages in Community Edition. MGNLUI-2939 added a new availability constraint writePermissionRequired=true to activate and activateRecursive actions. This has the side effect that Peter, whose demo-project-publisher role doesn't permit him to write to the website workspace, cannot publish pages either.This issue is specific to CE since it doesn't have workflow.(In EE, Peter can approve a workitem. The new action availability constraint was not added to /modules/workflow/messageViews/publish/actions/approve.)Update:This was introduced with: MAGNOLIA-5795In 4.5 we had workflow as part of CE and peter was never able to 'activate' anything on a workspace. He was only able to publish from workItems from the inbox. As we changed this in 5.0 by removing workflow from CE, peter should now be able to publish in CE (which conflicts with his readOnly permission on the workspace).One possible solution is to change the writePermissionRequired to ' true false ' in CE and switching it to ' false true ' when installing workflow for that app. which IMO is only an ugly workaround to a conceptual problem we're facing.OTOH, why should peter be able to push something to a public instance (which is a much more harmful action) and not be able to publish (activate) something which is more likely do much less harm, than pushing it to public. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3200) Peter cannot publish anymore in CE and EE
Espen Jervidalo updated MGNLUI-3200 Peter cannot publish anymore in CE and EE Change By: Espen Jervidalo (15/Oct/14 11:27 AM) Affects Version/s: 5.3.1 Affects Version/s: 5.2.6 Affects Version/s: 5.3.4 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3200) Peter cannot publish anymore in CE and EE
Espen Jervidalo updated MGNLUI-3200 Peter cannot publish anymore in CE and EE Change By: Espen Jervidalo (15/Oct/14 11:28 AM) Description: Peter cannot publish pages in Community Edition. MGNLUI-2939 added a new availability constraint writePermissionRequired=true to activate and activateRecursive actions. This has the side effect that Peter, whose demo-project-publisher role doesn't permit him to write to the website workspace, cannot publish pages either.This issue is specific to CE since it doesn't have workflow.(In EE, Peter can approve a workitem. The new action availability constraint was not added to /modules/workflow/messageViews/publish/actions/approve.)Update:This was introduced with: MAGNOLIA-5795In 4.5 we had workflow as part of CE and peter was never able to 'activate' anything on a workspace. He was only able to publish from workItems from the inbox. As we changed this in 5.0 by removing workflow from CE, peter should now be able to publish in CE (which conflicts with his readOnly permission on the workspace).One possible solution is to change the writePermissionRequired to 'true' in CE and switching it to 'false' when installing workflow for that app. which IMO is only an ugly workaround to a conceptual problem we're facing.OTOH, why should peter be able to push something to a public instance (which is a much more disruptive harmful action) and not be able to publish (activate) something which is more likely do much less harm, than pushing it to public. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3200) Peter cannot publish anymore in CE and EE
Espen Jervidalo updated MGNLUI-3200 Peter cannot publish anymore in CE and EE Change By: Espen Jervidalo (15/Oct/14 11:26 AM) Description: Peter cannot publish pages in Community Edition. MGNLUI-2939 added a new availability constraint writePermissionRequired=true to activate and activateRecursive actions. This has the side effect that Peter, whose demo-project-publisher role doesn't permit him to write to the website workspace, cannot publish pages either.This issue is specific to CE since it doesn't have workflow.(In EE, Peter can approve a workitem. The new action availability constraint was not added to /modules/workflow/messageViews/publish/actions/approve.) Update:This was introduced with: MAGNOLIA-5795In 4.5 we had workflow as part of CE and peter was never able to 'activate' anything on a workspace. He was only able to publish from workItems from the inbox. As we changed this in 5.0 by removing workflow from CE, peter should now be able to publish in CE (which conflicts with his readOnly permission on the workspace).One possible solution is to change the writePermissionRequired to 'true' in CE and switching it to 'false' when installing workflow for that app. which IMO is only an ugly workaround to a conceptual problem we're facing.OTOH, why should peter be able to push something to a public instance (which is a much more disruptive action) and not be able to publish (activate) something which is more likely do much less harm, than pushing it to public. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLGROOVY-68) Changes to a Groovy class in config aren't picked up
Federico Grilli reopened MGNLGROOVY-68 Changes to a Groovy class in config aren't picked up Discussed about it further with Phippu and his take is that from a user perspective it is best to go ahead with my proposed solution. Can be further discussed in arch meeting if necessary. Change By: Federico Grilli (15/Oct/14 10:31 AM) Resolution: Not an issue Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLGROOVY-68) Changes to a Groovy class in config aren't picked up
Federico Grilli updated MGNLGROOVY-68 Changes to a Groovy class in config aren't picked up Change By: Federico Grilli (15/Oct/14 10:31 AM) Fix Version/s: 2.3.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLCKEDIT-14) Make link browser open selected path in tree
Zdenek Skodik updated MGNLCKEDIT-14 Make link browser open selected path in tree Change By: Zdenek Skodik (15/Oct/14 10:25 AM) Labels: support This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLCKEDIT-15) CKRepositoryBrowserPageSelect: make popup larger
Zdenek Skodik updated MGNLCKEDIT-15 CKRepositoryBrowserPageSelect: make popup larger Change By: Zdenek Skodik (15/Oct/14 10:26 AM) Labels: support This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3200) Peter cannot publish anymore in CE and EE
Espen Jervidalo updated MGNLUI-3200 Peter cannot publish anymore in CE and EE Change By: Espen Jervidalo (15/Oct/14 10:24 AM) Fix Version/s: 5.2.10 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (MGNLUI-3200) Peter cannot publish anymore in CE and EE
Espen Jervidalo updated MGNLUI-3200 Peter cannot publish anymore in CE and EE Change By: Espen Jervidalo (15/Oct/14 10:19 AM) Summary: Peter cannot publish pages anymore in CE and EE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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:
