[magnolia-dev] [JIRA] (MGNLUI-4035) "Move Before" and "Move After" buttons' states are not handled correctly
Title: Message Title Hieu Nguyen Duc updated an issue Magnolia UI / MGNLUI-4035 "Move Before" and "Move After" buttons' states are not handled correctly Change By: Hieu Nguyen Duc Summary: " Move Before " and " Move After " buttons' states are not handled correctly 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-4035) Move Before and Move After buttons' states are not handled correctly
Title: Message Title Hieu Nguyen Duc updated an issue Magnolia UI / MGNLUI-4035 Move Before and Move After buttons' states are not handled correctly Change By: Hieu Nguyen Duc Labels: 5.5-beta-1 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-4035) Move Before and Move After buttons' states are not handled correctly
Title: Message Title Hieu Nguyen Duc updated an issue Magnolia UI / MGNLUI-4035 Move Before and Move After buttons' states are not handled correctly Change By: Hieu Nguyen Duc This issue occurs in Site app and Security app.Steps to reproduce: + * Open Site app + * Create a folder + * Create a content node inside that folder + * Select that content node, open Move dialog + * Select then deselect on the content node + * {{Move Before}} and {{Move After}} will be enabled + * Click on any of those buttons=> Expected: The content node is moved to first level.=> Actual: It disappears! We can see it using JCR app.Consider to disable "Move before" and "Move after" in this case like Pages app because this issue doesn't occur in Pages app. 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-4035) Move Before and Move After buttons' states are not handled correctly
Title: Message Title Hieu Nguyen Duc updated an issue Magnolia UI / MGNLUI-4035 Move Before and Move After buttons' states are not handled correctly Change By: Hieu Nguyen Duc Component/s: dialogs 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-4035) Move Before and Move After buttons' states are not handled correctly
Title: Message Title Hieu Nguyen Duc created an issue Magnolia UI / MGNLUI-4035 Move Before and Move After buttons' states are not handled correctly Issue Type: Bug Affects Versions: 5.4.10, 5.5 Assignee: Unassigned Attachments: reproductionImage.png Created: 18/Oct/16 6:21 AM Labels: 5.5-beta-1 Priority: Neutral Reporter: Hieu Nguyen Duc Security Level: Public This issue occurs in Site app and Security app. Steps to reproduce: + Open Site app + Create a folder + Create a content node inside that folder + Select that content node, open Move dialog + Select then deselect on the content node + Move Before and Move after will be enabled + Click
[magnolia-dev] [JIRA] (MGNLUI-4035) Move Before and Move After buttons' states are not handled correctly
Title: Message Title Hieu Nguyen Duc updated an issue Magnolia UI / MGNLUI-4035 Move Before and Move After buttons' states are not handled correctly Change By: Hieu Nguyen Duc This issue occurs in Site app and Security app.Steps to reproduce:+ Open Site app+ Create a folder+ Create a content node inside that folder+ Select that content node, open Move dialog+ Select then deselect on the content node+ {{ Move Before }} and {{ Move after After}} will be enabled+ Click on any of those buttons=> Expected: The content node is moved to first level.=> Actual: It disappears! We can see it using JCR app.Consider to disable "Move before" and "Move after" in this case like Pages app because this issue doesn't occur in Pages app. 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] (DOCU-851) Postponed from 'Golden leafs' release
Title: Message Title Christoph Meier updated an issue Documentation / DOCU-851 Postponed from 'Golden leafs' release Change By: Christoph Meier Labels: mnow 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] (DOCU-850) Magnolia Now docs 'White snow release'
Title: Message Title Christoph Meier updated an issue Documentation / DOCU-850 Magnolia Now docs 'White snow release' Change By: Christoph Meier Labels: mnow 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] (DOCU-822) How to replicate an environment
Title: Message Title Christoph Meier updated an issue Documentation / DOCU-822 How to replicate an environment Change By: Christoph Meier Security: Private Public Parent Issue: DOCU- 820 851 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] (DOCU-825) How to tweak an environment
Title: Message Title Christoph Meier updated an issue Documentation / DOCU-825 How to tweak an environment Change By: Christoph Meier Fix Version/s: 5.5.x 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] (DOCU-822) How to replicate an environment
Title: Message Title Christoph Meier updated an issue Documentation / DOCU-822 How to replicate an environment Change By: Christoph Meier Fix Version/s: 5.5.x 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] (DOCU-825) How to tweak an environment
Title: Message Title Christoph Meier updated an issue Documentation / DOCU-825 How to tweak an environment Change By: Christoph Meier Security: Private Public Parent Issue: DOCU- 820 851 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] (DOCU-850) Magnolia Now docs 'White snow release'
Title: Message Title Christoph Meier updated an issue Documentation / DOCU-850 Magnolia Now docs 'White snow release' Change By: Christoph Meier Fix Version/s: 5.5.x 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] (DOCU-851) Postponed from 'Golden leafs' release
Title: Message Title Christoph Meier created an issue Documentation / DOCU-851 Postponed from 'Golden leafs' release Issue Type: Story Assignee: Unassigned Created: 17/Oct/16 5:31 PM Fix Versions: 5.5.x Priority: Neutral Reporter: Christoph Meier Security Level: Public Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
[magnolia-dev] [JIRA] (DOCU-850) Magnolia Now docs 'White snow release'
Title: Message Title Christoph Meier created an issue Documentation / DOCU-850 Magnolia Now docs 'White snow release' Issue Type: Epic Assignee: Unassigned Created: 17/Oct/16 5:29 PM Priority: Neutral Reporter: Christoph Meier Security Level: Public This is the epic for the Magnolia Now documentation things to be created / updated / whatever for the 'White snow release'. Add Comment This message was
[magnolia-dev] [JIRA] (JSONFN-1) Code cleanup
Title: Message Title Evzen Fochr updated an issue JSON Templating Functions / JSONFN-1 Code cleanup Change By: Evzen Fochr Labels: backlog 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] (JSONFN-1) Code cleanup
Title: Message Title Evzen Fochr updated an issue JSON Templating Functions / JSONFN-1 Code cleanup Change By: Evzen Fochr Labels: backlog 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] (JSONFN-1) Code cleanup
Title: Message Title Evzen Fochr updated an issue JSON Templating Functions / JSONFN-1 Code cleanup Change By: Evzen Fochr Labels: selected-for-backlog 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] (JSONFN-1) Code cleanup
Title: Message Title Evzen Fochr updated an issue JSON Templating Functions / JSONFN-1 Code cleanup Change By: Evzen Fochr Story Points: 0 Sprint: Kromeriz 66 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] (JSONFN-1) Code cleanup
Title: Message Title Evzen Fochr created an issue JSON Templating Functions / JSONFN-1 Code cleanup Issue Type: Improvement Assignee: Evzen Fochr Created: 17/Oct/16 4:02 PM Priority: Neutral Reporter: Evzen Fochr Fix versions in module descriptor Cleanup and code formating Raise parent pom to 31 fix JsonBuilder expand(String propertyNameRegex, String targetRepository, String targetPropertyName) javadoc Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
[magnolia-dev] [JIRA] (CFGUI-47) Use mono-space font for code-related detail messages
Title: Message Title Cedric Reichenbach updated an issue Definitions app / CFGUI-47 Use mono-space font for code-related detail messages Change By: Cedric Reichenbach Assignee: Cedric Reichenbach 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] (MGNLCE-61) Remove "too many open files" startup check - if possible thanks to H2
Title: Message Title Christopher Zimmermann created an issue Magnolia Community Edition / MGNLCE-61 Remove "too many open files" startup check - if possible thanks to H2 Issue Type: Task Assignee: Ilgun Ilgun Created: 17/Oct/16 2:43 PM Fix Versions: 5.5 Priority: Neutral Reporter: Christopher Zimmermann One benefit of switching to H2 is that it opens less file handles than Derby. After switching to H2, test if the problems due to too many open files are reduced ENOUGH, so that we can remove the check and restriction on Magnolia startup. Reason: It is a hurdle for evaluators and new developers to have to change the system settings for handling open files, so it would be an improvement if we could remove this check. See "too many open files" at https://documentation.magnolia-cms.com/display/DOCS/_Known+issues Add Comment
[magnolia-dev] [JIRA] (CFGUI-48) Provide detail view for problems
Title: Message Title Philip Mundt updated an issue Definitions app / CFGUI-48 Provide detail view for problems Change By: Philip Mundt Assignee: Aleksandr Pchelintcev 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] (CFGUI-50) Build unique url fragment in content connector
Title: Message Title Philip Mundt updated an issue Definitions app / CFGUI-50 Build unique url fragment in content connector Change By: Philip Mundt Assignee: Cedric Reichenbach 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] (MGNLSITE-60) Themes added by using the old mechanism (backwards-compatible) are not decorateable
Title: Message Title Michael Mühlebach updated an issue Magnolia Site Module / MGNLSITE-60 Themes added by using the old mechanism (backwards-compatible) are not decorateable Change By: Michael Mühlebach Assignee: Philip Mundt Aleksandr Pchelintcev 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] (DOCU-847) Document MTE navigation features
Title: Message Title Christoph Meier updated an issue Documentation / DOCU-847 Document MTE navigation features Change By: Christoph Meier Assignee: Ruth Stocks Martin Drápela 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] (CFGUI-50) Build unique url fragment in content connector
Title: Message Title Cedric Reichenbach updated an issue Definitions app / CFGUI-50 Build unique url fragment in content connector Change By: Cedric Reichenbach Currently, the fragment consists of the definition's path itself and the selected path within the definition. - However, since a definition's path is not unique, there may be collisions. For instance, templating has two definitions with the same path {{/modules/templating/templates/plaintext}}; one of type renderer and one of type template. Including their type in the fragment would avoid this particular collision. - In general, two items should have the same path fragment exactly when1. Their corresponding DefinitionProviderIds are "{{#equals}}"2. They point to the same sub-path inside their corresponding definition 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-98) Support i18n for 'New Component' in area of page editor
Title: Message Title Roman Kovařík updated an issue Magnolia pages module / PAGES-98 Support i18n for 'New Component' in area of page editor Change By: Roman Kovařík Project: Magnolia UI pages module Key: MGNLUI PAGES - 4034 98 Issue Type: Bug Improvement Security: Public Component/s: page editor Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) For list details, see:
[magnolia-dev] [JIRA] (MGNLDEMO-189) Move themes to new location
Title: Message Title Philip Mundt updated an issue Magnolia Demo Projects / MGNLDEMO-189 Move themes to new location Change By: Philip Mundt Fix Version/s: 1.1 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] (MGNLDEMO-189) Move themes to new location
Title: Message Title Philip Mundt updated an issue Magnolia Demo Projects / MGNLDEMO-189 Move themes to new location Change By: Philip Mundt With MGNLSITE-48 we introduced a registry for theme. However we did not migrate the themes from the demo-projects yet.In order to showcase the new mechanism we should move to themes to their new location: * {{config:/modules/travel-demo/themes/travel-demo-theme}}* {{config:/modules/travel-demo-multisite/themes/sportstation-theme}} 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] (MGNLSITE-73) Remove theme subapp from site-app
Title: Message Title Philip Mundt updated an issue Magnolia Site Module / MGNLSITE-73 Remove theme subapp from site-app Change By: Philip Mundt Issue Type: Bug Task 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] (MGNLDEMO-189) Move themes to new location
Title: Message Title Philip Mundt updated an issue Magnolia Demo Projects / MGNLDEMO-189 Move themes to new location Change By: Philip Mundt With MGNLSITE-48 we introduced a registry for theme. However we did not migrate the themes from the demo-projects yet.In order to showcase the new mechanism we should move to themes to their new location: 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] (MGNLSITE-73) Remove theme subapp from site-app
Title: Message Title Philip Mundt updated an issue Magnolia Site Module / MGNLSITE-73 Remove theme subapp from site-app Change By: Philip Mundt Assignee: Philip Mundt 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] (MGNLDEMO-189) Move themes to new location
Title: Message Title Philip Mundt created an issue Magnolia Demo Projects / MGNLDEMO-189 Move themes to new location Issue Type: Improvement Assignee: Unassigned Created: 17/Oct/16 1:11 PM Priority: Neutral Reporter: Philip Mundt Security Level: Public Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
[magnolia-dev] [JIRA] (MGNLSITE-73) Remove theme subapp from site-app
Title: Message Title Philip Mundt updated an issue Magnolia Site Module / MGNLSITE-73 Remove theme subapp from site-app Change By: Philip Mundt When themes are added to the registry using the new mechanism, themes will not show up in the themes app. They can and should be viewed through the definitions-app.Old mechanism: Themes are placed in {{config:/modules/site/config/themes/}} they are not decorateable . This is due to backwards-compatible code setting the raw-view of the theme to an empty String when it's added to the registry.When adding the theme to New mechanism: {{config:/modules//themes/}} everything works according to plan. _When added by using the new mechanism however, themes will not show up in the themes app (see MGNLSITE-56 – which will most likely be rendered as won't fixed once definitions app is there)._ h4. Proposed solution * Wait for definitions app and* Remove the removal of the themes-app from the site-apps. 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] (MGNLSITE-73) Remove theme subapp from site-app
Title: Message Title Philip Mundt created an issue Magnolia Site Module / MGNLSITE-73 Remove theme subapp from site-app Issue Type: Bug Assignee: Philip Mundt Created: 17/Oct/16 1:05 PM Fix Versions: 1.1 Priority: Neutral Reporter: Philip Mundt When themes are placed in config:/modules/site/config/themes/ they are not decorateable. This is due to backwards-compatible code setting the raw-view of the theme to an empty String when it's added to the registry. When adding the theme to config:/modules//themes/ everything works according to plan. When added by using the new mechanism however, themes will not show up in the themes app (see MGNLSITE-56 – which will most likely be rendered as won't fixed once definitions app is there). Proposed solution Wait for definitions app and the removal of the themes-app from the site-apps.
[magnolia-dev] [JIRA] (MGNLSITE-60) Themes added by using the old mechanism (backwards-compatible) are not decorateable
Title: Message Title Philip Mundt updated an issue Magnolia Site Module / MGNLSITE-60 Themes added by using the old mechanism (backwards-compatible) are not decorateable Change By: Philip Mundt When themes are placed in {{config:/modules/site/config/themes/}} they are not decorateable.This is due to backwards-compatible code setting the raw-view of the theme to an empty String when it's added to the registry.When adding the theme to {{config:/modules//themes/}} everything works according to plan._When added by using the new mechanism however, themes will not show up in the themes app (see MGNLSITE-56 – which will most likely be rendered as won't fixed once definitions app is there)._h4. Proposed Implemented solution * Wait for definitions app and* the removal Instead of creating the themes-app theme with en empty raw view, we now determine the raw view from the site-apps theme node itself – enabling decoration of that theme . 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] Re: fileupload into magnolia-tmp-dir
Hello Benjamin Which version of Magnolia are you using? -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=0c7666f1-0a4b-439b-8efb-dbe287fecd0d 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: Failing to change the language on form responses
Hey Nuno Did you ever figure this out? Thanks, Jonas -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=653345e4-6d70-4f8a-9d8e-1e50807f3bbc 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 Christoph Meier updated an issue Magnolia Community Edition / MGNLCE-60 Remove "too many open files" startup check - if possible thanks to H2 Change By: Christoph Meier Documentation update required: Yes 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] (MGNLUI-4034) Support i18n for 'New Component' in area of page editor
Title: Message Title Viet Nguyen updated an issue Magnolia UI / MGNLUI-4034 Support i18n for 'New Component' in area of page editor Support customer to easily change/update 'New component' i18n key in area of our page editor. Please reference to linked Support 6746 issue for more detail. Change By: Viet Nguyen Attachment: newComponent.png 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-4034) Support i18n for 'New Component' in area of page editor
Title: Message Title Viet Nguyen updated an issue Magnolia UI / MGNLUI-4034 Support i18n for 'New Component' in area of page editor Change By: Viet Nguyen Comment: Support customer to easily change/update 'New component' i18n key in area of our page editor. Please reference to linked Support 6746 issue for more detail. 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-4034) Support i18n for 'New Component' in area of page editor
Title: Message Title Viet Nguyen updated an issue Magnolia UI / MGNLUI-4034 Support i18n for 'New Component' in area of page editor Change By: Viet Nguyen Support customer to easily change/update 'New component' i18n key in area of our page editor. Please reference to linked Support 6746 issue for more detail. 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-4034) Support i18n for 'New Component' in area of page editor
Title: Message Title Viet Nguyen created an issue Magnolia UI / MGNLUI-4034 Support i18n for 'New Component' in area of page editor Issue Type: Bug Assignee: Unassigned Components: page editor Created: 17/Oct/16 11:53 AM Priority: Minor Reporter: Viet Nguyen Security Level: Public Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
[magnolia-dev] [JIRA] (MGNLUI-4033) Double-check that there are no missing i18n keys
Title: Message Title Philip Mundt updated an issue Magnolia UI / MGNLUI-4033 Double-check that there are no missing i18n keys Change By: Philip Mundt Attachment: missing_tooltip.png 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-4033) Double-check that there are no missing i18n keys
Title: Message Title Maxime Michel updated an issue Magnolia UI / MGNLUI-4033 Double-check that there are no missing i18n keys Change By: Maxime Michel For correct reasons, MGNLUI-4027 removed a lot of i18n keys. Some were critical and have been spotted by the UI tests, and added again (at another location) . Others are a bit harder to spot (tooltips for instance). The goal of this ticket is to make sure that no i18n has gone missing in the current UI. 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-4033) Double-check that there are no missing i18n keys
Title: Message Title Maxime Michel created an issue Magnolia UI / MGNLUI-4033 Double-check that there are no missing i18n keys Issue Type: Task Assignee: Unassigned Created: 17/Oct/16 11:27 AM Priority: Neutral Reporter: Maxime Michel Security Level: Public MGNLUI-4027 removed a lot of i18n keys. Some were critical and have been spotted by the UI tests, and added again. Others are a bit harder to spot (tooltips for instance). The goal of this ticket is to make sure that no i18n has gone missing in the current UI. Add Comment
[magnolia-dev] [JIRA] (MGNLCE-60) Remove "too many open files" startup check - if possible thanks to H2
Title: Message Title Ilgun Ilgun updated an issue Magnolia Community Edition / MGNLCE-60 Remove "too many open files" startup check - if possible thanks to H2 Change By: Ilgun Ilgun Assignee: Ilgun Ilgun 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] (MGNLCE-60) Remove "too many open files" startup check - if possible thanks to H2
Title: Message Title Ilgun Ilgun updated an issue Magnolia Community Edition / MGNLCE-60 Remove "too many open files" startup check - if possible thanks to H2 Change By: Ilgun Ilgun 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] (MGNLCE-60) Remove "too many open files" startup check - if possible thanks to H2
Title: Message Title Michael Mühlebach updated an issue Magnolia Community Edition / MGNLCE-60 Remove "too many open files" startup check - if possible thanks to H2 Change By: Michael Mühlebach Story Points: 3 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] (CFGUI-45) Polish problems subapp
Title: Message Title Michael Mühlebach updated an issue Definitions app / CFGUI-45 Polish problems subapp Change By: Michael Mühlebach Story Points: 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] (MGNLWORKFLOW-339) Update Registries to new API
Title: Message Title Michael Mühlebach updated an issue Magnolia Workflow Module / MGNLWORKFLOW-339 Update Registries to new API Change By: Michael Mühlebach Story Points: 1 3 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] (DOCU-849) Downplay STK in 5.5 docs
Title: Message Title Julie Legendre created an issue Documentation / DOCU-849 Downplay STK in 5.5 docs Issue Type: Bug Assignee: Julie Legendre Created: 17/Oct/16 10:21 AM Fix Versions: 5.5 Priority: Neutral Reporter: Julie Legendre Security Level: Public Update MTE & STK page to become a MTE page Search and remove mentions of STK throughout doc in most places Notes from STK meeting 6/6/16 with topher: STK bundles will still be delivered. Existing customers (pre 5.4) will still have STK based templates and may migrate directly to 5.5 MTE & STK page to become a MTE page that: contains a brief paragraph about STK and points people to 5.4 doc for more info has a
[magnolia-dev] [JIRA] (CFGUI-11) Improve display of warnings and errors
Title: Message Title Michael Mühlebach updated an issue Definitions app / CFGUI-11 Improve display of warnings and errors Change By: Michael Mühlebach Story Points: 8 13 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] (MGNLUI-4027) Remove adminInterface-legacy module.
Title: Message Title Michael Mühlebach updated an issue Magnolia UI / MGNLUI-4027 Remove adminInterface-legacy module. Change By: Michael Mühlebach Sprint: Basel 65 66 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] (MGNLSITE-72) Add required configurationSourceType while adding theme by SiteModule
Title: Message Title Michael Mühlebach updated an issue Magnolia Site Module / MGNLSITE-72 Add required configurationSourceType while adding theme by SiteModule Change By: Michael Mühlebach Story Points: 1 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] (MGNLUI-2787) Get rid of MGWT from AdminCentral.
Title: Message Title Mikaël Geljić updated an issue Magnolia UI / MGNLUI-2787 Get rid of MGWT from AdminCentral. Change By: Mikaël Geljić Sprint: Saigon 65 66 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-4026) Site app's move dialog doesn't work correctly
Title: Message Title Mikaël Geljić updated an issue Magnolia UI / MGNLUI-4026 Site app's move dialog doesn't work correctly Change By: Mikaël Geljić Sprint: Saigon 65 66 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] (MGNLCE-45) Older profiles cannot download their artifacts
Title: Message Title Michael Mühlebach updated an issue Magnolia Community Edition / MGNLCE-45 Older profiles cannot download their artifacts Change By: Michael Mühlebach Sprint: Kromeriz 65 66 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] (MTE-3) Navigation features
Title: Message Title Michael Mühlebach updated an issue Magnolia Templating Essentials / MTE-3 Navigation features Change By: Michael Mühlebach Story Points: 8 13 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] (MGNLCE-45) Older profiles cannot download their artifacts
Title: Message Title Roman Kovařík updated an issue Magnolia Community Edition / MGNLCE-45 Older profiles cannot download their artifacts Change By: Roman Kovařík Summary: Profiles for older tomcats Older profiles cannot download their artifacts 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: