[magnolia-dev] [JIRA] (MGNLDEMO-68) Clean up old STK permissions from apps
Title: Message Title Federico Grilli created an issue Magnolia Demo Projects / MGNLDEMO-68 Clean up old STK permissions from apps Issue Type: Story Affects Versions: 0.5 Assignee: Unassigned Created: 25/Jun/15 12:54 PM Fix Versions: 1.0 Priority: Blocker Reporter: Federico Grilli In 0.5 we provide basic groups, roles and users for the travel-demo. Now we need to go a step further and ensure no STK roles are directly bootstrapped by single apps but it's rather STK itself to add the needed roles/groups. Also we should make sure STK demo-project users and new travel-demo users do not conflict. Add Comment
[magnolia-dev] [JIRA] (MGNLRESTCL-10) Documentation
Title: Message Title Roman Kovařk updated an issue REST Client / MGNLRESTCL-10 Documentation Change By: Roman Kovařk Assignee: RomanKovařk JaroslavSimak Add Comment This message was sent by Atlassian JIRA (v6.4.7#64022-sha1:4cb2968) Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html Alternatively,useourforums:http://forum.magnolia-cms.com/ Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] (MGNLDEMO-30) Create users and roles for demonstration purposes
Title: Message Title
Federico Grilli updated an issue
Magnolia Demo Projects / MGNLDEMO-30
Create users and roles for demonstration purposes
Change By:
Federico Grilli
BasicproposalWeneedtocreatetwousertypologies:editorandpublisher-wecreatetwototallyindependentrolesforthesinglepurposeofthetravel-demoandthusalsoprefixthemwithtravel-demo---{{travel-demo-editor}}and{{travel-demo-publisher}}-anadditional{{travel-demo-base}}roleiscreatedwhichcanaccessadminCentralandtours,dam,categorisationworkspaces-twogroupswillbecreated{{travel-demo-editors}}and{{travel-demo-publishers}}withtheneededrolestocarryouttheirwork-ifworkflowisinstalled{{travel-demo-publishers}}willbeaddedto{{/modules/workflow-jbpm/tasks/publish/groups}}sotobeabletoseeworkflowtasksSoeventually,we'llendupwith{{eric}}(editor)={{travel-demo-editors}}/password=eric{{eric-de}}(Germaneditor)={{travel-demo-editors}}(likeericbutwithUIlanguagesettingsinGerman)/password=eric{{peter}}(publisher)={{travel-demo-publishers}}/password=peter{{tina}}(canonlyoperateontoursapp)={{travel-demo-base}}/password=tina*Allroles,groupsanduserscreatedbythetravel-demoarebootstrappedassamples*Findingsduringimplementation--Someappsgrantthemselvesaccessibilitytocertainactionsandroles(e.g.{{demo-project-}}fromSTKor{{editor}}and{{publisher}}availableonlywithworkflow).E.g.byissuingthefollowingqueryonthelatest5.4-SNAPSHOTEE-bundle{{select*from[nt:base]astwherecontains(t.*,'demo-project-%')orcontains(t.*,'editor')orcontains(t.*,'publisher')}}onegetsthefollowingrelevantresults{code}/modules/pages/apps/pages/subApps/browser/actions/activate/availability/access/roles/modules/dam-app/apps/assets/permissions/roles/modules/categorization/apps/categories/permissions/roles/modules/tours/apps/tourCategories/permissions/roles{code}Forthesakeofclarityandconsistencythoseshouldberemovedandletprojectsdefineroleswhichcanaccess some needed appsandactions.Bythesametoken,I'daddpermissionstoallappgroupsunder{{/modules/ui-admincentral/config/appLauncherLayout/groups}}andgrantthembydefaultto{{superuser}}only.Itwillbeaprojectconcerntoadditsrolesbygivingpermissionstotheappropriateroles(andwecouldcertainlyprovidegeneric{{Task}}stomakeiteasier).Inourcase,itwillbe{{magnolia-travel-demo}}tocreaterolesanddecidewhichappstheycanaccess.
Add Comment
[magnolia-dev] [JIRA] (MGNLDEMO-30) Create users and roles for demonstration purposes
Title: Message Title
Federico Grilli updated an issue
Magnolia Demo Projects / MGNLDEMO-30
Create users and roles for demonstration purposes
Change By:
Federico Grilli
Mustprovideericpeterasinolddemo.Howeverthisshouldbeimplementedbetterbyhavingabaseroleforadministratorsprovidedbyadmincentral.Additionally-todemonstratetranslationofui-provideanewusereric-dethatisthesameasericbutgerman.Additionally-todemonstrateoneofthekeyusecasesofapps-provideanewusertanyawhocanONLYaccessthetoursapp-notthepagesorcategoriesapps.BasicproposalWeneedtocreatetwousertypologies:editorandpublisher We we wouldcreatetwototallyindependentrolesforthesinglepurposeofthetravel-demoandthusalsoprefixthemwithtravel-demo--a basesecurityrolealreadyexistswhichdeniesaccesstosomepartofAdminCentral.Howeveritmostlycontainsoutdatedstuff(relatedtooldAdminInterface). travel - thenweeitherneedaverybasicroletoaccessAdminCentral.ThiscanbeabrandnewroleprovidedbymainorwemayaddpermissionstoaccessAdminCentraltosecurity- demo base itself Soeventually,eric(editor)=security-base(+ui-admin-base)+travel-demo-editorpeter(publisher)=security-base(+ui-admin-base)+travel-demo-publishereditorandpublishermustbeabletoaccessfollowingapps-pages,contacts,dam,tours,(previewasvisitoronee?)editorcanperformeditandpublish.Hecan'tseeworkflowtaskspublishercan'teditbutcanpublish.HemustseeworkflowtasksSomeappsgrantthemselvesaccessibilitytocertainactionsandroles(e.g.{{demo-project-}}fromSTKor{{editor}}and{{publisher}}availableonlywithworkflow).E.g.byissuingthefollowingqueryonthelatest5.4-SNAPSHOTEE-bundle{{select*from[nt:base]astwherecontains(t.*,'demo-project-%')orcontains(t.*,'editor')orcontains(t.*,'publisher')}}onegetsthefollowingrelevantresults{code}/modules/pages/apps/pages/subApps/browser/actions/activate/availability/access/roles/modules/dam-app/apps/assets/permissions/roles/modules/categorization/apps/categories/permissions/roles/modules/tours/apps/tourCategories/permissions/roles{code}Forthesakeofclarityandconsistencyshouldn'tthoseberemovedandletprojectsdefineroleswhichcanaccesssomeappsandactions?Bythesametoken,I'daddpermissionstoallappgroupsunder{{/modules/ui-admincentral/config/appLauncherLayout/groups}}andgrantthembydefaultto{{superuser}}only.Itwillbeaprojectconcerntoadditsrolesbygivingpermissionstotheappropriateroles(andwecouldcertainlyprovidegeneric{{Task}}stomakeiteasier).Inourcase,itwillbe{{magnolia-travel-demo}}tocreaterolesanddecidewhichappstheycanaccess.
Add Comment
[magnolia-dev] [JIRA] (MGNLDEMO-30) Create users and roles for demonstration purposes
Title: Message Title Federico Grilli updated an issue Magnolia Demo Projects / MGNLDEMO-30 Create users and roles for demonstration purposes Change By: Federico Grilli Priority: Neutral Critical Add Comment This message was sent by Atlassian JIRA (v6.4.7#64022-sha1:4cb2968) Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html Alternatively,useourforums:http://forum.magnolia-cms.com/ Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] (MGNLDEMO-30) Create users and roles for demonstration purposes
Title: Message Title
Federico Grilli updated an issue
Magnolia Demo Projects / MGNLDEMO-30
Create users and roles for demonstration purposes
Change By:
Federico Grilli
BasicproposalWeneedtocreatetwousertypologies:editorandpublisher-wecreatetwototallyindependentrolesforthesinglepurposeofthetravel-demoandthusalsoprefixthemwithtravel-demo---{{travel-demo-editor}}and{{travel-demo-publisher}}-anadditional{{travel-demo-base}}roleiscreatedwhichcanaccessadminCentralandtoursworkspace-twogroupswillbecreated{{travel-demo-editors}}and{{travel-demo-publishers}}withtheneededrolestocarryouttheirwork -ifworkflowisinstalled{{travel-demo-publishers}}willbeaddedto{{/modules/workflow-jbpm/tasks/publish/groups}}sotobeabletoseeworkflowtasks Soeventually,we'llendupwith{{eric}}(editor)={{travel-demo-editors}}{{eric-de}}(Germaneditor)={{travel-demo-editors}}(likeericbutwithUIlanguagesettingsinGerman){{peter}}(publisher)={{travel-demo-publishers}}{{tina}}(canonlyoperateontoursapp)={{travel-demo-base}}*passwordsfortheaboveusersareequaltotheirusername* *Allroles,groupsanduserscreatedbythetravel-demoarebootstrappedassamples* Findingsduringimplementation--Someappsgrantthemselvesaccessibilitytocertainactionsandroles(e.g.{{demo-project-}}fromSTKor{{editor}}and{{publisher}}availableonlywithworkflow).E.g.byissuingthefollowingqueryonthelatest5.4-SNAPSHOTEE-bundle{{select*from[nt:base]astwherecontains(t.*,'demo-project-%')orcontains(t.*,'editor')orcontains(t.*,'publisher')}}onegetsthefollowingrelevantresults{code}/modules/pages/apps/pages/subApps/browser/actions/activate/availability/access/roles/modules/dam-app/apps/assets/permissions/roles/modules/categorization/apps/categories/permissions/roles/modules/tours/apps/tourCategories/permissions/roles{code}Forthesakeofclarityandconsistencythoseshouldberemovedandletprojectsdefineroleswhichcanaccesssomeappsandactions.Bythesametoken,I'daddpermissionstoallappgroupsunder{{/modules/ui-admincentral/config/appLauncherLayout/groups}}andgrantthembydefaultto{{superuser}}only.Itwillbeaprojectconcerntoadditsrolesbygivingpermissionstotheappropriateroles(andwecouldcertainlyprovidegeneric{{Task}}stomakeiteasier).Inourcase,itwillbe{{magnolia-travel-demo}}tocreaterolesanddecidewhichappstheycanaccess.
Add Comment
[magnolia-dev] [JIRA] (MGNLDEMO-30) Create users and roles for demonstration purposes
Title: Message Title
Federico Grilli updated an issue
Magnolia Demo Projects / MGNLDEMO-30
Create users and roles for demonstration purposes
Change By:
Federico Grilli
BasicproposalWeneedtocreatetwousertypologies:editorandpublisher-wecreatetwototallyindependentrolesforthesinglepurposeofthetravel-demoandthusalsoprefixthemwithtravel-demo---{{travel-demo-editor}}and{{travel-demo-publisher}}-anadditional{{travel-demo-base}}roleiscreatedwhichcanaccessadminCentralandtours,dam,categorisationworkspaces-twogroupswillbecreated{{travel-demo-editors}}and{{travel-demo-publishers}}withtheneededrolestocarryouttheirwork-ifworkflowisinstalled{{travel-demo-publishers}}willbeaddedto{{/modules/workflow-jbpm/tasks/publish/groups}}sotobeabletoseeworkflowtasksSoeventually,we'llendupwith{{eric}}(editor)={{travel-demo-editors}}/password=eric{{eric-de}}(Germaneditor)={{travel-demo-editors}}(likeericbutwithUIlanguagesettingsinGerman)/password=eric{{peter}}(publisher)={{travel-demo-publishers}}/password=peter{{tina}}(canonlyoperateontoursapp)={{travel-demo-base}}/password=tina *passwordsfortheaboveusersareequaltotheirusername* *Allroles,groupsanduserscreatedbythetravel-demoarebootstrappedassamples*Findingsduringimplementation--Someappsgrantthemselvesaccessibilitytocertainactionsandroles(e.g.{{demo-project-}}fromSTKor{{editor}}and{{publisher}}availableonlywithworkflow).E.g.byissuingthefollowingqueryonthelatest5.4-SNAPSHOTEE-bundle{{select*from[nt:base]astwherecontains(t.*,'demo-project-%')orcontains(t.*,'editor')orcontains(t.*,'publisher')}}onegetsthefollowingrelevantresults{code}/modules/pages/apps/pages/subApps/browser/actions/activate/availability/access/roles/modules/dam-app/apps/assets/permissions/roles/modules/categorization/apps/categories/permissions/roles/modules/tours/apps/tourCategories/permissions/roles{code}Forthesakeofclarityandconsistencythoseshouldberemovedandletprojectsdefineroleswhichcanaccesssomeappsandactions.Bythesametoken,I'daddpermissionstoallappgroupsunder{{/modules/ui-admincentral/config/appLauncherLayout/groups}}andgrantthembydefaultto{{superuser}}only.Itwillbeaprojectconcerntoadditsrolesbygivingpermissionstotheappropriateroles(andwecouldcertainlyprovidegeneric{{Task}}stomakeiteasier).Inourcase,itwillbe{{magnolia-travel-demo}}tocreaterolesanddecidewhichappstheycanaccess.
Add Comment
[magnolia-dev] [JIRA] (MGNLDEMO-30) Create users and roles for demonstration purposes
Title: Message Title
Federico Grilli updated an issue
Magnolia Demo Projects / MGNLDEMO-30
Create users and roles for demonstration purposes
Change By:
Federico Grilli
BasicproposalWeneedtocreatetwousertypologies:editorandpublisher-wecreatetwototallyindependentrolesforthesinglepurposeofthetravel-demoandthusalsoprefixthemwithtravel-demo---{{travel-demo-editor}}and{{travel-demo-publisher}}-anadditional{{travel-demo-base}}roleiscreatedwhichcanaccessadminCentralandtours,dam,categorisationworkspaces-twogroupswillbecreated{{travel-demo-editors}}and{{travel-demo-publishers}}withtheneededrolestocarryouttheirwork-ifworkflowisinstalled{{travel-demo-publishers}}willbeaddedto{{/modules/workflow-jbpm/tasks/publish/groups}}sotobeabletoseeworkflowtasksSoeventually,we'llendupwith{{eric}}(editor)={{travel-demo-editors}} /password=eric {{eric-de}}(Germaneditor)={{travel-demo-editors}}(likeericbutwithUIlanguagesettingsinGerman) /password=eric {{peter}}(publisher)={{travel-demo-publishers}} /password=peter {{tina}}(canonlyoperateontoursapp)={{travel-demo-base}} /password=tina *passwordsfortheaboveusersareequaltotheirusername**Allroles,groupsanduserscreatedbythetravel-demoarebootstrappedassamples*Findingsduringimplementation--Someappsgrantthemselvesaccessibilitytocertainactionsandroles(e.g.{{demo-project-}}fromSTKor{{editor}}and{{publisher}}availableonlywithworkflow).E.g.byissuingthefollowingqueryonthelatest5.4-SNAPSHOTEE-bundle{{select*from[nt:base]astwherecontains(t.*,'demo-project-%')orcontains(t.*,'editor')orcontains(t.*,'publisher')}}onegetsthefollowingrelevantresults{code}/modules/pages/apps/pages/subApps/browser/actions/activate/availability/access/roles/modules/dam-app/apps/assets/permissions/roles/modules/categorization/apps/categories/permissions/roles/modules/tours/apps/tourCategories/permissions/roles{code}Forthesakeofclarityandconsistencythoseshouldberemovedandletprojectsdefineroleswhichcanaccesssomeappsandactions.Bythesametoken,I'daddpermissionstoallappgroupsunder{{/modules/ui-admincentral/config/appLauncherLayout/groups}}andgrantthembydefaultto{{superuser}}only.Itwillbeaprojectconcerntoadditsrolesbygivingpermissionstotheappropriateroles(andwecouldcertainlyprovidegeneric{{Task}}stomakeiteasier).Inourcase,itwillbe{{magnolia-travel-demo}}tocreaterolesanddecidewhichappstheycanaccess.
Add Comment
[magnolia-dev] [JIRA] (MGNLDEMO-30) Create users and roles for demonstration purposes
Title: Message Title
Federico Grilli updated an issue
Magnolia Demo Projects / MGNLDEMO-30
Create users and roles for demonstration purposes
Change By:
Federico Grilli
BasicproposalWeneedtocreatetwousertypologies:editorandpublisher-wecreatetwototallyindependentrolesforthesinglepurposeofthetravel-demoandthusalsoprefixthemwithtravel-demo---{{travel-demo-editor}}and{{travel-demo-publisher}}-anadditional{{travel-demo-base}}roleiscreatedwhichcanaccessadminCentralandtours workspace ,dam,categorisationworkspaces -twogroupswillbecreated{{travel-demo-editors}}and{{travel-demo-publishers}}withtheneededrolestocarryouttheirwork-ifworkflowisinstalled{{travel-demo-publishers}}willbeaddedto{{/modules/workflow-jbpm/tasks/publish/groups}}sotobeabletoseeworkflowtasksSoeventually,we'llendupwith{{eric}}(editor)={{travel-demo-editors}}{{eric-de}}(Germaneditor)={{travel-demo-editors}}(likeericbutwithUIlanguagesettingsinGerman){{peter}}(publisher)={{travel-demo-publishers}}{{tina}}(canonlyoperateontoursapp)={{travel-demo-base}}*passwordsfortheaboveusersareequaltotheirusername**Allroles,groupsanduserscreatedbythetravel-demoarebootstrappedassamples*Findingsduringimplementation--Someappsgrantthemselvesaccessibilitytocertainactionsandroles(e.g.{{demo-project-}}fromSTKor{{editor}}and{{publisher}}availableonlywithworkflow).E.g.byissuingthefollowingqueryonthelatest5.4-SNAPSHOTEE-bundle{{select*from[nt:base]astwherecontains(t.*,'demo-project-%')orcontains(t.*,'editor')orcontains(t.*,'publisher')}}onegetsthefollowingrelevantresults{code}/modules/pages/apps/pages/subApps/browser/actions/activate/availability/access/roles/modules/dam-app/apps/assets/permissions/roles/modules/categorization/apps/categories/permissions/roles/modules/tours/apps/tourCategories/permissions/roles{code}Forthesakeofclarityandconsistencythoseshouldberemovedandletprojectsdefineroleswhichcanaccesssomeappsandactions.Bythesametoken,I'daddpermissionstoallappgroupsunder{{/modules/ui-admincentral/config/appLauncherLayout/groups}}andgrantthembydefaultto{{superuser}}only.Itwillbeaprojectconcerntoadditsrolesbygivingpermissionstotheappropriateroles(andwecouldcertainlyprovidegeneric{{Task}}stomakeiteasier).Inourcase,itwillbe{{magnolia-travel-demo}}tocreaterolesanddecidewhichappstheycanaccess.
Add Comment
[magnolia-dev] [JIRA] (MGNLRESTCL-10) Documentation
Title: Message Title Jan Haderka updated an issue REST Client / MGNLRESTCL-10 Documentation Change By: Jan Haderka Assignee: JanHaderka RomanKovařk Add Comment This message was sent by Atlassian JIRA (v6.4.7#64022-sha1:4cb2968) Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html Alternatively,useourforums:http://forum.magnolia-cms.com/ Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] (MGNLUI-3474) App launcher is no longer translated - always english
Title: Message Title Christopher Zimmermann created an issue Magnolia UI / MGNLUI-3474 App launcher is no longer translated - always english Issue Type: Bug Affects Versions: 5.4 Assignee: Unassigned Created: 25/Jun/15 3:17 PM Fix Versions: 5.4 Priority: Critical Reporter: Christopher Zimmermann Security Level: Public If you switch the language of superuser to german and log out and in again - the app launcher is still in english. If you open an app - the app is show in german.
[magnolia-dev] [JIRA] (MGNLUI-3473) Tranformer for TwinColumnField: Provide transformers alike the DelegatingMultiValueFieldTransformer and DelegatingMultiValueSubnodeTransformer for the TwinColumnFi
Title: Message Title Christian Ringele created an issue Magnolia UI / MGNLUI-3473 Tranformer for TwinColumnField: Provide transformers alike the DelegatingMultiValueFieldTransformer and DelegatingMultiValueSubnodeTransformer for the TwinColumnField Issue Type: Improvement Affects Versions: 5.3.9 Assignee: Unassigned Components: forms Created: 25/Jun/15 2:46 PM Labels: support Priority: Neutral Reporter: Christian Ringele Security Level: Public The TwinColumnField (actually a ComboBox) stores the data by default into a JCR MultiValue property. Same as the as the MultiField does by default. There is also the need for TwinColumnField to have this
[magnolia-dev] [JIRA] (MGNLDEMO-30) Create users and roles for demonstration purposes
Title: Message Title
Federico Grilli updated an issue
Magnolia Demo Projects / MGNLDEMO-30
Create users and roles for demonstration purposes
Change By:
Federico Grilli
Mustprovideericpeterasinolddemo.Howeverthisshouldbeimplementedbetterbyhavingabaseroleforadministratorsprovidedbyadmincentral.Additionally-todemonstratetranslationofui-provideanewusereric-dethatisthesameasericbutgerman.Additionally-todemonstrateoneofthekeyusecasesofapps-provideanewusertanyawhocanONLYaccessthetoursapp-notthepagesorcategoriesapps. BasicproposalWeneedtocreatetwousertypologies:editorandpublisher - we would createtwototallyindependentrolesforthesinglepurposeofthetravel-demoandthusalsoprefixthemwithtravel-demo-- a -{{ travel-demo -editor}}and{{travel-demo-publisher}}-anadditional{{travel-demo- base }}roleiscreatedwhichcanaccessadminCentralandtoursworkspace -twogroupswillbecreated{{travel-demo-editors}}and{{travel-demo-publishers}}withtheneededrolestocarryouttheirwork Soeventually, we'llendupwith{{ eric }} (editor)= security {{travel - base(+ui demo - admin editors}}{{eric - base de}}(Germaneditor ) + ={{ travel-demo- editor editors}}(likeericbutwithUIlanguagesettingsinGerman) {{ peter }} (publisher)= security {{travel - base(+ui demo - admin-base publishers}}{{tina}}(canonlyoperateontoursapp ) + ={{ travel-demo- publishereditorandpublishermustbeable base}}*passwordsfortheaboveusersareequal to accessfollowingapps theirusername* -pages,contacts,dam,tours,(previewasvisitoronee?) editorcanperformeditandpublish.Hecan'tseeworkflowtasks publishercan'teditbutcanpublish.Hemustseeworkflowtasks Findingsduringimplementation -- Someappsgrantthemselvesaccessibilitytocertainactionsandroles(e.g.{{demo-project-}}fromSTKor{{editor}}and{{publisher}}availableonlywithworkflow).E.g.byissuingthefollowingqueryonthelatest5.4-SNAPSHOTEE-bundle{{select*from[nt:base]astwherecontains(t.*,'demo-project-%')orcontains(t.*,'editor')orcontains(t.*,'publisher')}}onegetsthefollowingrelevantresults{code}/modules/pages/apps/pages/subApps/browser/actions/activate/availability/access/roles/modules/dam-app/apps/assets/permissions/roles/modules/categorization/apps/categories/permissions/roles/modules/tours/apps/tourCategories/permissions/roles{code}Forthesakeofclarityandconsistency shouldn't those should beremovedandletprojectsdefineroleswhichcanaccesssomeappsandactions ? . Bythesametoken,I'daddpermissionstoallappgroupsunder{{/modules/ui-admincentral/config/appLauncherLayout/groups}}andgrantthembydefaultto{{superuser}}only.Itwillbeaprojectconcerntoadditsrolesbygivingpermissionstotheappropriateroles(andwecouldcertainlyprovidegeneric{{Task}}stomakeiteasier).Inourcase,itwillbe{{magnolia-travel-demo}}tocreaterolesanddecidewhichappstheycanaccess.
[magnolia-dev] [JIRA] (MGNLDEMO-69) Tours and Destinations text in Nav use wrong i18n mechanism
Title: Message Title Christopher Zimmermann updated an issue Magnolia Demo Projects / MGNLDEMO-69 Tours and Destinations text in Nav use wrong i18n mechanism Change By: Christopher Zimmermann Currentlyits ThecategorymenuheadersDestinationsandTourTypesare translatedbasedon theloggedin user 's language-ratherthanwebsitecontentlanguage. Add Comment This message was sent by Atlassian JIRA (v6.4.7#64022-sha1:4cb2968) Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html Alternatively,useourforums:http://forum.magnolia-cms.com/ Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] (MGNLWORKFLOW-293) Support multiple selection items for publishDeletion action
Title: Message Title Espen Jervidalo reopened an issue This does not work. As far as I can tell the UI test should always fail, when it goes back to the browser and checks for the two deleted pages not being there. So far I only debugged it locally. This is actually a very tricky and big ticket. The implemented part of it is probably right, but as soon as the workflow is launched, only one of the paths of the nodes to-be-deleted is passed. The paths should be passed as a List into the workflow and also be displayed like that into the messageView. There are a lot of problems to be solved to get this working. info.magnolia.module.workflow.commands.PublicationWorkflowCommand#setPath info.magnolia.module.workflow.commands.PublicationWorkflowCommand#getWorkflow I guess the ActivationCommand would have to support multiple paths, similar to how it handles recursive activations. Apart from that I don't get why we would implement this for deleting pages, but not for activating the pages. Magnolia Workflow Module / MGNLWORKFLOW-293 Support multiple selection items for publishDeletion action Change By: Espen Jervidalo Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.7#64022-sha1:4cb2968)
[magnolia-dev] [JIRA] (MGNLDEMO-63) Add a dedication to the Impressum page
Title: Message Title Christopher Zimmermann updated an issue Magnolia Demo Projects / MGNLDEMO-63 Add a dedication to the Impressum page Change By: Christopher Zimmermann Assignee: ChristopherZimmermann Add Comment This message was sent by Atlassian JIRA (v6.4.7#64022-sha1:4cb2968) Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html Alternatively,useourforums:http://forum.magnolia-cms.com/ Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] (MGNLUI-3474) App launcher is no longer translated - always english
Title: Message Title Aleksandr Pchelintcev updated an issue Magnolia UI / MGNLUI-3474 App launcher is no longer translated - always english Change By: Aleksandr Pchelintcev Assignee: AleksandrPchelintcev Add Comment This message was sent by Atlassian JIRA (v6.4.7#64022-sha1:4cb2968) Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html Alternatively,useourforums:http://forum.magnolia-cms.com/ Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] (MGNLDEMO-30) Create users and roles for demonstration purposes
Title: Message Title
Federico Grilli updated an issue
Magnolia Demo Projects / MGNLDEMO-30
Create users and roles for demonstration purposes
Change By:
Federico Grilli
BasicproposalWeneedtocreatetwousertypologies:editorandpublisher-wecreatetwototallyindependentrolesforthesinglepurposeofthetravel-demoandthusalsoprefixthemwithtravel-demo---{{travel-demo-editor}}and{{travel-demo-publisher}} *notetoworkaroundMGNLUI-3200thelatterrolehasR/Wpermissionsonwebsite,otherwises/hecan'tpublish* -anadditional{{travel-demo-base}}roleiscreatedwhichcanaccessadminCentralandtours,dam,categorisationworkspaces-twogroupswillbecreated{{travel-demo-editors}}and{{travel-demo-publishers}}withtheneededrolestocarryouttheirwork *notetoworkaround* -ifworkflowisinstalled{{travel-demo-publishers}}willbeaddedto{{/modules/workflow-jbpm/tasks/publish/groups}}sotobeabletoseeworkflowtasksSoeventually,we'llendupwith{{eric}}(editor)={{travel-demo-editors}}/password=eric{{eric-de}}(Germaneditor)={{travel-demo-editors}}(likeericbutwithUIlanguagesettingsinGerman)/password=eric-de{{peter}}(publisher)={{travel-demo-publishers}}/password=peter{{tina}}(canonlyoperateontoursapp)={{travel-demo-base}}/password=tina*Allroles,groupsanduserscreatedbythetravel-demoarebootstrappedassamples*Findingsduringimplementation--Someappsgrantthemselvesaccessibilitytocertainactionsandroles(e.g.{{demo-project-}}fromSTKor{{editor}}and{{publisher}}availableonlywithworkflow).E.g.byissuingthefollowingqueryonthelatest5.4-SNAPSHOTEE-bundle{{select*from[nt:base]astwherecontains(t.*,'demo-project-%')orcontains(t.*,'editor')orcontains(t.*,'publisher')}}onegetsthefollowingrelevantresults{code}/modules/pages/apps/pages/subApps/browser/actions/activate/availability/access/roles/modules/dam-app/apps/assets/permissions/roles/modules/categorization/apps/categories/permissions/roles/modules/tours/apps/tourCategories/permissions/roles{code}Forthesakeofclarityandconsistencythoseshouldberemovedandletprojectsdefineroleswhichcanaccessneededappsandactions.Bythesametoken,I'daddpermissionstoallappgroupsunder{{/modules/ui-admincentral/config/appLauncherLayout/groups}}andgrantthembydefaultto{{superuser}}only.Itwillbeaprojectconcerntoadditsrolesbygivingpermissionstotheappropriateroles(andwecouldcertainlyprovidegeneric{{Task}}stomakeiteasier).Inourcase,itwillbe{{magnolia-travel-demo}}tocreaterolesanddecidewhichappstheycanaccess.
Add Comment
[magnolia-dev] [JIRA] (MGNLDEMO-30) Create users and roles for demonstration purposes
Title: Message Title
Federico Grilli updated an issue
Magnolia Demo Projects / MGNLDEMO-30
Create users and roles for demonstration purposes
Change By:
Federico Grilli
BasicproposalWeneedtocreatetwousertypologies:editorandpublisher-wecreatetwototallyindependentrolesforthesinglepurposeofthetravel-demoandthusalsoprefixthemwithtravel-demo---{{travel-demo-editor}}and{{travel-demo-publisher}}-anadditional{{travel-demo-base}}roleiscreatedwhichcanaccessadminCentralandtours,dam,categorisationworkspaces-twogroupswillbecreated{{travel-demo-editors}}and{{travel-demo-publishers}}withtheneededrolestocarryouttheirwork *notetoworkaround* -ifworkflowisinstalled{{travel-demo-publishers}}willbeaddedto{{/modules/workflow-jbpm/tasks/publish/groups}}sotobeabletoseeworkflowtasksSoeventually,we'llendupwith{{eric}}(editor)={{travel-demo-editors}}/password=eric{{eric-de}}(Germaneditor)={{travel-demo-editors}}(likeericbutwithUIlanguagesettingsinGerman)/password=eric -de {{peter}}(publisher)={{travel-demo-publishers}}/password=peter{{tina}}(canonlyoperateontoursapp)={{travel-demo-base}}/password=tina *Allroles,groupsanduserscreatedbythetravel-demoarebootstrappedassamples*Findingsduringimplementation--Someappsgrantthemselvesaccessibilitytocertainactionsandroles(e.g.{{demo-project-}}fromSTKor{{editor}}and{{publisher}}availableonlywithworkflow).E.g.byissuingthefollowingqueryonthelatest5.4-SNAPSHOTEE-bundle{{select*from[nt:base]astwherecontains(t.*,'demo-project-%')orcontains(t.*,'editor')orcontains(t.*,'publisher')}}onegetsthefollowingrelevantresults{code}/modules/pages/apps/pages/subApps/browser/actions/activate/availability/access/roles/modules/dam-app/apps/assets/permissions/roles/modules/categorization/apps/categories/permissions/roles/modules/tours/apps/tourCategories/permissions/roles{code}Forthesakeofclarityandconsistencythoseshouldberemovedandletprojectsdefineroleswhichcanaccessneededappsandactions.Bythesametoken,I'daddpermissionstoallappgroupsunder{{/modules/ui-admincentral/config/appLauncherLayout/groups}}andgrantthembydefaultto{{superuser}}only.Itwillbeaprojectconcerntoadditsrolesbygivingpermissionstotheappropriateroles(andwecouldcertainlyprovidegeneric{{Task}}stomakeiteasier).Inourcase,itwillbe{{magnolia-travel-demo}}tocreaterolesanddecidewhichappstheycanaccess.
Add Comment
[magnolia-dev] [JIRA] (MGNLDEMO-30) Create users and roles for demonstration purposes
Title: Message Title
Federico Grilli updated an issue
Magnolia Demo Projects / MGNLDEMO-30
Create users and roles for demonstration purposes
Change By:
Federico Grilli
BasicproposalWeneedtocreatetwousertypologies:editorandpublisher-wecreatetwototallyindependentrolesforthesinglepurposeofthetravel-demoandthusalsoprefixthemwithtravel-demo---{{travel-demo-editor}}and{{travel-demo-publisher}}* note Note: toworkaroundMGNLUI-3200thelatterrolehasR/Wpermissionsonwebsite,otherwises/hecan'tpublish*-anadditional{{travel-demo-base}}roleiscreatedwhichcanaccessadminCentralandtours,dam,categorisationworkspaces-twogroupswillbecreated{{travel-demo-editors}}and{{travel-demo-publishers}}withtheneededrolestocarryouttheirwork-ifworkflowisinstalled{{travel-demo-publishers}}willbeaddedto{{/modules/workflow-jbpm/tasks/publish/groups}}sotobeabletoseeworkflowtasksSoeventually,we'llendupwith{{eric}}(editor)={{travel-demo-editors}}/password=eric{{eric-de}}(Germaneditor)={{travel-demo-editors}}(likeericbutwithUIlanguagesettingsinGerman)/password=eric-de{{peter}}(publisher)={{travel-demo-publishers}}/password=peter{{tina}}(canonlyoperateontoursapp)={{travel-demo-base}}/password=tina*Allroles,groupsanduserscreatedbythetravel-demoarebootstrappedassamples*Findingsduringimplementation--Someappsgrantthemselvesaccessibilitytocertainactionsandroles(e.g.{{demo-project-}}fromSTKor{{editor}}and{{publisher}}availableonlywithworkflow).E.g.byissuingthefollowingqueryonthelatest5.4-SNAPSHOTEE-bundle{{select*from[nt:base]astwherecontains(t.*,'demo-project-%')orcontains(t.*,'editor')orcontains(t.*,'publisher')}}onegetsthefollowingrelevantresults{code}/modules/pages/apps/pages/subApps/browser/actions/activate/availability/access/roles/modules/dam-app/apps/assets/permissions/roles/modules/categorization/apps/categories/permissions/roles/modules/tours/apps/tourCategories/permissions/roles{code}Forthesakeofclarityandconsistencythoseshouldberemovedandletprojectsdefineroleswhichcanaccessneededappsandactions.Bythesametoken,I'daddpermissionstoallappgroupsunder{{/modules/ui-admincentral/config/appLauncherLayout/groups}}andgrantthembydefaultto{{superuser}}only.Itwillbeaprojectconcerntoadditsrolesbygivingpermissionstotheappropriateroles(andwecouldcertainlyprovidegeneric{{Task}}stomakeiteasier).Inourcase,itwillbe{{magnolia-travel-demo}}tocreaterolesanddecidewhichappstheycanaccess.
Add Comment
[magnolia-dev] [JIRA] (MGNLDEMO-30) Create users and roles for demonstration purposes
Title: Message Title Federico Grilli updated an issue Magnolia Demo Projects / MGNLDEMO-30 Create users and roles for demonstration purposes Change By: Federico Grilli Release notes required: Yes Add Comment This message was sent by Atlassian JIRA (v6.4.7#64022-sha1:4cb2968) Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html Alternatively,useourforums:http://forum.magnolia-cms.com/ Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] (MGNLDEMO-69) Tours and Destinations text in Nav use wrong i18n mechanism
Title: Message Title Christopher Zimmermann created an issue Magnolia Demo Projects / MGNLDEMO-69 Tours and Destinations text in Nav use wrong i18n mechanism Issue Type: Bug Affects Versions: 0.5 Assignee: Christopher Zimmermann Created: 25/Jun/15 6:43 PM Fix Versions: 0.5 Priority: Neutral Reporter: Christopher Zimmermann Currently its translated based on user language - rather than website content language. Add Comment
[magnolia-dev] [JIRA] (MGNLDEMO-67) Website should have UI element to switch language
Title: Message Title Christopher Zimmermann updated an issue Magnolia Demo Projects / MGNLDEMO-67 Website should have UI element to switch language Change By: Christopher Zimmermann Fix Version/s: 0.5 Add Comment This message was sent by Atlassian JIRA (v6.4.7#64022-sha1:4cb2968) Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html Alternatively,useourforums:http://forum.magnolia-cms.com/ Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] (MGNLUI-3424) Allow multi-fields (composite, switchable, multi-value) to become read only
Title: Message Title Eric Hechinger updated an issue Magnolia UI / MGNLUI-3424 Allow multi-fields (composite, switchable, multi-value) to become read only Change By: Eric Hechinger Attachment: magnolia_ui.patch Add Comment This message was sent by Atlassian JIRA (v6.4.7#64022-sha1:4cb2968) Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html Alternatively,useourforums:http://forum.magnolia-cms.com/ Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] (MGNLUI-3424) Allow multi-fields (composite, switchable, multi-value) to become read only
Title: Message Title Eric Hechinger updated an issue Magnolia UI / MGNLUI-3424 Allow multi-fields (composite, switchable, multi-value) to become read only Change By: Eric Hechinger Summary: Allow multivaluefield multi-fields(composite,switchable,multi-value) tobecomereadonly Add Comment This message was sent by Atlassian JIRA (v6.4.7#64022-sha1:4cb2968) Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html Alternatively,useourforums:http://forum.magnolia-cms.com/ Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com
