[magnolia-dev] [JIRA] (MGNLUI-4140) Remember last used folder
Title: Message Title Ervín Výstup updated an issue Magnolia UI / MGNLUI-4140 Remember last used folder Change By: Ervín Výstup Project: Magnolia DAM Module UI Key: MGNLDAM MGNLUI - 693 4140 Component/s: User Interaction 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-4139) Use favorites when choosing assets
Title: Message Title Ervín Výstup updated an issue Magnolia UI / MGNLUI-4139 Use favorites when choosing assets Change By: Ervín Výstup Project: Magnolia DAM Module UI Key: MGNLDAM MGNLUI - 694 4139 Component/s: favorites Component/s: User Interaction Affects Version/s: 2.2 Affects Version/s: 2.2.1 Add Comment This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)
[magnolia-dev] [JIRA] (MGNLREST-82) Can't install modules because of conflict on Weblogic with Jersey library
Title: Message Title Edwin Guilbert updated an issue Magnolia REST Framework / MGNLREST-82 Can't install modules because of conflict on Weblogic with Jersey library Change By: Edwin Guilbert Attachment: Jersey-conflict.log 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] (MGNLREST-82) Can't install modules because of conflict on Weblogic with Jersey library
Title: Message Title Edwin Guilbert updated an issue Magnolia REST Framework / MGNLREST-82 Can't install modules because of conflict on Weblogic with Jersey library Change By: Edwin Guilbert REST modules currently use [resteasy-jaxrs-3.0.19.Final |https://mvnrepository.com/artifact/org.jboss.resteasy/resteasy-jaxrs/3.0.19.Final]library which in turn uses jboss-jaxrs-api_2.0_spec.Weblogic 12.1.3 uses internally [jersey-bundle-1.9|https://mvnrepository.com/artifact/com.sun.jersey/jersey-bundle/1.9] and jsr311-api-1.1.1.The problem is that both libraries are having a conflict which prevents magnolia's war to deploy:{code:java}com.sun.jersey.spi.inject.Errors$ErrorMessagesException at com.sun.jersey.spi.inject.Errors.processErrorMessages(Errors.java:170) at com.sun.jersey.spi.inject.Errors.postProcess(Errors.java:136) at com.sun.jersey.spi.inject.Errors.processWithErrors(Errors.java:199) at com.sun.jersey.server.impl.application.WebApplicationImpl.initiate(WebApplicationImpl.java:795) at com.sun.jersey.server.impl.application.WebApplicationImpl.initiate(WebApplicationImpl.java:790){code}On previous versions of the REST modules (in Magnolia 5.4.x), [resteasy-jaxrs-3.0.4.Final|https://mvnrepository.com/artifact/org.jboss.resteasy/resteasy-jaxrs/3.0.4.Final] was being used which didnt didn't have any dependency with jboss-jaxrs-api_2.0_spec and didnt didn't have any conflicts deploying on Weblogic. Full log of the deploy issue attached Add Comment This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)
[magnolia-dev] [JIRA] (MGNLREST-82) Can't install modules because of conflict on Weblogic with Jersey library
Title: Message Title Edwin Guilbert created an issue Magnolia REST Framework / MGNLREST-82 Can't install modules because of conflict on Weblogic with Jersey library Issue Type: Bug Affects Versions: 1.2 Assignee: Unassigned Attachments: Jersey-conflict.log Created: 09/Feb/17 7:06 PM Environment: Weblogic 12.1.3 Magnolia 5.5.x Priority: Critical Reporter: Edwin Guilbert REST modules currently use resteasy-jaxrs-3.0.19.Final library which in turn uses jboss-jaxrs-api_2.0_spec. Weblogic 12.1.3 uses internally jersey-bundle-1.9 and jsr311-api-1.1.1. The problem is that both libraries are having a conflict which prevents magnolia's war to deploy: "Jersey" failed to preload on startup in Web application: "test-stk-webapp-1.0-SNAPSHOT.war". com.sun.jersey.spi.inject.Errors$ErrorMessagesException at com.sun.jersey.spi.inject.Errors.processErrorMessages(Errors.java:170) at com.sun.jersey.spi.inject.Errors.postProcess(Errors.java:136) at com.sun.jersey.spi.inject.Errors.processWithErrors(Errors.java:199) at com.sun.jersey.server.impl.application.WebApplicationImpl.initiate(WebApplicationImpl.java:795) at com.sun.jersey.server.impl.application.WebApplicationImpl.initiate(WebApplicationImpl.java:790) On previous versions of the REST modules (in Magnolia 5.4.x),
[magnolia-dev] [JIRA] (NPMCLI-99) Search for magnolia light-module packages on npm
Title: Message Title Christopher Zimmermann updated an issue Magnolia CLI npm module / NPMCLI-99 Search for magnolia light-module packages on npm Change By: Christopher Zimmermann Provide a command to search for light-module packages on npm.The search should only return packages which have the keyword "magnolia-light-module".{{mgnl search [search fragment ] }}*Rationale*Magnolia is promoting npm as the place to share light-modules. It should be easy to find packages on npm that are relevant based on a search term. 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-99) Search for magnolia light-module packages on npm
Title: Message Title Christopher Zimmermann created an issue Magnolia CLI npm module / NPMCLI-99 Search for magnolia light-module packages on npm Issue Type: New Feature Assignee: Unassigned Created: 09/Feb/17 4:03 PM Priority: Neutral Reporter: Christopher Zimmermann Provide a command to search for light-module packages on npm. The search should only return packages which have the keyword "magnolia-light-module". mgnl search [search fragment Rationale Magnolia is promoting npm as the place to share light-modules. It should be easy to find packages on npm that are relevant based on a search term. Add Comment This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)
[magnolia-dev] [JIRA] (NPMCLI-98) Get a light-module package from npm repository
Title: Message Title Christopher Zimmermann created an issue Magnolia CLI npm module / NPMCLI-98 Get a light-module package from npm repository Issue Type: New Feature Assignee: Unassigned Created: 09/Feb/17 3:57 PM Priority: Neutral Reporter: Christopher Zimmermann Provide a command to get one package by supplying its name. Maybe mgnl get [package name] Rationale Magnolia is promoting npm as the place to share light-modules. It should be easy and clean to get those modules. There are other more sophisticated approaches - such as via the "build" command. But there should be a way to just get a specific module. The npm install command does this, but has the downside of downloading it into a node_modules directory, this is clunky and could be confusing. Add Comment
[magnolia-dev] [JIRA] (MGNLUI-3678) No component edit bars (Chrome, hybrid touch device)
Title: Message Title Michael Mühlebach updated an issue Magnolia UI / MGNLUI-3678 No component edit bars (Chrome, hybrid touch device) Change By: Michael Mühlebach 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] (MGNLUI-4131) Prevent triggering actionbar actions twice by doubleclick
Title: Message Title Michael Mühlebach updated an issue Magnolia UI / MGNLUI-4131 Prevent triggering actionbar actions twice by doubleclick Change By: Michael Mühlebach Sprint: Basel 83 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-79) Light Project support
Title: Message Title Michael Mühlebach updated an issue Magnolia CLI npm module / NPMCLI-79 Light Project support Change By: Michael Mühlebach Sprint: Basel 83 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-79) Light Project support
Title: Message Title Michael Mühlebach updated an issue Magnolia CLI npm module / NPMCLI-79 Light Project support Change By: Michael Mühlebach Story Points: 5 Add Comment This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf) For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (NPMCLI-97) Copy light module
Title: Message Title Christopher Zimmermann created an issue Magnolia CLI npm module / NPMCLI-97 Copy light module Issue Type: New Feature Assignee: Unassigned Created: 09/Feb/17 2:51 PM Priority: Neutral Reporter: Christopher Zimmermann Command to copy light module including changing all old references in yaml and ftl files from original module name to new one. mgnl copy-light-module Not sure what the arguments would be. To specify. This would be a helpful timesaver. Add Comment This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)
[magnolia-dev] [JIRA] (MGNLFORUM-295) 3.6+ status is unclear
Title: Message Title Maxime Michel updated an issue Magnolia Forum Module / MGNLFORUM-295 3.6+ status is unclear Change By: Maxime Michel It is not clear to customers what the situation is with this module in current bundles, see SUPPORT-7226. The goal of this ticket is to try to remove as much config leftovers as possible. Ideally, only the JAR needed by commenting should be visible. Pointers from grooming:* do we only use code from forum, or also config, in commenting?* if we make it a JAR and remove the MD => how can commenting check that it's here or not?* should we release a new commenting major version with the code forum needs included? 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-4115) Prevent two-time validation at dialogs
Title: Message Title Zdenek Skodik updated an issue Magnolia UI / MGNLUI-4115 Prevent two-time validation at dialogs Change By: Zdenek Skodik At the moment we execute a validator twice, the second validation is being done by {{info.magnolia.ui.dialog.actionarea.renderer.DefaultEditorActionRenderer}} that checks the validity for the sake of re-enabling commit/save button in order to prevent multiple savings. This Also the validation is being done for each language. All this can be quite an expensive operation, especially if you have a validator doing remote calls. 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] (MGNLFORUM-295) 3.6+ status is unclear
Title: Message Title Michael Mühlebach updated an issue Magnolia Forum Module / MGNLFORUM-295 3.6+ status is unclear Change By: Michael Mühlebach Story Points: 5 Add Comment This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf) For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] (DOCU-934) Disabling activation workflow - add a note for personalization
Title: Message Title Christoph Meier updated an issue Documentation / DOCU-934 Disabling activation workflow - add a note for personalization Change By: Christoph Meier Assignee: Christoph Meier 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-4136) Finalize pure-Vaadin Composite field
Title: Message Title Oanh Thai Hoang updated an issue Magnolia UI / MGNLUI-4136 Finalize pure-Vaadin Composite field Change By: Oanh Thai Hoang Original Estimate: 4d Remaining Estimate: 4d 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] (MGNLFORUM-295) 3.6+ status is unclear
Title: Message Title Maxime Michel created an issue Magnolia Forum Module / MGNLFORUM-295 3.6+ status is unclear Issue Type: Task Affects Versions: 3.6.1, 3.6 Assignee: Unassigned Created: 09/Feb/17 11:18 AM Priority: Neutral Reporter: Maxime Michel It is not clear to customers what the situation is with this module in current bundles, see SUPPORT-7226. The goal of this ticket is to try to remove as much config leftovers as possible. Ideally, only the JAR needed by commenting should be visible. Add Comment
[magnolia-dev] [JIRA] (MGNLUI-4138) Validation bubbles as JavaScriptExtension
Title: Message Title Hieu Nguyen Duc updated an issue Magnolia UI / MGNLUI-4138 Validation bubbles as _javascript_Extension Change By: Hieu Nguyen Duc Original Estimate: 5d Remaining Estimate: 5d 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: