[magnolia-dev] Re: Help needed to clean up repository/delete unwanted nodes
Good question, Vikram! That would make a good wiki article. And while the jackrabbit experts out there answer it, you could also explain how to delete old / unwanted versions (which I think would be better than turning off versioning completely)? Thanks, -will -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=29e31b61-c16d-460e-9162-3356751320f7 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] (MGNLUI-2991) Add one additional icon for to icon font
Christoph Meier updated MGNLUI-2991 Add one additional icon for to icon font Change By: Christoph Meier (28/Aug/14 12:05 PM) Assignee: ChristophMeier This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html Alternatively,useourforums:http://forum.magnolia-cms.com/ Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] (MGNLUI-3127) Provide a rich tooltip component
Federico Grilli created MGNLUI-3127 Provide a rich tooltip component Issue Type: Task Assignee: Unassigned Created: 28/Aug/14 3:36 PM Description: In soft locking (and possibly other modules too) we need a tooltip displaying users currently editing the same page and other info (see related issue and mockups) I first tried several approaches: rich tooltip (setting an HTML description for the relevant Vaadin component): can't be used because wouldn't work on tablets ContextMenu: hard to style PopupView: when it opens it covers its icon, by default can't be opened in a different position Extending Vaadin's PopupView looks like the best option as it is the closest thing to what we want to achieve. However, the client side needs some modification in order to get the correct positioning. Also the animation should be off. Project: Magnolia UI Priority: Major Reporter: Federico Grilli Security Level: Public This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html Alternatively,useourforums:http://forum.magnolia-cms.com/ Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] (MGNLWORKFLOW-270) Failed and resolved tasks can't be deleted / removed from list
Isabelle Dubach created MGNLWORKFLOW-270 Failed and resolved tasks cant be deleted / removed from list Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2014-08-28 at 4.17.01 PM.png Created: 28/Aug/14 4:18 PM Description: In the Pulse, failed and resolved tasks can't be completed. This is an issue because it's likely that they're taken care of somewhere else (in a different task, when retrying to publish, for example), and thus become irrelevant. Project: Magnolia Workflow Module Priority: Neutral Reporter: Isabelle Dubach This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html Alternatively,useourforums:http://forum.magnolia-cms.com/ Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] (MGNLWORKFLOW-271) Bulk actions don't make sense
Isabelle Dubach created MGNLWORKFLOW-271 Bulk actions dont make sense Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2014-08-28 at 4.18.55 PM.png Created: 28/Aug/14 4:20 PM Description: In Assigned and Resolved categories, for example, I can bulk-assign them to me. This doesn't make sense - if they're assigned, I don't want to assign them again, and if they're resolved, I don't need to act on them at all (except for deletion, which is not possible, see issue http://jira.magnolia-cms.com/browse/MGNLWORKFLOW-270. It would be be great if bulk actions would be relevant to the context. Project: Magnolia Workflow Module Priority: Neutral Reporter: Isabelle Dubach This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html Alternatively,useourforums:http://forum.magnolia-cms.com/ Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] (MGNLUI-3128) DefaultI18NAuthoringSupport: fallbackLocale provided in scope of pages app's editor is always from default site definiton
Christian Ringele created MGNLUI-3128 DefaultI18NAuthoringSupport: fallbackLocale provided in scope of pages apps editor is always from default site definiton Issue Type: Bug Affects Versions: 5.3.2 Assignee: Unassigned Attachments: fallbackLocal.jpg Components: dialogs, page editor Created: 28/Aug/14 11:00 PM Description: This issue is very related to MULTISITE-22, it's is follow up. The described behavior was also detected on the defaultLocale (MULTISITE-22). Description: When changing in a specific site definition the defaultLocale the fallbackLocale, the already stored content should appear in a dialog. This is not the case because the fallbackLocale is still served from the "default" site definition, see print screen fallbackLocal.jpg. (MULTISITE-22) corrected that the defaultLocale is set correctly and the dialog opens in the default locale (in this case "de") from the specific site definition, but because the fallbackLocale(en) != defaultLocale(de) the dialog still want to edit a property with "_en" appended to its name. There fore the dialog is empty, and if entering content it will store a "%propertyName_fallsbackLocale%" property. Reason: In info.magnolia.ui.framework.i18n.DefaultI18NAuthoringSupport.i18nize(HasComponents, Locale) the locale provided as the parameter is the correct defaultLocal. But in this code: boolean isFallbackLanguage = i18nContentSupport.getFallbackLocale().equals(locale); The provided fallbackLocal from i18nContentSupport (Object=MultiSiteI18nAuthoringSupport) is from the "default" site definition (set in MultiSiteFilter). This because the detected site definition in the scope of the pages app is not the actual specific site definition from the edited page (different requests). (same problem as in MULTISITE-22) Tried solution: I tried to create also a node dependent getFallbackLocale(Node node) method for MultiSiteI18nAuthoringSupport DefaultI18nAuthoringSupport as done in the MULTISITE-22 for the defaultLocale. The problem is that in the calling class of the method DefaultI18NAuthoringSupport#i18nize is the dialogs view: info.magnolia.ui.dialog.formdialog.ItemFormView.createLocaleSelector() I haven't found a way to retrieve the content the DialogView operates on. Which could be well intended by the MVP pattern. A different solution might has to be found. Project: Magnolia UI Labels: support Priority: Major Reporter: Christian Ringele This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html Alternatively,useourforums:http://forum.magnolia-cms.com/ Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] (MGNLUI-3128) DefaultI18NAuthoringSupport: fallbackLocale is always from default site definiton in pages app.
Christian Ringele updated MGNLUI-3128 DefaultI18NAuthoringSupport: fallbackLocale is always from default site definiton in pages app. Change By: Christian Ringele (28/Aug/14 11:10 PM) Summary: DefaultI18NAuthoringSupport:fallbackLocale providedinscopeofpagesappseditor isalwaysfromdefaultsitedefiniton inpagesapp. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html Alternatively,useourforums:http://forum.magnolia-cms.com/ Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] (MGNLUI-3128) DefaultI18NAuthoringSupport: fallbackLocale is in pages app always from default site definiton.
Christian Ringele updated MGNLUI-3128 DefaultI18NAuthoringSupport: fallbackLocale is in pages app always from default site definiton. Change By: Christian Ringele (28/Aug/14 11:11 PM) Summary: DefaultI18NAuthoringSupport:fallbackLocaleis inpagesapp alwaysfromdefaultsitedefiniton inpagesapp . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html Alternatively,useourforums:http://forum.magnolia-cms.com/ Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] Re: Help needed to clean up repository/delete unwanted nodes
Thanks Will An update on this: I rechecked and can confirm that my app does not use versioning. Also the versions workspace is quite small. So the issue isn't related to versioning. Could anyone suggest other options/reasons for why this might not be working? -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=29e31b61-c16d-460e-9162-3356751320f7 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: dev-list-unsubscr...@magnolia-cms.com
