[magnolia-dev] [JIRA] (NPMCLI-83) templateScript path uses backslash

2017-02-03 Thread JIRA (on behalf of Federico Grilli) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-83  
 
 
  templateScript path uses backslash   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 
 
Priority: 
 Neutral Major  
 

  
 
 
 
 

 
 
 

 
 
 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-3571) More subtle appearance of language switcher in dialogs

2017-02-03 Thread on behalf of Michael Mühlebach 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3571  
 
 
  More subtle appearance of language switcher in dialogs   
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Fix Version/s: 
 5.4.x  
 

  
 
 
 
 

 
 
 

 
 
 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] (MTE-103) Stacktrace on missing image for MTK/Image component

2017-02-03 Thread JIRA (on behalf of Martijn Kooijman) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martijn Kooijman created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Templating Essentials /  MTE-103  
 
 
  Stacktrace on missing image for MTK/Image component   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 1.1.1  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 03/Feb/17 3:45 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Martijn Kooijman  
 

  
 
 
 
 

 
 In my project, I am using mtk:components/image component. I have selected an image and it works fine. Now the image is deleted and the component throws: FreeMarker template error (HTML_DEBUG mode; use RETHROW in production!) The following has evaluated to null or missing: ==> damfn.getRendition(content.image, "original") [in template "mtk/templates/components/image.ftl" at line 14, column 26] It looks like the code at mtk/templates/components/image.ftl:line 14 is not handling null-values very well, because getRendition can return null when the image is not there: assign rendition = damfn.getRendition(content.image, "original")  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[magnolia-dev] [JIRA] (MGNLUI-3567) Elements in dialog footer not vertically centered, if combobox appears

2017-02-03 Thread on behalf of Michael Mühlebach 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3567  
 
 
  Elements in dialog footer not vertically centered, if combobox appears   
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Fix Version/s: 
 5.4.x  
 

  
 
 
 
 

 
 
 

 
 
 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-72) Groovy scripts in light modules

2017-02-03 Thread JIRA (on behalf of Anonymous Community User) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Anonymous Community User created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Suggestion Box /  SUGGEST-72  
 
 
  Groovy scripts in light modules   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 03/Feb/17 3:03 PM  
 
 
Environment: 

 
 
Labels: 
 collector-0cf1239d  
 
 
Reporter: 
 Anonymous Community User  
 

  
 
 
 
 

 
 We are currently migrating our components from one ui module to another and created a groovy script to go through the website JCR and replace the old mgnl:template values with the new ones. We don’t have that script currently under source control since we need to modify it often as we add new components so keeping it in a backend module would be too slow. Being able to keep groovy scripts in our light module would help us get the benefits of keeping them under source control and still be able to make fast changes. Reporter: Niko Salminen E-mail: n...@salminen.me  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[magnolia-dev] [JIRA] (MGNLACTIVATION-143) Create maven submodules

2017-02-03 Thread JIRA (on behalf of Jaroslav Simak) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jaroslav Simak updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Activation Module /  MGNLACTIVATION-143  
 
 
  Create maven submodules   
 

  
 
 
 
 

 
Change By: 
 Jaroslav Simak  
 
 
Summary: 
 Split activation into Create maven  submodules  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLACTIVATION-143) Split activation into submodules

2017-02-03 Thread JIRA (on behalf of Jaroslav Simak) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jaroslav Simak updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Activation Module /  MGNLACTIVATION-143  
 
 
  Split activation into submodules   
 

  
 
 
 
 

 
Change By: 
 Jaroslav Simak  
 

  
 
 
 
 

 
 Split activation into maven submodules:*  activation  publishing - ui app *  activation  publishing -sender*  activation  publishing -receiver*  activation  publishing -compatibility  
 

  
 
 
 
 

 
 
 

 
 
 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

2017-02-03 Thread on behalf of Michael Mühlebach 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Task Management /  TASKMGMT-17  
 
 
  Register the TaskEventDispatchers inside the task module   
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Fix Version/s: 
 1.1.x  
 

  
 
 
 
 

 
 
 

 
 
 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-3384) Remove Task Event related code from AdminCentral

2017-02-03 Thread on behalf of Michael Mühlebach 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3384  
 
 
  Remove Task Event related code from AdminCentral   
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Fix Version/s: 
 5.4.x  
 

  
 
 
 
 

 
 
 

 
 
 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] Configuring custom SearchContentToolPresenter

2017-02-03 Thread Sebastian Tauch (via Magnolia Forums) 
Hello,

the magnolia implementation of SearchContentToolPresenter switches into the 
ListView if the search field is empty, regardless of the view the user was in 
before starting a search.

I want to change this behaviour to always switch into the TreeView instead, 
because otherwise our users run into timeouts when searching in the DAM App due 
to our huge amount of assets.

What is the best way to achieve this?

 * I tried registering my custom SearchContentToolPresenter implementation via 
the project.xml, but I get google inject compile errors for missing magnolia 
class implementations. If I add them as well, there are now even more magnolia 
classes implementations missing. This doesn't seem to be the way.
* I tried writing and registering a custom WorkbenchPresenter implentation via 
the project.xml, but I run into the same problems as above
* I tried to add my custom SearchContentToolPresenter through the config app's 
workbench configuration but I can't find any example or documentation on how to 
achieve this correctly

Some pointers would be very appreciated!
Sebastian Tauch

Sebastian Tauch

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=a3e70426-4a34-4ae9-8533-5dc2e93e7cf3



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-3288) UI requires PUSH

2017-02-03 Thread on behalf of Michael Mühlebach 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3288  
 
 
  UI requires PUSH   
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Story Points: 
 21  
 

  
 
 
 
 

 
 
 

 
 
 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] (LOGTOOLS-22) Adapt to current Grid style

2017-02-03 Thread JIRA (on behalf of Maxime Michel) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maxime Michel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Log Tools /  LOGTOOLS-22  
 
 
  Adapt to current Grid style   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Affects Versions: 
 1.0.3  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 files.png, levels.png  
 
 
Created: 
 03/Feb/17 2:05 PM  
 
 
Fix Versions: 
 1.0.4  
 
 
Labels: 
 ux  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Maxime Michel  
 

  
 
 
 
 

 
 The following commit altered the defaults that the Log Tools stylesheet is built from: https://git.magnolia-cms.com/projects/PLATFORM/repos/ui/commits/42b492bdb9a71896337b36795d5b2e4c60abf083 Resulting in a layout that looks untidy/broken, as seen in the screenshots. What is done in the Log Tools stylesheet should therefore be adapted.

[magnolia-dev] [JIRA] (MGNLUI-3577) Sortable property shouldn't sort by default

2017-02-03 Thread on behalf of Robert Šiška 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Robert Šiška updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-3577  
 
 
  Sortable property shouldn't sort by default   
 

  
 
 
 
 

 
Change By: 
 Robert Šiška  
 
 
Fix Version/s: 
 5.4.11  
 
 
Fix Version/s: 
 5.5.2  
 
 
Fix Version/s: 
 5.4.x  
 

  
 
 
 
 

 
 
 

 
 
 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] (MGNLWKLED-15) As a workflow editor, I would like to configure my task directly in the editor properties panel

2017-02-03 Thread JIRA (on behalf of Adrien Manzoni) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Manzoni updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia workflow online editor /  MGNLWKLED-15  
 
 
  As a workflow editor, I would like to configure my task directly in the editor properties panel   
 

  
 
 
 
 

 
Change By: 
 Adrien Manzoni  
 
 
Sprint: 
 Sprint  3  4  
 

  
 
 
 
 

 
 
 

 
 
 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-934) Disabling activation workflow add a not for personalization

2017-02-03 Thread JIRA (on behalf of Mercedes Iruela) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mercedes Iruela created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-934  
 
 
  Disabling activation workflow add a not for personalization   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Affects Versions: 
 5.5, 5.4.10  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 content  
 
 
Created: 
 03/Feb/17 10:01 AM  
 
 
Due Date: 
03/Feb/17 
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Mercedes Iruela  
 

  
 
 
 
 

 
 There is a page in documentation that explains how to disable activation workflow (https://documentation.magnolia-cms.com/display/DOCS/Disabling+activation+workflow), when you disable the activation workflow for Pages app, and instead use: default-activate just activates the content. No workflow, no versioning. versioned-activate activates and versions the content. No workflow. Variants are not published, since these commands don´t use personalizationActivation command, as it is used in workflow-activate.  It would be great if we can add a comment about it. If the command is changed directly in /modules/activation/commands/versioned/activate/activate@commandName, it will affect to all workspaces. So maybe it would be better create a new command based on versioned-activate command, but using personalizationActivation command, and use this command stead.

[magnolia-dev] [JIRA] (MGNLCACHE-164) Browser cache policy "never" is too broad

2017-02-03 Thread on behalf of Roman Kovařík 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roman Kovařík updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Cache Module /  MGNLCACHE-164  
 
 
  Browser cache policy "never" is too broad   
 

  
 
 
 
 

 
Change By: 
 Roman Kovařík  
 

  
 
 
 
 

 
 The browser cache policy {{never}} is too broad. It prevents the browser from caching image thumbnails in the Assets app and preview images in the asset chooser. Users may experience this as slow performance. The browser reloads thumbnails every time the user expands/collapses an asset folder, which causes delay and feels frustrating.To reproduce:# Go to https://demo.magnolia-cms.com/# Open the Assets app.# Expand the {{/tours}} folder. Image thumbnails are generated and loaded.# Collapse and expand the folder again. Image thumbnails are loaded *again*.The {{never}} policy configuration was introduced Magnolia 5.5.1 (MGNLCACHE-12). The purpose was to address an issue (MGNLUI-3769) where a user adds an image in CKEditor, then crops the image in Assets, but doesn't see the edit reflected in CKEditor.Proposal: Remove the {{never}} policy and introduce a *more specific policy*  that resolves theCKEditor issue  should be solved  without impacting image thumbnails and previews in the Assets app , see MGNLUI-3769 .{{/modules/cache/config/contentCaching/defaultPageCache/browserCachePolicy/policies/never}}   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[magnolia-dev] [JIRA] (NPMCLI-94) Use consistent logging style

2017-02-03 Thread JIRA (on behalf of Federico Grilli) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-94  
 
 
  Use consistent logging style   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 
 
Story Points: 
 2 3  
 

  
 
 
 
 

 
 
 

 
 
 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] (NPMCLI-94) Use consistent logging style

2017-02-03 Thread JIRA (on behalf of Federico Grilli) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-94  
 
 
  Use consistent logging style   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 
 
Story Points: 
 2  
 

  
 
 
 
 

 
 
 

 
 
 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: