[magnolia-dev] [JIRA] (MCTP-7) Detect and register newly added content-types at runtime
Title: Message Title Espen Jervidalo updated an issue Magnolia Content Types Project / MCTP-7 Detect and register newly added content-types at runtime Change By: Espen Jervidalo Removes the need to manually trigger reload of module for registration to happen. This does not cover more sophisticated use-cases like, changes to files Add Comment This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf) 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] (MCTP-7) Detect and register newly added content-types at runtime
Title: Message Title Espen Jervidalo updated an issue Magnolia Content Types Project / MCTP-7 Detect and register newly added content-types at runtime Change By: Espen Jervidalo Removes the need to manually trigger reload of module for registration to happen. This does not cover more sophisticated use-cases like, changes to files . Add Comment This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf) 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] (MCTP-7) Detect and register newly added content-types at runtime
Title: Message Title Espen Jervidalo created an issue Magnolia Content Types Project / MCTP-7 Detect and register newly added content-types at runtime Issue Type: Task Assignee: Espen Jervidalo Created: 20/Mar/17 3:08 PM Priority: Neutral Reporter: Espen Jervidalo Add Comment This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf) 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] (MCTP-4) Register non-existing namespaces
Title: Message Title Espen Jervidalo updated an issue Magnolia Content Types Project / MCTP-4 Register non-existing namespaces Change By: Espen Jervidalo Assignee: Espen Jervidalo Add Comment This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf) 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] (MCTP-3) Create editor and base-permissions for registered content-types
Title: Message Title Espen Jervidalo updated an issue Magnolia Content Types Project / MCTP-3 Create editor and base-permissions for registered content-types Change By: Espen Jervidalo Fix Version/s: 0.5 Add Comment This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf) 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] (MCTP-1) Load content-types and register workspace and node-types
Title: Message Title Espen Jervidalo updated an issue Magnolia Content Types Project / MCTP-1 Load content-types and register workspace and node-types Change By: Espen Jervidalo Fix Version/s: 0.5 Fix Version/s: 1.0 Add Comment This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf) 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] (MCTP-2) Allow ad-hoc subscription of created workspaces
Title: Message Title Espen Jervidalo updated an issue Magnolia Content Types Project / MCTP-2 Allow ad-hoc subscription of created workspaces Change By: Espen Jervidalo Fix Version/s: 0.5 Fix Version/s: 1.0 Add Comment This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf) 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] (MCTP-4) Register non-existing namespaces
Title: Message Title
Espen Jervidalo updated an issue
Magnolia Content Types Project / MCTP-4
Register non-existing namespaces
Change By:
Espen Jervidalo
See https://git.magnolia-cms.com/projects/MODULES/repos/magnolia-content-types/pull-requests/3/overviewJackrabbit throws exception if you try to register nodetypes with yet unknown namespace. Namespaces need to be register with an URI. What URI should be used?Besides the exception that is thrown is swallowed. That should definitely not be the case. I'll create a follow up, as we need this commit for the others to apply.{code}info.magnolia.repository.DefaultRepositoryManager#registerNameSpacesAndNodeTypesinfo.magnolia.jackrabbit.ProviderImpl#registerNamespacejavax.jcr.NamespaceRegistry#registerNamespace{code}
Add Comment
This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: htt
[magnolia-dev] [JIRA] (MCTP-4) Register non-existing namespaces
Title: Message Title Espen Jervidalo created an issue Magnolia Content Types Project / MCTP-4 Register non-existing namespaces Issue Type: Task Assignee: Unassigned Created: 23/Feb/17 5:08 PM Priority: Neutral Reporter: Espen Jervidalo Add Comment This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf) 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] (MCTP-3) Create editor and base-permissions for registered content-types
Title: Message Title
Espen Jervidalo updated an issue
Magnolia Content Types Project / MCTP-3
Create editor and base-permissions for registered content-types
Change By:
Espen Jervidalo
After creating the the workspace we need to assign permissions to it. Upon installation of the module:- we create two roles: {{content-base}} and {{content-editor}}.- The roles are assigned to superuser respectively anonymousUpon registration of new workspaces based on the content-types:- The roles are granted {{READ}} resp. {{ALL}} permissions to the workspace
Add Comment
This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)
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] (MCTP-3) Create editor and base-permissions for registered content-types
Title: Message Title Espen Jervidalo updated an issue Magnolia Content Types Project / MCTP-3 Create editor and base-permissions for registered content-types Change By: Espen Jervidalo Assignee: Espen Jervidalo Add Comment This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf) 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] (MCTP-3) Create editor and base-permissions for registered content-types
Title: Message Title Espen Jervidalo updated an issue Magnolia Content Types Project / MCTP-3 Create editor and base-permissions for registered content-types Change By: Espen Jervidalo Summary: Create editor and base-permissions for regsitered registered content-types Add Comment This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf) 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] (MCTP-1) Load content-types and register workspace and node-types
Title: Message Title Espen Jervidalo updated an issue Magnolia Content Types Project / MCTP-1 Load content-types and register workspace and node-types Change By: Espen Jervidalo Attachment: event.yaml Add Comment This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf) 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] (MCTP-1) Load content-types and register workspace and node-types
Title: Message Title Espen Jervidalo updated an issue Magnolia Content Types Project / MCTP-1 Load content-types and register workspace and node-types Change By: Espen Jervidalo Attachment: event.ctd Add Comment This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf) 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] (MCTP-3) Create editor and base-permissions for regsitered content-types
Title: Message Title Espen Jervidalo created an issue Magnolia Content Types Project / MCTP-3 Create editor and base-permissions for regsitered content-types Issue Type: Task Assignee: Unassigned Created: 21/Feb/17 4:55 PM Priority: Neutral Reporter: Espen Jervidalo After creating the the workspace we need to assign permissions to it. Add Comment This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)
[magnolia-dev] [JIRA] (MCTP-2) Allow ad-hoc subscription of created workspaces
Title: Message Title Espen Jervidalo created an issue Magnolia Content Types Project / MCTP-2 Allow ad-hoc subscription of created workspaces Issue Type: New Feature Assignee: Unassigned Created: 16/Feb/17 11:20 AM Fix Versions: 1.0 Priority: Neutral Reporter: Espen Jervidalo Create a custom Subscriber-implementation extending today's DefaultSubscriber. In case no matching subscription is found we need to query for ad-hoc registered workspaces in the content-types module. The Subscriber(s) implementation should be changed at module install time. Reference: https://wiki.magnolia-cms.com/display/ARCHI/2017-02-13+Meeting+notes Add Comment
[magnolia-dev] [JIRA] (MCTP-1) Load content-types and register workspace and node-types
Title: Message Title
Espen Jervidalo updated an issue
Magnolia Content Types Project / MCTP-1
Load content-types and register workspace and node-types
Change By:
Espen Jervidalo
# Introduce a new key in magnolia.properties file pointing to the content-type directory.# Load all files in that directory during content-types ' module startup - phase# Create workspace and register nodetypes for the defined content-type.Minimal requirement for now is to have the name and the namespace of the content-type read from the content-type file.Example listing of the directory:{code}$ tree content-types/content-types/├── contact.ctd├── event.ctd└── my_file.ctd{code}For now we leave the files under the root-type directory and the filename is arbitrary. I don't want the namespace (e.g. 'mgnl') to be extracted from the filename.{code}$ cat contact.ctdnamspace 'mgnl'entity 'contact'{code}
Add Comment
This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)
[magnolia-dev] [JIRA] (MCTP-1) Load content-types and register workspace and node-types
Title: Message Title Espen Jervidalo created an issue Magnolia Content Types Project / MCTP-1 Load content-types and register workspace and node-types Issue Type: New Feature Assignee: Unassigned Created: 14/Feb/17 3:44 PM Fix Versions: 1.0 Priority: Neutral Reporter: Espen Jervidalo Introduce a new key in magnolia.properties file pointing to the content-type directory. Load all files in that directory during content-types module startup phase Create workspace and register nodetypes for the defined content-type. Minimal requirement for now is to have the name and the namespace of the content-type read from the content-type file. Example listing of the directory: $ tree content-types/ content-types/ ├── contact.ctd ├── event.ctd └── my_file.ctd For now we leave the files under the root-type directory and the filename is arbitrary. I don't want the namespace (e.g. 'mgnl') to be extracted from the filename. $ cat contact.ctd namspace 'mgnl' entity 'contact'
[magnolia-dev] [JIRA] (DOCU-940) Module Quickstart page needs temporary workaround notice
Title: Message Title Espen Jervidalo updated an issue Documentation / DOCU-940 Module Quickstart page needs temporary workaround notice Change By: Espen Jervidalo Issue Type: Project registration Task Add Comment This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf) 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] (DOCU-940) Module Quickstart page needs temporary workaround notice
Title: Message Title Espen Jervidalo created an issue Documentation / DOCU-940 Module Quickstart page needs temporary workaround notice Issue Type: Project registration Assignee: Unassigned Created: 14/Feb/17 2:16 PM Priority: Neutral Reporter: Espen Jervidalo Affected page: https://wiki.magnolia-cms.com/display/WIKI/Module+QuickStart#ModuleQuickStart-UsingaMavenArchetype A new version of the Maven archetype plugin has been released, which seems to have introduced a regression. To get Magnolia's archetypes resolved properly the following command needs to changed ... From: mvn archetype:generate -DarchetypeCatalog=https://nexus.magnolia-cms.com/content/groups/public/ To: mvn org.apache.maven.plugins:maven-archetype-plugin:2.4:generate -DarchetypeCatalog=https://nexus.magnolia-cms.com/content/groups/public/ Add Comment
[magnolia-dev] [JIRA] (DOCU-940) Module Quickstart page needs temporary workaround notice
Title: Message Title
Espen Jervidalo updated an issue
Documentation / DOCU-940
Module Quickstart page needs temporary workaround notice
Change By:
Espen Jervidalo
Affected page: https://wiki.magnolia-cms.com/display/WIKI/Module+QuickStart#ModuleQuickStart-UsingaMavenArchetypeA new version of the [Maven archetype plugin|http://maven.apache.org/archetype/maven-archetype-plugin/index.html] has been released, which seems to have introduced a regression. To get Magnolia's archetypes resolved properly the following command needs to changed change ...*From*:{code}mvn archetype:generate -DarchetypeCatalog=https://nexus.magnolia-cms.com/content/groups/public/{code}*To*:{code}mvn org.apache.maven.plugins:maven-archetype-plugin:2.4:generate -DarchetypeCatalog=https://nexus.magnolia-cms.com/content/groups/public/{code}
Add Comment
This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)
For list details, see: http://www.magnolia-cms.com/community/ma
[magnolia-dev] [JIRA] (DOCU-940) Module Quickstart page needs temporary workaround notice
Title: Message Title
Espen Jervidalo updated an issue
Documentation / DOCU-940
Module Quickstart page needs temporary workaround notice
Change By:
Espen Jervidalo
Affected page: https://wiki.magnolia-cms.com/display/WIKI/Module+QuickStart#ModuleQuickStart-UsingaMavenArchetypeA new version of the [Maven archetype plugin|http://maven.apache.org/archetype/maven-archetype-plugin/index.html] has been released, which seems to have introduced a regression. To get Magnolia's archetypes resolved properly the following command needs to changed ... * From * :{code}mvn archetype:generate -DarchetypeCatalog=https://nexus.magnolia-cms.com/content/groups/public/{code} * To * :{code}mvn org.apache.maven.plugins:maven-archetype-plugin:2.4:generate -DarchetypeCatalog=https://nexus.magnolia-cms.com/content/groups/public/{code}
Add Comment
This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)
For list details, see: http://www.magnolia-cms.com/community/mail
[magnolia-dev] [JIRA] (MGNLACTIVATION-146) Ad-hoc Registration of workspace to subscribers
Title: Message Title
Espen Jervidalo updated an issue
Magnolia Activation Module / MGNLACTIVATION-146
Ad-hoc Registration of workspace to subscribers
Change By:
Espen Jervidalo
We need to register workspaces without having to touch any JCR configuration. One missing piece is configuration of the workspace-subscriptions under {{/server/activation/subscribers/xy/subscriptions}}.The subscription is automatically set up during installation of the module in {{info.magnolia.module.delta.SetupModuleRepositoriesTask#subscribeRepository}}Whether the subscription (adding the node to the subscribers) is performed during install or not is voter-based. The voting mechanism is not intended (but used) for deciding whether the subscription should be performed or not, it is relevant for voting for the best subscription during an activation. This is weird and should be simplified.The idea so far is to configure the workspaces you do not want to subscribe and not as today to add those that should be subscribed.Further notes: * Introduce new API and replace usage of core-interfaces in {{info.magnolia.cms.exchange}}* Please clean up the usage of {{ repository }} in the code where ' {{ workspace ' }} is meant, at least where possible.
Add Comment
This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)
[magnolia-dev] [JIRA] (MGNLACTIVATION-146) Ad-hoc Registration of workspace to subscribers
Title: Message Title
Espen Jervidalo updated an issue
Magnolia Activation Module / MGNLACTIVATION-146
Ad-hoc Registration of workspace to subscribers
Change By:
Espen Jervidalo
We need to register workspaces without having to touch any JCR configuration. One missing piece is configuration of the workspace-subscriptions under {{/server/activation/subscribers/xy/subscriptions}}.The subscription is automatically set up during installation of the module in {{info.magnolia.module.delta.SetupModuleRepositoriesTask#subscribeRepository}}Whether the subscription (adding the node to the subscribers) is performed during install or not is voter-based. The voting mechanism is not intended (but used) for deciding whether the subscription should be performed or not, it is relevant for voting for the best subscription during an activation. This is weird and should be simplified.The idea so far is to configure the workspaces you do not want to subscribe and not as today to add those that should be subscribed.Further notes: * Introduce new API for and replace usage of core-interfaces in {{ info.magnolia.cms.exchange }} * Please clean up the usage of ' repository ' in the code where 'workspace' is meant, at least where possible.
Add Comment
This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)
[magnolia-dev] [JIRA] (MGNLACTIVATION-146) Ad-hoc Registration of workspace to subscribers
Title: Message Title
Espen Jervidalo updated an issue
Magnolia Activation Module / MGNLACTIVATION-146
Ad-hoc Registration of workspace to subscribers
Change By:
Espen Jervidalo
We need to register workspaces without having to touch any JCR configuration. One missing piece is configuration of the workspace-subscriptions under {{/server/activation/subscribers/xy/subscriptions}}.The subscription is automatically set up during installation of the module in {{info.magnolia.module.delta.SetupModuleRepositoriesTask#subscribeRepository}}Whether the subscription (adding the node to the subscribers) is performed during install or not is voter-based. The voting mechanism is not intended (but used) for deciding whether the subscription should be performed or not, it is relevant for voting for the best subscription during an activation. This is weird and should be simplified.The idea so far is to configure the workspaces you do not want to subscribe and not as today to add those that should be subscribed.Further notes: * Introduce new API for core-interfaces in info.magnolia.cms.exchange* Please clean up the usage of 'repository' in the code where 'workspace' is meant, at least where possible.
Add Comment
This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)
[magnolia-dev] [JIRA] (MGNLACTIVATION-146) Ad-hoc Registration of workspace to subscribers
Title: Message Title Espen Jervidalo updated an issue Magnolia Activation Module / MGNLACTIVATION-146 Ad-hoc Registration of workspace to subscribers Change By: Espen Jervidalo Project: Magnolia Activation Module Key: MAGNOLIA MGNLACTIVATION - 6953 146 Add Comment This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf) 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-17) Register the TaskEventDispatchers inside the task module
Title: Message Title Espen Jervidalo updated an issue Task Management / TASKMGMT-17 Register the TaskEventDispatchers inside the task module Change By: Espen Jervidalo Assignee: Espen Jervidalo Add Comment This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf) 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] (EXTIDX-20) Search singular and plural words in French
Title: Message Title Espen Jervidalo updated an issue External indexing and search engine services / EXTIDX-20 Search singular and plural words in French Change By: Espen Jervidalo Assignee: Espen Jervidalo Add Comment This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf) 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] (MGNLCE-60) Remove "too many open files" startup check - if possible thanks to H2
Title: Message Title Espen Jervidalo updated an issue Magnolia Community Edition / MGNLCE-60 Remove "too many open files" startup check - if possible thanks to H2 Change By: Espen Jervidalo Project: Magnolia Community Edition Key: MAGNOLIA MGNLCE - 6804 60 Security: Public Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 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] (MGNLWORKFLOW-339) Update Registries to new API
Title: Message Title Espen Jervidalo updated an issue Magnolia Workflow Module / MGNLWORKFLOW-339 Update Registries to new API Change By: Espen Jervidalo Release notes required: Yes Account: null (null) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 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] (PAGES-96) Magnolia saves the "position" attribute to newly added component
Title: Message Title Espen Jervidalo updated an issue Magnolia pages module / PAGES-96 Magnolia saves the "position" attribute to newly added component Change By: Espen Jervidalo Project: Magnolia pages module Key: MAGNOLIA PAGES - 6779 96 Security: Public Component/s: templating components Affects Version/s: 5.4.9 Affects Version/s: 5.4.9 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
[magnolia-dev] [JIRA] (PAGES-89) Consolidate display of edit-bars for inherited elements
Title: Message Title Espen Jervidalo updated an issue Magnolia pages module / PAGES-89 Consolidate display of edit-bars for inherited elements Change By: Espen Jervidalo Fix Version/s: 5.5 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 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] (MGNLWORKFLOW-339) Update Registries to new API
Title: Message Title Espen Jervidalo updated an issue Magnolia Workflow Module / MGNLWORKFLOW-339 Update Registries to new API Change By: Espen Jervidalo There are two registries (workflows and workitemhandlers) using the old, deprecated Registry-APIs and observation mechanisms. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 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] (MGNLWORKFLOW-339) Update Registries to new API
Title: Message Title Espen Jervidalo created an issue Magnolia Workflow Module / MGNLWORKFLOW-339 Update Registries to new API Issue Type: Improvement Assignee: Espen Jervidalo Created: 29/Sep/16 9:16 AM Fix Versions: 5.6 Priority: Neutral Reporter: Espen Jervidalo Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) For
[magnolia-dev] [JIRA] (MGNLWORKFLOW-338) Update jbpm to 6.4
Title: Message Title Espen Jervidalo updated an issue Magnolia Workflow Module / MGNLWORKFLOW-338 Update jbpm to 6.4 Change By: Espen Jervidalo Assignee: Espen Jervidalo Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 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] (MGNLWORKFLOW-338) Update jbpm to 6.4
Title: Message Title Espen Jervidalo created an issue Magnolia Workflow Module / MGNLWORKFLOW-338 Update jbpm to 6.4 Issue Type: Task Assignee: Unassigned Created: 27/Sep/16 11:30 AM Fix Versions: 5.6 Priority: Neutral Reporter: Espen Jervidalo Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
[magnolia-dev] [JIRA] (PAGES-89) Consolidate display of edit-bars for inherited elements
Title: Message Title Espen Jervidalo updated an issue Magnolia pages module / PAGES-89 Consolidate display of edit-bars for inherited elements Change By: Espen Jervidalo The display of inherited areas and components have changed due to various unrelated changes in the page-editor.IIRC inherited areas and components were always shown in the page-structure but annotated with 'inherited' on edit-bars and their actions were disabled.Looking at the code this changed in MAGNOLIA-5439: Now all of a sudden inherited areas are wiped from the structure, but leaving the components in, which causes several side-effects, e.g. components associated with the parent-page instead of an area and different display for inherited areas vs inherited components.This ended up crashing when PAGES-62 was introduced and blindly casting the parent of all components to MgnlArea. This was patched in a QA commit, which now consistently removes all inherited elements, but breaking the initial idea of still displaying those.Some more notes:- the 'inherited' annotation was former criticized for not being i18nable.. so maybe rather have some sort of icon for display.- Do we actually need to display the inherited once ones ? adding more noise to the page. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 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] (PAGES-89) Consolidate display of edit-bars for inherited elements
Title: Message Title Espen Jervidalo updated an issue Magnolia pages module / PAGES-89 Consolidate display of edit-bars for inherited elements Change By: Espen Jervidalo The display of inherited areas and components have changed due to various unrelated changes in the page-editor.IIRC inherited areas and components were always shown in the page-structure but annotated with 'inherited' on bar-widgets and their actions were disabled. Looking at the code this changed in MAGNOLIA-5439: Now all of a sudden inherited areas are wiped from the structure, but leaving the components in, which causes several side-effects, e.g. components associated with the parent-page instead of an area and different display for inherited areas vs inherited components .This ended up crashing when PAGES-62 was introduced and blindly casting the parent of all components to MgnlArea. This was patched in a QA commit, which now consistently removes all inherited elements, but breaking the initial idea of still displaying those.Some more notes:- the 'inherited' annotation was former criticized for not being i18nable.. so maybe rather have some sort of icon for disaplay display .- Do we actually need to display the inherited once? adding more noise to the page. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 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] (PAGES-89) Consolidate display of edit-bars for inherited elements
Title: Message Title Espen Jervidalo updated an issue Magnolia pages module / PAGES-89 Consolidate display of edit-bars for inherited elements Change By: Espen Jervidalo The display of inherited areas and components have changed due to various unrelated changes in the page-editor.IIRC inherited areas and components were always shown in the page-structure but annotated with 'inherited' on bar-widgets and their actions were disabled. Looking at the code this changed in MAGNOLIA-5439: Now all of a sudden inherited areas are wiped from the structure, but leaving the components in, which causes several side-effects, e.g. components associated with the parent-page instead of an area and different display for inherited areas vs inherited components.This ended up crashing when PAGES-62 was introduced and blindly casting the parent of all components to MgnlArea. This was patched in a QA commit, which now consistently removes all inherited elements, but breaking the initial idea of still displaying those.Some more notes:- the 'inherited' annotation was former criticized for not being i18nable.. so maybe rather have some sort of icon for display.- Do we actually need to display the inherited once? adding more noise to the page. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 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] (PAGES-89) Consolidate display of edit-bars for inherited elements
Title: Message Title Espen Jervidalo updated an issue Magnolia pages module / PAGES-89 Consolidate display of edit-bars for inherited elements Change By: Espen Jervidalo The display of inherited areas and components have changed due to various unrelated changes in the page-editor.IIRC inherited areas and components were always shown in the page-structure but annotated with 'inherited' on bar edit - widgets bars and their actions were disabled.Looking at the code this changed in MAGNOLIA-5439: Now all of a sudden inherited areas are wiped from the structure, but leaving the components in, which causes several side-effects, e.g. components associated with the parent-page instead of an area and different display for inherited areas vs inherited components.This ended up crashing when PAGES-62 was introduced and blindly casting the parent of all components to MgnlArea. This was patched in a QA commit, which now consistently removes all inherited elements, but breaking the initial idea of still displaying those.Some more notes:- the 'inherited' annotation was former criticized for not being i18nable.. so maybe rather have some sort of icon for display.- Do we actually need to display the inherited once? adding more noise to the page. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 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] (PAGES-89) Consolidate component-bar forinherited elements
Title: Message Title Espen Jervidalo created an issue Magnolia pages module / PAGES-89 Consolidate component-bar forinherited elements Issue Type: Improvement Assignee: Unassigned Created: 29/Aug/16 1:04 PM Fix Versions: 5.5 Priority: Neutral Reporter: Espen Jervidalo The display of inherited areas and components have changed due to various unrelated changes in the page-editor. IIRC inherited areas and components were always shown in the page-structure but annotated with 'inherited' on bar-widgets and their actions were disabled. Looking at the code this changed in MAGNOLIA-5439 : Now all of a sudden inherited areas are wiped from the structure, but leaving the components in, which causes several side-effects, e.g. components associated with the parent-page instead of an area. This ended up crashing when PAGES-62 was introduced and blindly casting the parent of all components to MgnlArea. This was patched in a QA commit, which now consistently removes all inherited elements, but breaking the initial idea of still displaying those. Some more notes: the 'inherited' annotation was former criticized for not being i18nable.. so maybe rather have some sort of icon for disaplay.
[magnolia-dev] [JIRA] (PAGES-89) Consolidate display of edit-bars for inherited elements
Title: Message Title Espen Jervidalo updated an issue Magnolia pages module / PAGES-89 Consolidate display of edit-bars for inherited elements Change By: Espen Jervidalo Summary: Consolidate component display of edit - bar forinherited bars for inherited elements Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 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-3998) Introduce a new vaadin widgetset for the enterprise-pro webapp
Title: Message Title Espen Jervidalo created an issue Magnolia UI / MGNLUI-3998 Introduce a new vaadin widgetset for the enterprise-pro webapp Issue Type: Improvement Assignee: Espen Jervidalo Components: widgetset-pro Created: 22/Aug/16 4:05 PM Fix Versions: 5.5 Priority: Neutral Reporter: Espen Jervidalo Security Level: Public Add Comment
[magnolia-dev] [JIRA] (PAGES-42) Introduce PagesContentConnector and ActionExecutor
Title: Message Title Espen Jervidalo reopened an issue Magnolia pages module / PAGES-42 Introduce PagesContentConnector and ActionExecutor Change By: Espen Jervidalo Resolution: Won't Do Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 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] (PAGES-54) Use GWT.create (or similar) for selected components in the page-editor-widget
Title: Message Title Espen Jervidalo updated an issue Magnolia pages module / PAGES-54 Use GWT.create (or similar) for selected components in the page-editor-widget Change By: Espen Jervidalo It should be possible to extend selected client-side GWT classes. *UPD* It's now possible to configure deferred bindings in Widgetsets inheriting from PagesWidgetSet and MagnoliaWidgetSet.There are some subtle hooks allowed by extending ComponentBar, AreaBar and ComponentPlaceHolder and overriding the selected methods. Keep in mind that extensions to the Widgetset tend to be expensive changes, and backward compatibility is not granted the same way as server-side components. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 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] (PAGES-54) Use GWT.create (or similar) for selected components in the page-editor-widget
Title: Message Title Espen Jervidalo updated an issue Magnolia pages module / PAGES-54 Use GWT.create (or similar) for selected components in the page-editor-widget Change By: Espen Jervidalo Assignee: Espen Jervidalo Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 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-3943) JcrContentConnector ignores node-name for JcrNewNodeItemId
Title: Message Title Espen Jervidalo updated an issue Magnolia UI / MGNLUI-3943 JcrContentConnector ignores node-name for JcrNewNodeItemId Change By: Espen Jervidalo Assignee: Espen Jervidalo Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 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-3943) JcrContentConnector ignores node-name for JcrNewNodeItemId
Title: Message Title Espen Jervidalo updated an issue Magnolia UI / MGNLUI-3943 JcrContentConnector ignores node-name for JcrNewNodeItemId Change By: Espen Jervidalo Fix Version/s: 5.4.8 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 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-3943) JcrContentConnector ignores node-name for JcrNewNodeItemId
Title: Message Title Espen Jervidalo created an issue Magnolia UI / MGNLUI-3943 JcrContentConnector ignores node-name for JcrNewNodeItemId Issue Type: Bug Affects Versions: 5.4.7 Assignee: Unassigned Created: 11/Jul/16 10:40 AM Fix Versions: 5.5 Priority: Neutral Reporter: Espen Jervidalo Security Level: Public Add Comment
[magnolia-dev] [JIRA] (PAGES-80) Adapt pages app to Content-Connector concept
Title: Message Title Espen Jervidalo updated an issue Magnolia pages module / PAGES-80 Adapt pages app to Content-Connector concept Change By: Espen Jervidalo The motivation is to further simplify the API and make the key-components JCR-agnostic. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 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] (PAGES-80) Adapt pages app to Content-Connector concept
Title: Message Title Espen Jervidalo created an issue Magnolia pages module / PAGES-80 Adapt pages app to Content-Connector concept Issue Type: Improvement Assignee: Espen Jervidalo Created: 05/Jul/16 9:47 AM Priority: Neutral Reporter: Espen Jervidalo Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 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] (PAGES-25) As an editor I want to edit like in Typo3 Neos, to have better usability.
Title: Message Title Espen Jervidalo updated an issue Magnolia pages module / PAGES-25 As an editor I want to edit like in Typo3 Neos, to have better usability. Change By: Espen Jervidalo Assignee: Espen Jervidalo Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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-17) Register the TaskEventDispatchers inside the task module
Title: Message Title Espen Jervidalo updated an issue Task Management / TASKMGMT-17 Register the TaskEventDispatchers inside the task module Change By: Espen Jervidalo Story Points: 3 Account: Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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-3384) Remove Task Event related code from AdminCentral
Title: Message Title Espen Jervidalo updated an issue Magnolia UI / MGNLUI-3384 Remove Task Event related code from AdminCentral Change By: Espen Jervidalo Story Points: 5 Account: Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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-17) Register the TaskEventDispatchers inside the task module
Title: Message Title Espen Jervidalo updated an issue Task Management / TASKMGMT-17 Register the TaskEventDispatchers inside the task module Change By: Espen Jervidalo Labels: awl Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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-3384) Remove Task Event related code from AdminCentral
Title: Message Title Espen Jervidalo updated an issue Magnolia UI / MGNLUI-3384 Remove Task Event related code from AdminCentral Change By: Espen Jervidalo Labels: awl cleanup improvement Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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-3903) Task bulk-actions should only be archivable when completed
Title: Message Title Espen Jervidalo updated an issue Magnolia UI / MGNLUI-3903 Task bulk-actions should only be archivable when completed Change By: Espen Jervidalo Labels: awl Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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-1) Extract task related classes from ui project
Title: Message Title Espen Jervidalo updated an issue Task Management / TASKMGMT-1 Extract task related classes from ui project Change By: Espen Jervidalo Assignee: Espen Jervidalo Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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-1) Extract task related classes from ui project
Title: Message Title Espen Jervidalo updated an issue Task Management / TASKMGMT-1 Extract task related classes from ui project Change By: Espen Jervidalo Assignee: Espen Jervidalo Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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-1) Extract task related classes from ui project
Title: Message Title Espen Jervidalo updated an issue Task Management / TASKMGMT-1 Extract task related classes from ui project Change By: Espen Jervidalo Labels: awl usertask Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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-1) Extract task related classes from ui project
Title: Message Title Espen Jervidalo updated an issue Task Management / TASKMGMT-1 Extract task related classes from ui project Change By: Espen Jervidalo Labels: awl usertask Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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-3903) Task bulk-actions should only be archivable when completed
Title: Message Title Espen Jervidalo created an issue Magnolia UI / MGNLUI-3903 Task bulk-actions should only be archivable when completed Issue Type: Bug Affects Versions: 5.5 Assignee: Unassigned Created: 01/Jun/16 5:29 PM Fix Versions: 5.5 Priority: Neutral Reporter: Espen Jervidalo Security Level: Public You can currently bulk-archive tasks in the drop-down in pulse in all statuses. This is wrong, as it won't affect the underlying jbpm-process and work-items. Abort might be a viable solution, plus the ability to bulk-archive the aborted tasks.
[magnolia-dev] [JIRA] (MGNLUI-3902) Task availability rule logs null warning
Title: Message Title
Espen Jervidalo updated an issue
Magnolia UI / MGNLUI-3902
Task availability rule logs null warning
Change By:
Espen Jervidalo
The refactoring done in Pulse to enable bulk-actions creates causes the following warning, when e.g. switching from the list to the detail view of a task, due to the selected item being nulled:{{WARN ulse.task.action.availability.TaskAvailabilityRule: Got a null task. Availability rule will return false}}
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
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-3902) Task availability rule logs null warning
Title: Message Title
Espen Jervidalo updated an issue
Magnolia UI / MGNLUI-3902
Task availability rule logs null warning
Change By:
Espen Jervidalo
The refactoring done in Pulse to enable bulk-actions creates the following warning, when e.g. switching from the list to the detail view of a task, due to the selected item being nulled:{{ WARN ulse.task.action.availability.TaskAvailabilityRule: Got a null task. Availability rule will return false }}
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
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-3902) Task availability rule logs null warning
Title: Message Title
Espen Jervidalo created an issue
Magnolia UI / MGNLUI-3902
Task availability rule logs null warning
Issue Type:
Bug
Affects Versions:
5.5
Assignee:
Unassigned
Created:
01/Jun/16 4:59 PM
Fix Versions:
5.5
Priority:
Neutral
Reporter:
Espen Jervidalo
Security Level:
Public
The refactoring done in Pulse to enable bulk-actions creates the following warning, when e.g. switching from the list to the detail view of a task, due to the selected item being nulled: {{ WARN ulse.task.action.availability.TaskAvailabilityRule: Got a null task. Availability rule will return false }}
[magnolia-dev] [JIRA] (MGNLSITE-54) Site Prototype in YAML
Title: Message Title
Espen Jervidalo updated an issue
Magnolia Site Module / MGNLSITE-54
Site Prototype in YAML
Change By:
Espen Jervidalo
*UPD:*After discussions with [~mgeljic] and [~had] it was decided to postpone this ticket. Short summary:- the visibility of the prototype is undefined as it needs to be hidden in one place, and implicitly (null-valued) visible in the other. The visibility of templates is already quirky as is. (more on the PR)- introducing {{PageTemplateDefinition}} in the site-module is a bargain. Can't go further up, due to dependencies to {{ResourceDefintitions}}. Introducing a marker class in core and a {{SiteAwarePageTemplateDef}} is not any better.- The class hierarchy with {{PageTemplateDefinition}} subclassed by {{PrototypeDefinition}} is arguable. Could also be the other way around. - We might consider decoration for the prototype? That way, whenever you retrieve a page-template from the registry, it would be decorated by the prototype and we would not need to manually merge it in the renderer. That would probably also allow using primitive types on the page-template (e.g. visible). - *Original description:*So that a dev using light development can have all their main configuration in yaml files - it must be possible to specify the site prototype in YAML.Implement what is decided upon based on the concept.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use
[magnolia-dev] [JIRA] (MGNLSITE-54) Site Prototype in YAML
Title: Message Title
Espen Jervidalo updated an issue
Magnolia Site Module / MGNLSITE-54
Site Prototype in YAML
Change By:
Espen Jervidalo
* UPD: * After discussion with [~mgeljic] and [~had] it was decided to postpone this ticket. Short summary:- the visibility of the prototype is undefined as it needs to be hidden in one place, and implicitly (null-valued) visible in the other. The visibility of templates is already quirky as is. (more on the PR)- introducing {{ PageTemplateDefinition }} in the site-module is a bargain. Can't go further up, due to dependencies to {{ ResourceDefintitions }} . Introducing a marker class in core and a {{ SiteAwarePageTemplateDef }} is not any better.- The class hierarchy with {{ PageTemplateDefinition subclassed by {{ PrototypeDefinition }} is arguable. Could also be the other way around.We might consider decoration for the prototype? That way, whenever you retrieve a page-template from the registry, it would be decorated by the prototype and we would not need to manually merge it in the renderer. That would probably also allow using primitive types on the page-template (e.g. visible). * Original description: * So that a dev using light development can have all their main configuration in yaml files - it must be possible to specify the site prototype in YAML.Implement what is decided upon based on the concept.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.htm
[magnolia-dev] [JIRA] (MGNLSITE-54) Site Prototype in YAML
Title: Message Title
Espen Jervidalo updated an issue
Magnolia Site Module / MGNLSITE-54
Site Prototype in YAML
Change By:
Espen Jervidalo
*UPD:*After discussion with [~mgeljic] and [~had] it was decided to postpone this ticket. Short summary:- the visibility of the prototype is undefined as it needs to be hidden in one place, and implicitly (null-valued) visible in the other. The visibility of templates is already quirky as is. (more on the PR)- introducing {{PageTemplateDefinition}} in the site-module is a bargain. Can't go further up, due to dependencies to {{ResourceDefintitions}}. Introducing a marker class in core and a {{SiteAwarePageTemplateDef}} is not any better.- The class hierarchy with {{PageTemplateDefinition }} subclassed by {{PrototypeDefinition}} is arguable. Could also be the other way around.We might consider decoration for the prototype? That way, whenever you retrieve a page-template from the registry, it would be decorated by the prototype and we would not need to manually merge it in the renderer. That would probably also allow using primitive types on the page-template (e.g. visible).*Original description:*So that a dev using light development can have all their main configuration in yaml files - it must be possible to specify the site prototype in YAML.Implement what is decided upon based on the concept.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our f
[magnolia-dev] [JIRA] (MGNLSITE-54) Site Prototype in YAML
Title: Message Title
Espen Jervidalo updated an issue
Magnolia Site Module / MGNLSITE-54
Site Prototype in YAML
Change By:
Espen Jervidalo
*UPD:*After discussion discussions with [~mgeljic] and [~had] it was decided to postpone this ticket. Short summary:- the visibility of the prototype is undefined as it needs to be hidden in one place, and implicitly (null-valued) visible in the other. The visibility of templates is already quirky as is. (more on the PR)- introducing {{PageTemplateDefinition}} in the site-module is a bargain. Can't go further up, due to dependencies to {{ResourceDefintitions}}. Introducing a marker class in core and a {{SiteAwarePageTemplateDef}} is not any better.- The class hierarchy with {{PageTemplateDefinition}} subclassed by {{PrototypeDefinition}} is arguable. Could also be the other way around.We might consider decoration for the prototype? That way, whenever you retrieve a page-template from the registry, it would be decorated by the prototype and we would not need to manually merge it in the renderer. That would probably also allow using primitive types on the page-template (e.g. visible).*Original description:*So that a dev using light development can have all their main configuration in yaml files - it must be possible to specify the site prototype in YAML.Implement what is decided upon based on the concept.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternative
[magnolia-dev] [JIRA] (MGNLSITE-54) Site Prototype in YAML
Title: Message Title Espen Jervidalo updated an issue Magnolia Site Module / MGNLSITE-54 Site Prototype in YAML Change By: Espen Jervidalo UPD:After discussion with [~mgeljic] and [~had] it was decided to postpone this ticket. Short summary:- the visibility of the prototype is undefined as it needs to be hidden in one place, and implicitly (null-valued) visible in the other. The visibility of templates is already quirky as is. (more on the PR)- introducing PageTemplateDefinition in the site-module is a bargain. Can't go further up, due to dependencies to ResourceDefintitions. Introducing a marker class in core and a SiteAwarePageTemplateDef is not any better.- The class hierarchy with PageTemplateDefinition subclassed by PrototypeDefinition is arguable. Could also be the other way around.We might consider decoration for the prototype? That way, whenever you retrieve a page-template from the registry, it would be decorated by the prototype and we would not need to manually merge it in the renderer. That would probably also allow using primitive types on the page-template (e.g. visible).Original description: So that a dev using light development can have all their main configuration in yaml files - it must be possible to specify the site prototype in YAML.Implement what is decided upon based on the concept. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magno
[magnolia-dev] [JIRA] (BLOSSOM-237) Adapt to new API in 5.4.7
Title: Message Title
Espen Jervidalo updated an issue
Magnolia Blossom Module / BLOSSOM-237
Adapt to new API in 5.4.7
Change By:
Espen Jervidalo
Adapt to changes introduced in DefinitionProvider and TranslationService.Setting the modification-date to current-time as blossom creates the the definitions on the fly. So decorators should be re-applied on every request IMO.The new decoration-concept is not yet adopted in blossom. This is more of a work-around and for future iterations one might consider to deprecate the {{@PreRegister}} functionality in favor of a decoration mechanism . See linked ticket.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
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] (BLOSSOM-237) Adapt to new API in 5.4.7
Title: Message Title
Espen Jervidalo updated an issue
Magnolia Blossom Module / BLOSSOM-237
Adapt to new API in 5.4.7
Change By:
Espen Jervidalo
Adapt to changes introduced in DefinitionProvider and TranslationService. Setting the modification-date to current-time as blossom creates the the definitions on the fly. So decorators should be re-applied on every request IMO.The new decoration-concept is not yet adopted in blossom. This is more of a work-around and for future iterations one might consider to deprecate the {{@PreRegister}} functionality in favor of a decoration mechanism.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
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] (BLOSSOM-237) Adapt to new API in 5.4.7
Title: Message Title Espen Jervidalo created an issue Magnolia Blossom Module / BLOSSOM-237 Adapt to new API in 5.4.7 Issue Type: Task Assignee: Espen Jervidalo Created: 25/May/16 2:04 PM Fix Versions: 3.1.4 Priority: Neutral Reporter: Espen Jervidalo Adapt to changes introduced in DefinitionProvider and TranslationService. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
[magnolia-dev] [JIRA] (BLOSSOM-237) Adapt to new API in 5.4.7
Title: Message Title Espen Jervidalo updated an issue Magnolia Blossom Module / BLOSSOM-237 Adapt to new API in 5.4.7 Change By: Espen Jervidalo Affects Version/s: 3.1.3 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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-3875) Failing tests with Java 8
Title: Message Title Espen Jervidalo updated an issue Magnolia UI / MGNLUI-3875 Failing tests with Java 8 Change By: Espen Jervidalo Assignee: Maxime Michel Espen Jervidalo Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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-2689) Remove legacy Log4j page
Title: Message Title Espen Jervidalo updated an issue Magnolia UI / MGNLUI-2689 Remove legacy Log4j page Change By: Espen Jervidalo Summary: Migrate Remove legacy Log4j page to new UI Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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] (LMPLUGIN-8) Allow reading the npm auth-token from .npmrc
Title: Message Title
Espen Jervidalo updated an issue
Magnolia Light Module Maven Plugin / LMPLUGIN-8
Allow reading the npm auth-token from .npmrc
Change By:
Espen Jervidalo
Even after the final release of nexus3 it seems the user-token authentication used in nexus2 does not seem to work properly or the realm has changed. Either way adding the possibility to use the npm Bearer token is a legit use case, so you can use the generated '.npmrc' file for obtaining the auth token generated by:{code}npm login --registry=https://npm.magnolia-cms.com/repository/npm-internal / {code} Note: the tailing '/' is important. Otherwise it will add an entry with 'https://npm.magnolia-cms.com/repository' in .npmrc. Weird.. Reference:http://blog.npmjs.org/post/118393368555/deploying-with-npm-private-moduleshttps://books.sonatype.com/nexus-book/reference/usertoken.html (nexus 2)https://books.sonatype.com/nexus-book/3.0/reference/security.html#realms (nexus 3)
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
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] (LMPLUGIN-8) Allow reading the npm auth-token from .npmrc
Title: Message Title
Espen Jervidalo updated an issue
Magnolia Light Module Maven Plugin / LMPLUGIN-8
Allow reading the npm auth-token from .npmrc
Change By:
Espen Jervidalo
Even after the final release of nexus3 it seems the user-token authentication used in nexus2 does not seem to work properly or the realm has changed. Either way adding the possibility to use the npm Bearer token is a legit use case, so you can use the generated '.npmrc' file for obtaining the auth token generated by:{code}npm login --registry=https://npm.magnolia-cms.com/repository/npm-internal{code}Reference: http://blog.npmjs.org/post/118393368555/deploying-with-npm-private-modules https://books.sonatype.com/nexus-book/reference/usertoken.html (nexus 2)https://books.sonatype.com/nexus-book/3.0/reference/security.html#realms (nexus 3)
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
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] (LMPLUGIN-8) Allow reading the npm auth-token from .npmrc
Title: Message Title
Espen Jervidalo updated an issue
Magnolia Light Module Maven Plugin / LMPLUGIN-8
Allow reading the npm auth-token from .npmrc
Change By:
Espen Jervidalo
Even after the final release of nexus3 it seems the user-token authentication used in nexus2 does not seem to work properly or the realm has changed. Either way adding the possibility to use the npm Bearer token is a legit use case, so you can use the generated '.npmrc' file for obtaining the auth token generated by:{code}npm login --registry=https://npm.magnolia-cms.com/repository/npm-internal{code} Reference:https://books.sonatype.com/nexus-book/reference/usertoken.html (nexus 2)https://books.sonatype.com/nexus-book/3.0/reference/security.html#realms (nexus 3)
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
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] (LMPLUGIN-8) Allow reading the npm auth-token from .npmrc
Title: Message Title
Espen Jervidalo updated an issue
Magnolia Light Module Maven Plugin / LMPLUGIN-8
Allow reading the npm auth-token from .npmrc
Change By:
Espen Jervidalo
Even after the final release of nexus3 it seems the user-token authentication used in nexus2 does not seem to work properly or the realm has changes. Either way adding the possibility to use the npm Bearer token is a legit use case, so you can use the generated '.npmrc' file for obtaining the auth token generated by:{code}npm login --registry=https://npm.magnolia-cms.com/repository/npm-internal{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
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] (LMPLUGIN-8) Allow reading the npm auth-token from .npmrc
Title: Message Title
Espen Jervidalo updated an issue
Magnolia Light Module Maven Plugin / LMPLUGIN-8
Allow reading the npm auth-token from .npmrc
Change By:
Espen Jervidalo
Even after the final release of nexus3 it seems the user-token authentication used in nexus2 does not seem to work properly or the realm has changes changed . Either way adding the possibility to use the npm Bearer token is a legit use case, so you can use the generated '.npmrc' file for obtaining the auth token generated by:{code}npm login --registry=https://npm.magnolia-cms.com/repository/npm-internal{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
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] (LMPLUGIN-8) Allow reading the npm auth-token from .npmrc
Title: Message Title Espen Jervidalo created an issue Magnolia Light Module Maven Plugin / LMPLUGIN-8 Allow reading the npm auth-token from .npmrc Issue Type: New Feature Affects Versions: 1.0 Assignee: Espen Jervidalo Created: 22/Apr/16 11:06 AM Fix Versions: 1.0.1 Priority: Neutral Reporter: Espen Jervidalo Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
[magnolia-dev] [JIRA] (LMPLUGIN-7) Add dist-tags to json-request to point to latest version
Title: Message Title Espen Jervidalo updated an issue Magnolia Light Module Maven Plugin / LMPLUGIN-7 Add dist-tags to json-request to point to latest version Change By: Espen Jervidalo Fix Version/s: 1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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] (LMPLUGIN-4) Extracted npm packages should end up in 'package'-directory
Title: Message Title Espen Jervidalo updated an issue Magnolia Light Module Maven Plugin / LMPLUGIN-4 Extracted npm packages should end up in 'package'-directory Change By: Espen Jervidalo Fix Version/s: 1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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] (LMPLUGIN-1) Implement maven-plugin for the automated creation and deployment of light-modules from magnolia modules
Title: Message Title Espen Jervidalo updated an issue Magnolia Light Module Maven Plugin / LMPLUGIN-1 Implement maven-plugin for the automated creation and deployment of light-modules from magnolia modules Change By: Espen Jervidalo Fix Version/s: 1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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] (LMPLUGIN-2) Versioning and deployment for SNAPSHOT and FINAL versions
Title: Message Title Espen Jervidalo updated an issue Magnolia Light Module Maven Plugin / LMPLUGIN-2 Versioning and deployment for SNAPSHOT and FINAL versions Change By: Espen Jervidalo Fix Version/s: 1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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] (LMPLUGIN-5) Generated light-modules should be scoped 'magnolia'
Title: Message Title Espen Jervidalo updated an issue Magnolia Light Module Maven Plugin / LMPLUGIN-5 Generated light-modules should be scoped 'magnolia' Change By: Espen Jervidalo Fix Version/s: 1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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] (LMPLUGIN-3) Add possibility to pass auth method and token for the npm repository
Title: Message Title Espen Jervidalo updated an issue Magnolia Light Module Maven Plugin / LMPLUGIN-3 Add possibility to pass auth method and token for the npm repository Change By: Espen Jervidalo Fix Version/s: 1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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] (MGNLWORKFLOW-328) Allow assigning actor and groups per path and workspace in publication
Title: Message Title
Espen Jervidalo updated an issue
Magnolia Workflow Module / MGNLWORKFLOW-328
Allow assigning actor and groups per path and workspace in publication
Change By:
Espen Jervidalo
It's currently possible to launch different workflows based on the path of the content to be published. This is called workflow-mappings: https://documentation.magnolia-cms.com/display/DOCS/Workflow+processes#Workflowprocesses-WorkflowmappingsAnother nice addition would be to allow assigning different actors and groups based on workspace and path of the content , e.g. :All publications of content in pages workspace should be assigned to groupA. All content underneath /home/news should be assigned to group-news and all assets to group-assets.The assignees of a task are determined in {{info.magnolia.module.workflow.jbpm.humantask.parameter.PublicationTaskParameterResolver#setTaskParameters}} for publication.The definition should be extended to allow this to be configured and while at it, it should be parameterized in the implementation.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
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] (MGNLWORKFLOW-328) Allow assigning actor and groups per path and workspace in publication
Title: Message Title Espen Jervidalo updated an issue Magnolia Workflow Module / MGNLWORKFLOW-328 Allow assigning actor and groups per path and workspace in publication Change By: Espen Jervidalo Summary: Allow assigning actor and groups per path and workspace in publication Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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] (MGNLWORKFLOW-328) Allow assigning actor and groups per path in publication
Title: Message Title Espen Jervidalo created an issue Magnolia Workflow Module / MGNLWORKFLOW-328 Allow assigning actor and groups per path in publication Issue Type: New Feature Affects Versions: 5.5.1 Assignee: Unassigned Created: 30/Mar/16 1:05 PM Fix Versions: 5.5.2 Priority: Neutral Reporter: Espen Jervidalo It's currently possible to launch different workflows based on the path of the content to be published. This is called workflow-mappings: https://documentation.magnolia-cms.com/display/DOCS/Workflow+processes#Workflowprocesses-Workflowmappings Another nice addition would be to allow assigning different actors and groups based on workspace and path of the content: All publications of content in pages workspace should be assigned to groupA. All content underneath /home/news should be assigned to group-news and all assets to group-assets. The assignees of a task are determined in info.magnolia.module.workflow.jbpm.humantask.parameter.PublicationTaskParameterResolver#setTaskParameters for publication. The definition should be extended to allow this to be configured and while at it, it should be parameterized in the implementation.
[magnolia-dev] [JIRA] (LMPLUGIN-7) Add dist-tags to json-request to point to latest version
Title: Message Title Espen Jervidalo updated an issue Magnolia Light Module Maven Plugin / LMPLUGIN-7 Add dist-tags to json-request to point to latest version Change By: Espen Jervidalo Sprint: Basel 36 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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] (LMPLUGIN-7) Add dist-tags to json-request to point to latest version
Title: Message Title Espen Jervidalo updated an issue Magnolia Light Module Maven Plugin / LMPLUGIN-7 Add dist-tags to json-request to point to latest version Change By: Espen Jervidalo npm expects a dist-tags property for resolving the latest version. Leaving it out lead to failing builds when trying to resolve e.g. "@magnolia/mtk" : "latest" Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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] (LMPLUGIN-7) Add dist-tags to json-request to point to latest version
Title: Message Title Espen Jervidalo created an issue Magnolia Light Module Maven Plugin / LMPLUGIN-7 Add dist-tags to json-request to point to latest version Issue Type: Bug Assignee: Espen Jervidalo Created: 25/Mar/16 1:12 PM Priority: Neutral Reporter: Espen Jervidalo Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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] (MTE-78) Integrate light-module-maven-plugin into templating kit
Title: Message Title Espen Jervidalo updated an issue Magnolia Templating Essentials / MTE-78 Integrate light-module-maven-plugin into templating kit Change By: Espen Jervidalo The plugin will take care of auto-generating the npm package during 'generate-resource' phase and deploy it to nexus during 'deploy' phase. This has been manually tested with the attached patch.Some open questions:- There's no way to re-deploy SNAPSHOT versions. Once it's deployed to nexus, we have to manually DELETE the whole package (including all versions). No-go for production, but for testing we don't mind. How to solve it is not yet decided. (fixed in LMPLUGIN-2) - We should test it during release (staging). That's the fall-back solution if we can't solve the SNAPSHOT issue. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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] (MTE-78) Integrate light-module-maven-plugin into templating kit
Title: Message Title Espen Jervidalo updated an issue Magnolia Templating Essentials / MTE-78 Integrate light-module-maven-plugin into templating kit Change By: Espen Jervidalo Sprint: Basel 36 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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] (MTE-78) Integrate light-module-maven-plugin into templating kit
Title: Message Title Espen Jervidalo updated an issue Magnolia Templating Essentials / MTE-78 Integrate light-module-maven-plugin into templating kit Change By: Espen Jervidalo Assignee: Espen Jervidalo Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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] (MGNLWORKFLOW-327) CommandWorkItemHandler works only with commands inside the default catalog
Title: Message Title Espen Jervidalo created an issue Magnolia Workflow Module / MGNLWORKFLOW-327 CommandWorkItemHandler works only with commands inside the default catalog Issue Type: Bug Affects Versions: 5.5.1 Assignee: Unassigned Created: 23/Mar/16 2:37 PM Fix Versions: 5.5.2 Priority: Neutral Reporter: Espen Jervidalo CommandWorkItemHandler doesn't read the passed commandCatalog. Add Comment
[magnolia-dev] [JIRA] (MTE-78) Integrate light-module-maven-plugin into templating kit
Title: Message Title Espen Jervidalo updated an issue Magnolia Templating Essentials / MTE-78 Integrate light-module-maven-plugin into templating kit Change By: Espen Jervidalo The plugin will take care of auto-generating the npm package during 'generate-resource' phase and deploy it to nexus during 'deploy' phase. This has been manually tested with the attached patch.Some open questions:- There's no way to re-deploy SNAPSHOT versions. Once it's deployed to nexus, we have to manually DELETE the whole package (including all versions). No-go for production, but for testing we don't mind. How to solve it is not yet decided. (fixed in LMPLUGIN-2) - We should test it during release (staging). That's the fall-back solution if we can't solve the SNAPSHOT issue. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 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-3810) Pulse hides new tasks created by current user
Title: Message Title
Espen Jervidalo updated an issue
Magnolia UI / MGNLUI-3810
Pulse hides new tasks created by current user
Change By:
Espen Jervidalo
To reproduce with STK demo:* assign demo-project-editors role to peter* become peter* publish /demo-project* you should find the pulse badge not increased and no new task visible in there. It gets refreshed only manually, e.g. if you forth/back switch tabs within Pulse. Update:The problem is that the {{LocalTaskDispatcherManager#getAllRecipients}} doesn't seem to resolve groups transitively.So peter is member of 'demo-project-publisher' and transitively member of 'publisher' group: He should receive the task-event.The reason why this works in the new demo is because the group was set up wrong in the first place. 'travel-demo-publisher' is not part of 'publisher' group but the publish-task is assigned to both groups. That's why it works there. The transitive group-member is working correctly when it's not triggered by the event, so it's implemented correctly there. This might help: {{TasksStoreImpl#findPendingTasksByUser}} or {{GroupManager#getAllGroups(java.lang.String)}}See attached screenshots.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
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:
