[magnolia-dev] Quickbooks Error Support Number@+1-(888)-436-4111)Quickbooks Error Support Number@+1-(888)-436-4111)Quickbooks Error Support Number@+1-(888)-436-4111)Quickbooks Error Support Number@+1

[Adam Gill (via Magnolia Forums)]

Quickbooks Error Support Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support Number@+1-(888)-436-4111)

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=330458ab-7fa6-4597-80e6-3d316ff0f1a4



For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] Re: Quickbooks Error Support Number@+1-(888)-436-4111)Quickbooks Error Support Number@+1-(888)-436-4111)Quickbooks Error Support Number@+1-(888)-436-4111)Quickbooks Error Support Numbe

[Adam Gill (via Magnolia Forums)]

Quickbooks Error Support Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 
Number@+1-(888)-436-4111)Quickbooks Error Support 

[magnolia-dev] [JIRA] (DOCU-645) Add a section about using imgfn on page "Working with images"

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Documentation /  DOCU-645 
 
 
 
  Add a section about using imgfn on page "Working with images"  
 
 
 
 
 
 
 
 
 

Change By:
 
 Christoph Meier 
 
 
 
 
 
 
 
 
 
 Main goal:*Show how to get a link an a link for a variation (defined on site) for binaries stored on "any" workspace.*A side nore from Philip Mundt: _Actually, imgfn will work with  (a binary node from)  assets but damfn won't work with images in website workspace, IIRC_Example:/tours/shark_brian_warrick_0824.JPG/jcr:content/tours/shark_brian_warrick_0824.JPG/jcr:content/jcr:data="" />asset.getJCRNode()imgfn <- asset.getJCRNode().getNode("jcr:content")=> stuff from DAM also could be applied to damfn. However, vice versa is not possible. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3924) Pulse messages doesn't show for user with commercial at (@) in name

[JIRA (on behalf of Milan Divilek)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Milan Divilek updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3924 
 
 
 
  Pulse messages doesn't show for user with commercial at (@) in name  
 
 
 
 
 
 
 
 
 

Change By:
 
 Milan Divilek 
 
 
 

Summary:
 
 Allow Pulse messages doesn't show for user with  commercial at (@)  for usernames  in name 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3924) Allow commercial at (@) for usernames

[JIRA (on behalf of Milan Divilek)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Milan Divilek updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3924 
 
 
 
  Allow commercial at (@) for usernames  
 
 
 
 
 
 
 
 
 

Change By:
 
 Milan Divilek 
 
 
 

Project:
 
 Magnolia  UI 
 
 
 

Key:
 
 MAGNOLIA MGNLUI - 6644 3924 
 
 
 

Fix Version/s:
 
 5.4.8 
 
 
 

Fix Version/s:
 
 5.4.8 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (MGNLACTIVATION-130) Update dependencies as part of Bouncy Castle update

[JIRA (on behalf of Maxime Michel)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maxime Michel created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia Activation Module /  MGNLACTIVATION-130 
 
 
 
  Update dependencies as part of Bouncy Castle update  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Maxime Michel 
 
 
 

Created:
 

 21/Jun/16 3:09 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Maxime Michel 
 
 
 
 
 
 
 
 
 
 
Integrating the following old commit as part of the Bouncy Castle update: https://git.magnolia-cms.com/projects/MODULES/repos/activation/commits/e96f15d713cda4a328de2d33e26ca20be6fa8f84 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
   

[magnolia-dev] [JIRA] (MGNLUI-3921) Adjust restore previous version action to pass rule to the command

[on behalf of Robert Šiška]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robert Šiška updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3921 
 
 
 
  Adjust restore previous version action to pass rule to the command  
 
 
 
 
 
 
 
 
 

Change By:
 
 Robert Šiška 
 
 
 

Fix Version/s:
 
 5.3.15 
 
 
 

Fix Version/s:
 
 5.4.8 
 
 
 

Fix Version/s:
 
 5.5 
 
 
 

Story Points:
 
 1 
 
 
 

Sprint:
 
 Kromeriz 49 
 
 
 

Account:
 
 null (null) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
   

[magnolia-dev] [JIRA] (MGNLUI-3923) Scheduled date in Pulse is not displayed in user's time zone

[JIRA (on behalf of Antti Hietala)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antti Hietala created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3923 
 
 
 
  Scheduled date in Pulse is not displayed in user's time zone  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.7 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 scheduled-date.png 
 
 
 

Components:
 

 admincentral 
 
 
 

Created:
 

 21/Jun/16 1:50 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Antti Hietala 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
With MNGLUI-2695 we started to display dates and times in the user's preferred time zone. However, this change was only applied to date columns in apps. The Scheduled date field in a Pulse task does not follow the pattern. It shows "server time" instead. Please adapt the Scheduled date field too so that it follows the general pattern.  
 

[magnolia-dev] [JIRA] (MGNLUI-3923) Scheduled date in Pulse is not displayed in user's time zone

[JIRA (on behalf of Antti Hietala)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antti Hietala updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3923 
 
 
 
  Scheduled date in Pulse is not displayed in user's time zone  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antti Hietala 
 
 
 
 
 
 
 
 
 
 With  MNGLUI  MGNLUI -2695 we started to display dates and times in the user's preferred time zone. However, this change was only applied to date _columns_ in apps. The Scheduled date field in a Pulse task does not follow the pattern. It shows "server time" instead. Please adapt the Scheduled date field too so that it follows the general pattern. To reproduce,# Schedule the publishing of a page to the next full hour.# Change the user's time zone preference away from the default "Your browser timezone".# Logout / login.# Open the publication task in Pulse.Expected outcome: The message view shows the Scheduled date in your preferred time zone.Actual outcome: The message view shows the Scheduled date in server time. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3922) Page delete confirmation message in dialog is not correct processed

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3922 
 
 
 
  Page delete confirmation message in dialog is not correct processed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Frank Sommer 
 
 
 
 
 
 
 
 
 
 The message in page delete confirmation dialog is not processed. The bug occures  at least  for French and Italian users. German and English is fine. It is reproducable on Demoauthor instance. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3922) Page delete confirmation message in dialog is not correct processed

[JIRA (on behalf of Frank Sommer)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Frank Sommer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3922 
 
 
 
  Page delete confirmation message in dialog is not correct processed  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 5.4.6, 5.3.14 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 remove-dialog-french.png, remove-dialog-italian.png 
 
 
 

Components:
 

 dialogs 
 
 
 

Created:
 

 21/Jun/16 1:40 PM 
 
 
 

Priority:
 
  Neutral 
 
 
 

Reporter:
 
 Frank Sommer 
 
 
 

Security Level:
 

 Public 
 
 
 
 
 
 
 
 
 
 
The message in page delete confirmation dialog is not processed. The bug occures for French and Italian users. German and English is fine. It is reproducable on Demoauthor instance. 
 
 
 
  

[magnolia-dev] [JIRA] (MGNLUI-3921) Adjust restore previous version action to pass rule to the command

[on behalf of Robert Šiška]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robert Šiška updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia UI /  MGNLUI-3921 
 
 
 
  Adjust restore previous version action to pass rule to the command  
 
 
 
 
 
 
 
 
 

Change By:
 
 Robert Šiška 
 
 
 

Project:
 
 Magnolia  DAM Module  UI 
 
 
 

Key:
 
 MGNLDAM MGNLUI - 661 3921 
 
 
 

Security:
 
 Public 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] (SUGGEST-40) Allow YAML format for module descriptor for both light modules and Maven modules

[JIRA (on behalf of Christoph Meier)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Meier created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Suggestion Box /  SUGGEST-40 
 
 
 
  Allow YAML format for module descriptor for both light modules and Maven modules   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 21/Jun/16 10:44 AM 
 
 
 

Environment:
 
   
 
 
 

Labels:
 

 collector-0cf1239d 
 
 
 

Reporter:
 
 Christoph Meier 
 
 
 
 
 
 
 
 
 
 
Allow YAML format for module descriptor for both light modules and Maven modules. 
For sure this is not possible before the YAML based module descriptor can define all the properties which can be defined in the XML based mod. desc. 
"At the end" it should be possible to use the YAML based file for both "types of modules" on the same location. (See https://documentation.magnolia-cms.com/display/DOCS/Module+structure) - and at this point prbly. the XML based mod. desc. may become deprecated. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 

[magnolia-dev] Re: Light Module App/SubApp template

[Christoph Meier (via Magnolia Forums)]

Dear Mikael

[quote]
The easiest way to describe what I want to do is How do I make a AppLauncher 
for the Hello Magnolia light module example without any Java?
https://documentation.magnolia-cms.com/display/DOCS/Hello+Magnolia
[/quote]

(1)
You want to make an App Launcher ... or i guess you want to add a *App launcher 
tile*.
Please note that an  *App launcher tile* is meant to launch an app 
(https://documentation.magnolia-cms.com/display/DOCS/_What+is+the+App+launcher).
See  , https://documentation.magnolia-cms.com/display/DOCS/Apps  to understand 
what an *App* is (in the Magnolia context).
Furthermore, the page 
https://documentation.magnolia-cms.com/display/DOCS/App+launcher+layout  
explains how to add an App launcher tile to your Magnolia instance (to launch 
one of *your* apps).

(2)
When following the "Hello Magnolia" tutorial, there is no new app created. All 
what happens, one creates a light module named "hello-magnolia", which contains 
a page template, a component template, 2 dialogs and some css, but NO app.

Neither in (1) nor in (2) you need Java.

A (light) module may contain 0 to many apps, hello-magnolia has none. 
Therefore, no need to add an extra app launcher tile to the app launcher.

I still don't know exactly, what you try to achieve.
However, if your use case requires an app - then create an app - with or 
without Java.
The page 
https://documentation.magnolia-cms.com/display/DOCS/My+first+content+app  would 
give you some first ideas ho to create an app.

Cheers,
 Christoph

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=5b0fd144-f28d-486a-9d1b-7995a0bdc2bb



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: