[magnolia-dev] [JIRA] (DOCU-896) Refine YAML page

[JIRA (on behalf of Christoph Meier)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-896  
 
 
  Refine YAML page   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 

  
 
 
 
 

 
 2 major aims*Mention YAML as bootstrap format*Since YAML with _"Provide JCR bootstraps as YAML (too)"_ - YAML no longer limited to use for definition items only. This must be reflected on the YAML page.E.g. adapt the section "YAML in the context of Magnolia"*Add more sophisticated examples ...*.. for YAML as item definition language. The page just covers the very basic.  Let's add a few more sophisticated things, such as:- Reusing existing maps when defining a new one using {{>>}}-- here we may also mention the down sides which may appear when decorating- etc. pp  Since YAML with "Provide JCR bootstraps as YAML (too)" - YAML no longer limited to use for definition items only Check links, etc .  This must be reflected on the YAML page.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list 

[magnolia-dev] [JIRA] (MGNLCACHE-179) Request Header

[JIRA (on behalf of Franco Minella)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Franco Minella created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Cache Module /  MGNLCACHE-179  
 
 
  Request Header   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 5.4.7  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 image-2017-05-11-17-46-27-422.png  
 
 
Components: 
 browser cache, ehcache  
 
 
Created: 
 11/May/17 5:53 PM  
 
 
Environment: 
 Windows Server 2008 R2 Standard  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Franco Minella  
 

  
 
 
 
 

 
 Hi,  how can I say to magnolia to dont't cache headers on the request on a specific page? On the image, our configuration.   Is our configuration in the wrong place? PS: we have few time until releasing on live environment, so I hope that someone can help me quickly. Thank you. PS2: we work with 5.4.9, but the form don't allow to select that version. Regards  
 

  
 
 
 
 

 
 
 

 
  

[magnolia-dev] [JIRA] (MGNLUI-3650) Extract the icon-font to its own project (and build)

[on behalf of Mikaël Geljić]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mikaël Geljić updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3650  
 
 
  Extract the icon-font to its own project (and build)   
 

  
 
 
 
 

 
Change By: 
 Mikaël Geljić  
 
 
Summary: 
 Extract the icon-font to its own project  (  and build )  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLUI-3650) Extract the icon-font to its own project and build

[on behalf of Michael Mühlebach]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3650  
 
 
  Extract the icon-font to its own project and build   
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Sprint: 
 Basel 96  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLDEMO-212) Move Travel Demo template labels into a separate message bundle

[JIRA (on behalf of Antti Hietala)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Antti Hietala updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Demo Projects /  MGNLDEMO-212  
 
 
  Move Travel Demo template labels into a separate message bundle   
 

  
 
 
 
 

 
Change By: 
 Antti Hietala  
 
 
Labels: 
 blocked  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLUI-3650) Extract the icon-font to its own project and build

[on behalf of Mikaël Geljić]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mikaël Geljić updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3650  
 
 
  Extract the icon-font to its own project and build   
 

  
 
 
 
 

 
 Great; now that the icon-font was copy-pasted into several other locations for the redesign of installation and related screens, it becomes pointless to update the font manually in all of these, so the extraction is now a prerequisite. 
 
main/magnolia-core/src/main/resources/installation/resources/fonts 
ui/magnolia-ui-vaadin-theme/src/main/resources/VAADIN/themes/magnolia/fonts (used to be the one and only) 
ce-packs/magnolia-community-demo-bundle/src/release/tomcat/webapps/ROOT/fonts 
ce-packs/magnolia-community-demo-bundle/src/release/tomcat/webapps/magnoliaPublic/fonts 
ee-packs/magnolia-enterprise-pro-demo-bundle/src/release/tomcat/webapps/ROOT/fonts 
ee-packs/magnolia-enterprise-pro-demo-bundle/src/release/tomcat/webapps/magnoliaPublic/fonts 
ee-packs/magnolia-enterprise-pro-stk-bundle/src/release/tomcat/webapps/ROOT/fonts 
ee-packs/magnolia-enterprise-pro-stk-bundle/src/release/tomcat/webapps/magnoliaPublic/fonts 
 Even if we don't generate the font automatically, a first step is anyway extraction to its own repo and maven artifact—which will eventually be upstream from both main and UI. For bundles, extraction must be done with maven.  
 

  
 
 
 
 

 
Change By: 
 Mikaël Geljić  
 
 
Story Points: 
 5  
 
 
Priority: 
 Neutral Major  
 
 
Labels: 
 icomoon icon icon-font  to-estimate  
 

  
 
 
 
 

 

[magnolia-dev] [JIRA] (DOCU-896) Improve YAML page

[JIRA (on behalf of Christoph Meier)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-896  
 
 
  Improve YAML page   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 

  
 
 
 
 

 
 The page just covers the very basic.  Let's  adda  add a  few more sophisticated things, such as:- Reusing existing maps when defining a new one using {{>>}}-- here we may also mention the down sides which may appear when decorating- etc. pp  Since YAML with "Provide JCR bootstraps as YAML (too)" - YAML no longer limited to use for definition items only. This must be reflected on the YAML page.  
 

  
 
 
 
 

 
 
 

 
 
 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-896) Refine YAML page

[JIRA (on behalf of Christoph Meier)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-896  
 
 
  Refine YAML page   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 
 
Summary: 
 Improve Refine  YAML page  
 

  
 
 
 
 

 
 
 

 
 
 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] (SUGGEST-83) Prompt editor to publish page assets at same time as publishing page

[JIRA (on behalf of Ben Price)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ben Price created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Suggestion Box /  SUGGEST-83  
 
 
  Prompt editor to publish page assets at same time as publishing page   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 11/May/17 3:04 PM  
 
 
Environment: 

 
 
Labels: 
 collector-0cf1239d  
 
 
Reporter: 
 Ben Price  
 

  
 
 
 
 

 
 When an editor publishes a page (especially new pages), there are nearly always assets which need publishing too. Very often, the page is published, only for the user to then see that assets are not displayed on the public page. oops! The editor has to then go back in to the DAM and publish each asset in turn, once they've found them, that is. It would be really helpful and save time, if upon publishing a page, there could be a prompt which notifies the editor if attempting to publish a page, within which are unpublished assets e.g. "This page contains unpublished assets, do you wish to publish these too?" And then maybe offer check boxes to select which of the page's assets can be published at the same time as the page.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
   

[magnolia-dev] [JIRA] (MGNLCACHE-178) Incorrect location of the ehcache3 directory

[on behalf of Roman Kovařík]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Roman Kovařík updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Cache Module /  MGNLCACHE-178  
 
 
  Incorrect location of the ehcache3 directory   
 

  
 
 
 
 

 
Change By: 
 Roman Kovařík  
 

  
 
 
 
 

 
 {{magnolia-ee-test-webapp-5.5.4-SNAPSHOT/cache/--Users/romankovarik/projects/master/ee/magnolia-ee-integration-tests/magnolia-ee-test-webapp/target/magnolia-ee-test-webapp-5.5.4-SNAPSHOT--/file/}}*  {{info.magnolia.module.cache.ehcache3.EhCache3Factory#EhCache3Factory}}*  Moreover the usage of the cache manager id directory seems redundant since an ID is part of the folder name ({{defaultPageCache_2be127d2b81becfaaa14322fdad4d84df2ca4c9f}})...collision of multiple webapps to be checked.* Also {{info.magnolia.cms.core.Path#getCacheDirectoryPath}} is deprecated on 5.5 branch, we should consider resolving the cache directory on our own  or just add a default into the factory and drop {{magnolia . cache.startdir}}.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For 

[magnolia-dev] [JIRA] (MGNLCACHE-178) Incorrect location of the ehcache3 directory

[on behalf of Roman Kovařík]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Roman Kovařík created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Cache Module /  MGNLCACHE-178  
 
 
  Incorrect location of the ehcache3 directory   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 5.5.4  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 ehcache3  
 
 
Created: 
 11/May/17 3:00 PM  
 
 
Fix Versions: 
 5.5.5  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Roman Kovařík  
 

  
 
 
 
 

 
 magnolia-ee-test-webapp-5.5.4-SNAPSHOT/cache/-Users/romankovarik/projects/master/ee/magnolia-ee-integration-tests/magnolia-ee-test-webapp/target/magnolia-ee-test-webapp-5.5.4-SNAPSHOT-/file/ 
 
Moreover the usage of the cache manager id directory seems redundant since an ID is part of the folder name (defaultPageCache_2be127d2b81becfaaa14322fdad4d84df2ca4c9f)...collision of multiple webapps to be checked. 
Also info.magnolia.cms.core.Path#getCacheDirectoryPath is deprecated on 5.5 branch, we should consider resolving the cache directory on our own. 
  
 

  
 
 
 
 

 
 
 

[magnolia-dev] [JIRA] (DOCU-1018) Polish and refine pages concerning bootstrapping and import / export JCR data

[JIRA (on behalf of Christoph Meier)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-1018  
 
 
  Polish and refine pages concerning bootstrapping and import / export JCR data   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 

  
 
 
 
 

 
 This ticket is a follow-up which arose during tackling DOCU-1016 (Reflect "JCR Export improvements").h4. Polish and refine pages concerning bootstrapping and import / export JCR dataReasons:- The page "Importing and exporting JCR data" was a big mingle-mangle concerning many different types of importing and exporting data - not only related to JCR-export-import.- Clearly distinct between -- Download YAML definition (to create YAML based definition items to be used in light modules).-- Export / import JCR data - bootstrapping - with both (XML and) YAML filesWhile working on DOCU-1016, i have decided to split up the mingle-mangle page - at least on the {{DOCS}} space so far.(So, as an exception, the ticket describes in retrospect what has be done.This allows to figure out later what we have changed and reflects our work).*New structure:*_Importing and exporting data_ (basically only a parent page with links to children)- _Importing and exporting JCR data for bootstrapping_ -- _Bootstrapping in Maven modules_ (moved)-- _Bootstrapping in light modules_ (moved)- _Downloading YAML definition_- _Importing and exporting data for the Content Translation app_- _Importing ZIP files with the Assets app_* Deleted Remove :*- Bootsrapping- Importing and exporting JCR data  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA 

[magnolia-dev] [JIRA] (MGNLMAIL-66) Implement OAuth 2.0 authentication

[on behalf of Robert Šiška]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert Šiška updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Mail Module /  MGNLMAIL-66  
 
 
  Implement OAuth 2.0 authentication   
 

  
 
 
 
 

 
Change By: 
 Robert Šiška  
 
 
Summary: 
 Using Gmail as a mail client requires enabling a less secure option on your account Implement OAuth 2.0 authentication  
 

  
 
 
 
 

 
 
 

 
 
 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-1018) Polish and refine pages concerning bootstrapping and import / export JCR data

[JIRA (on behalf of Christoph Meier)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-1018  
 
 
  Polish and refine pages concerning bootstrapping and import / export JCR data   
 

  
 
 
 
 

 
Change By: 
 Christoph Meier  
 
 
Sprint: 
 Docu Sprint 24  
 

  
 
 
 
 

 
 
 

 
 
 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-1018) Polish and refine pages concerning bootstrapping and import / export JCR data

[JIRA (on behalf of Christoph Meier)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Meier created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-1018  
 
 
  Polish and refine pages concerning bootstrapping and import / export JCR data   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Christoph Meier  
 
 
Created: 
 11/May/17 1:34 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christoph Meier  
 

  
 
 
 
 

 
 This ticket is a follow-up which arose during tackling DOCU-1016 (Reflect "JCR Export improvements"). Polish and refine pages concerning bootstrapping and import / export JCR data Reasons: 
 
The page "Importing and exporting JCR data" was a big mingle-mangle concerning many different types of importing and exporting data - not only related to JCR-export-import. 
Clearly distinct between 
 
Download YAML definition (to create YAML based definition items to be used in light modules). 
Export / import JCR data - bootstrapping - with both (XML and) YAML files 
  
 While working on DOCU-1016, i have decided to split up the mingle-mangle page - at least on the DOCS space so far. (So, as an exception, the ticket describes in retrospect what has be done. This allows to figure out later what we have changed and reflects our work). New structure: Importing and exporting data (basically only a parent page with links to children) 
 
Importing and exporting JCR data for bootstrapping 
 
Bootstrapping in Maven modules (moved) 
Bootstrapping in light modules (moved) 
   

[magnolia-dev] [JIRA] (MGNLWORKFLOW-305) As a publisher I should be able to take control of an "InProgress" workitem

[JIRA (on behalf of Zdenek Skodik)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Zdenek Skodik updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Workflow Module /  MGNLWORKFLOW-305  
 
 
  As a publisher I should be able to take control of an "InProgress" workitem   
 

  
 
 
 
 

 
Change By: 
 Zdenek Skodik  
 
 
Support Score: 
  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLCACHE-177) On Windows cache folder is not used and a new one is created instead

[JIRA (on behalf of Federico Grilli)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Cache Module /  MGNLCACHE-177  
 
 
  On Windows cache folder is not used and a new one is created instead   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 
 
Labels: 
 windows  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLCACHE-177) On Windows cache folder is not used and a new one is created instead

[JIRA (on behalf of Federico Grilli)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Cache Module /  MGNLCACHE-177  
 
 
  On Windows cache folder is not used and a new one is created instead   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 11/May/17 11:53 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Federico Grilli  
 

  
 
 
 
 

 
 On Windows a "cacheC" folder is created and used instead of the predefined "cache" folder. This may be related to an issue in info.magnolia.cms.core.Path#getCacheDirectory. Caching functionality should not be affected anyway.  The odd folder name may be due to C referring to C: drive in Windows. Then the subfolders basically mirror the absolute path to the web app. e.g. suppose the web app is under c:\\foo\apache-tomcat\webapps\magnolia-webapp then the cache folder structure is something like cacheC\foo\apache-tomcat\magnolia-webapp.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
   

[magnolia-dev] [JIRA] (MGNLWORKFLOW-260) Failed publication task cannot be removed from list

[on behalf of Roman Kovařík]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Roman Kovařík reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Reopened, new rule throw error for nodes marked as deleted: 

 

2017-05-11 11:16:34,213 WARN  lization.action.availability.IsNotVariantsNodeRule: Can't get nodetype for node with uuid [daee5d0a-6b39-4015-9ed6-42721294a758] in version [null]. Availability rule will return false
javax.jcr.version.VersionException: org.apache.jackrabbit.spi.commons.conversion.IllegalNameException: empty name
at org.apache.jackrabbit.core.version.VersionHistoryImpl.getVersion(VersionHistoryImpl.java:144)
at info.magnolia.jcr.decoration.ContentDecoratorVersionHistoryWrapper.getVersion(ContentDecoratorVersionHistoryWrapper.java:105)
at info.magnolia.jcr.decoration.ContentDecoratorVersionHistoryWrapper.getVersion(ContentDecoratorVersionHistoryWrapper.java:105)
at info.magnolia.jcr.decoration.ContentDecoratorVersionHistoryWrapper.getVersion(ContentDecoratorVersionHistoryWrapper.java:105)
at info.magnolia.jcr.decoration.ContentDecoratorVersionHistoryWrapper.getVersion(ContentDecoratorVersionHistoryWrapper.java:105)
at info.magnolia.jcr.decoration.ContentDecoratorVersionHistoryWrapper.getVersion(ContentDecoratorVersionHistoryWrapper.java:105)
at info.magnolia.cms.core.version.BaseVersionManager.getVersion(BaseVersionManager.java:366)
at info.magnolia.personalization.action.availability.IsNotVariantsNodeRule.isAvailableForItem(IsNotVariantsNodeRule.java:61)
at info.magnolia.ui.api.availability.AbstractAvailabilityRule.isAvailable(AbstractAvailabilityRule.java:53)
at info.magnolia.ui.framework.availability.AvailabilityCheckerImpl.isAvailable(AvailabilityCheckerImpl.java:111)
at info.magnolia.ui.admincentral.shellapp.pulse.item.detail.AbstractPulseDetailPresenter.start(AbstractPulseDetailPresenter.java:114)
at info.magnolia.ui.admincentral.shellapp.pulse.task.TasksListPresenter.openItem(TasksListPresenter.java:144)
at info.magnolia.ui.admincentral.shellapp.pulse.PulsePresenter.openItem(PulsePresenter.java:147)
at info.magnolia.ui.admincentral.shellapp.pulse.task.TasksListPresenter.updateDetailView(TasksListPresenter.java:160)
at info.magnolia.ui.admincentral.shellapp.pulse.item.detail.AbstractPulseDetailPresenter.onUpdateDetailView(AbstractPulseDetailPresenter.java:144)
at info.magnolia.ui.admincentral.shellapp.pulse.task.action.ClaimTaskAction.executeTask(ClaimTaskAction.java:59)
at info.magnolia.ui.admincentral.shellapp.pulse.task.action.AbstractTaskAction.execute(AbstractTaskAction.java:76)
at info.magnolia.ui.api.action.AbstractActionExecutor.execute(AbstractActionExecutor.java:62)
at info.magnolia.ui.admincentral.shellapp.pulse.item.detail.AbstractPulseDetailPresenter.onActionbarItemClicked(AbstractPulseDetailPresenter.java:155)
at info.magnolia.ui.actionbar.ActionbarPresenter.onActionbarItemClicked(ActionbarPresenter.java:205)
at info.magnolia.ui.actionbar.ActionbarViewImpl$1.actionTrigger(ActionbarViewImpl.java:67)
at sun.reflect.GeneratedMethodAccessor902.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.vaadin.event.ListenerMethod.receiveEvent(ListenerMethod.java:508)
at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:198)
at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:161)
at com.vaadin.server.AbstractClientConnector.fireEvent(AbstractClientConnector.java:1008)
at info.magnolia.ui.vaadin.actionbar.Actionbar.access$000(Actionbar.java:59)
at info.magnolia.ui.vaadin.actionbar.Actionbar$1.onActionTriggered(Actionbar.java:72)
at sun.reflect.GeneratedMethodAccessor901.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at 

[magnolia-dev] [JIRA] (MGNLGROOVY-161) Groovy createAppScript causes a Definitions app problem

[JIRA (on behalf of Maxime Michel)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Groovy Module /  MGNLGROOVY-161  
 
 
  Groovy createAppScript causes a Definitions app problem   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Affects Versions: 
 2.5.2  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 11/May/17 10:47 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Maxime Michel  
 

  
 
 
 
 

 
 

 

Property [workspace] not found in class [info.magnolia.ui.contentapp.definition.ConfiguredEditorDefinition], property is not assigned
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment