[magnolia-dev] AUTO: Marc Bechtiger is out of the office. (returning 02.01.2013)
I am out of the office until 02.01.2013. I will respond to your message when I return. Note: This is an automated response to your message [magnolia-dev] [JIRA] Updated: (MAGNOLIA-4413) GZip filter breaks cached forms in chrome: strange binary content at bottom sent on 17.12.2012 08:53:27. This is the only notification you will receive while this person is away. 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] i18nBasename in 4.5.6
Dear all, i follow this instruction for having my own key in the jsp.
http://documentation.magnolia-cms.com/technical-guide/i18n.html#Templatescripts
But each time the result is ???mykey???.
I have done the following operation.
1) crate a pagacke in my module which contains the messages_fr.properties (es
: com.ditta.ss.messages)
2) In the template definition module/mymodule/templates/pages/mytemplate/ i
creted the property : i18nBasename with the value the name of the package in
the project (com.ditta.ss.messages)
3) I the jsp
[code]
fmt:setBundle var=x basename=com.ditta.ss.messages /
fmt:message bundle=${x} key=test/[/code]
Any help would be appreciated.
Thanks a lot !!
AT
--
Context is everything:
http://forum.magnolia-cms.com/forum/thread.html?threadId=13019597-7b26-46a3-b9f9-046d1211cecf
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] Re: i18nBasename in 4.5.6
Found solution :) If you configure in your template a i18nBasename com.ditta.ss.messages, you have to put the messages_en.properties in the package com.ditta.ss . This is in relatione to the canonical name of java classes. -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=13019597-7b26-46a3-b9f9-046d1211cecf 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] Created: (MAGNOLIA-4731) wrong layout on edit bar when component html use floating
wrong layout on edit bar when component html use floating
-
Key: MAGNOLIA-4731
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4731
Project: Magnolia
Issue Type: Bug
Security Level: Public
Components: admininterface
Affects Versions: 4.5.6
Reporter: Mike Wilson
Attachments: mgnl456-layoutbug-fixed.png, mgnl456-layoutbug.png
See attached screenshots and look at the edit bar for the second component.
The second image fixes the layout problem by adding:
{code}
div.mgnlEditorBar.component, .mgnlEditorBar.placeholder {
clear: both;
}
{code}
to CSS.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
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] Updated: (MAGNOLIA-4731) wrong layout on edit bar when component html use floating
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Wilson updated MAGNOLIA-4731:
--
Description:
See attached screenshots and look at the edit bar for the second component.
The fixed image fixes the layout problem by adding:
{code}
div.mgnlEditorBar.component, .mgnlEditorBar.placeholder {
clear: both;
}
{code}
to CSS.
was:
See attached screenshots and look at the edit bar for the second component.
The second image fixes the layout problem by adding:
{code}
div.mgnlEditorBar.component, .mgnlEditorBar.placeholder {
clear: both;
}
{code}
to CSS.
wrong layout on edit bar when component html use floating
-
Key: MAGNOLIA-4731
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4731
Project: Magnolia
Issue Type: Bug
Security Level: Public
Components: admininterface
Affects Versions: 4.5.6
Reporter: Mike Wilson
Attachments: mgnl456-layoutbug-fixed.png, mgnl456-layoutbug.png
See attached screenshots and look at the edit bar for the second component.
The fixed image fixes the layout problem by adding:
{code}
div.mgnlEditorBar.component, .mgnlEditorBar.placeholder {
clear: both;
}
{code}
to CSS.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
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] Created: (MAGNOLIA-4732) There is no utility methos that returns all the properties that are not special, needed when you dont know the name of the properties you want to displ
There is no utility methos that returns all the properties that are not special, needed when you dont know the name of the properties you want to display -- Key: MAGNOLIA-4732 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4732 Project: Magnolia Issue Type: Improvement Security Level: Public Components: core Affects Versions: 4.5.7 Reporter: Teresa Miyar Priority: Major Either content.getProperties() and contentMap.keyset return all the properties in the node, including the special properties. In the previous API you could call getProperties and it would return all the non special properties. This is needed i.e. multiselect control, when you get the properties as 0,1... you dont know the names. One way could be to prefix this names with the node name like link0, link1 this way you could get all the properties that start with 'link', and the other way would be to provide a method that returns just the non special properties. Have a look at current method contentMap.keyset, it returns all the properties special an non special and also the special prefixed with @ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Re: mgnl 4.5.x how to use MyMessagesManager instead of DefaultMessagesManager?
Hi Fabrizio, I can't reproduce this problem. I've used the same xml snippet, although a different replacement implementation and I get the init() call from ConfigLoader. Could you file a ticket for this with the exact version where you're seeing the problem? // Tobias -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=23d7fd89-dedd-450e-9e77-c741088713fd 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] Created: (MAGNOLIA-4733) Create a generic PropertyFilteringNodeWrapper that filter property.
Create a generic PropertyFilteringNodeWrapper that filter property. --- Key: MAGNOLIA-4733 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4733 Project: Magnolia Issue Type: Task Security Level: Public Components: core Affects Versions: 5.0 Alpha1 Reporter: Eric Hechinger Assignee: Eric Hechinger Fix For: 5.0 Alpha2 s011 Create a PropertyFilteringNodeWrapper that filter Properties associated to a node that pass the following Predicate: Property.getString() equals the constructor value. If the value is set to null, properties with null value will be returned. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Updated: (MGNLUI-37) Make AbstractJcrContainer implement com.vaadin.data.Filterable.
[ http://jira.magnolia-cms.com/browse/MGNLUI-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Lipp updated MGNLUI-37: -- Assignee: (was: Daniel Lipp) Make AbstractJcrContainer implement com.vaadin.data.Filterable. --- Key: MGNLUI-37 URL: http://jira.magnolia-cms.com/browse/MGNLUI-37 Project: Magnolia UI Issue Type: Task Security Level: Public Reporter: Aleksandr Pchelintcev Priority: Major Fix For: 5.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Created: (MSHOP-53) Warenkorb löschen
Warenkorb löschen - Key: MSHOP-53 URL: http://jira.magnolia-cms.com/browse/MSHOP-53 Project: Magnolia Shop Issue Type: Improvement Affects Versions: 1.1, 1.0.9 Reporter: Dominik Berger Assignee: Will Scheidegger Momentan kann der Warenkorb nicht als ganzes gelöscht werden. Die Shopping Cart View sollte um den Butten Delete all ergänzt werden. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Created: (MGNLMIGRATION-193) Pages marked as deleted are not migrated properly
Pages marked as deleted are not migrated properly
-
Key: MGNLMIGRATION-193
URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-193
Project: Magnolia Migration
Issue Type: Bug
Reporter: Zdenek Skodik
The {{mgnl:template}} property is not updated to the new
{{adminInterface:mgnlDeleted}} notation thus the assigned template can't be
resolved.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
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] Created: (MSHOP-54) Anzahl in den Warenkorb Feld Verbesserung
Anzahl in den Warenkorb Feld Verbesserung - Key: MSHOP-54 URL: http://jira.magnolia-cms.com/browse/MSHOP-54 Project: Magnolia Shop Issue Type: Improvement Reporter: Dominik Berger Assignee: Will Scheidegger Anzahl 0 im Warenkorb wird als 1 Produkt gewertet * wenn ich zwei eingebe wird das als 1 produkt gewertet? ** validation einbauen, nur numerischer Wert erlauben, min/max/LotSize angeben ** oder einsetzen einer Combobox? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Updated: (MGNLSTK-1055) Diff and version view does not show uploaded images
[ http://jira.magnolia-cms.com/browse/MGNLSTK-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kovařík updated MGNLSTK-1055: --- Attachment: STKParameterProvider.patch Diff and version view does not show uploaded images --- Key: MGNLSTK-1055 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1055 Project: Magnolia Standard Templating Kit Issue Type: Bug Affects Versions: 2.0.7 Reporter: Frank Sommer Assignee: Roman Kovařík Fix For: 2.0.8 Attachments: diff-uploaded-images.png, STKParameterProvider.patch Uploaded images in your versioned page nodes were not displayed. Except images delivered by the STK imaging module. This images are displayed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Updated: (MAGNOLIA-4731) wrong layout on edit bar when component html use floating
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Haderka updated MAGNOLIA-4731:
--
Fix Version/s: 4.5.8
wrong layout on edit bar when component html use floating
-
Key: MAGNOLIA-4731
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4731
Project: Magnolia
Issue Type: Bug
Security Level: Public
Components: admininterface
Affects Versions: 4.5.6
Reporter: Mike Wilson
Fix For: 4.5.8
Attachments: mgnl456-layoutbug-fixed.png, mgnl456-layoutbug.png
See attached screenshots and look at the edit bar for the second component.
The fixed image fixes the layout problem by adding:
{code}
div.mgnlEditorBar.component, .mgnlEditorBar.placeholder {
clear: both;
}
{code}
to CSS.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
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] Created: (MAGNOLIA-4734) Wrong layout on edit bar when component html use floating
Wrong layout on edit bar when component html use floating
-
Key: MAGNOLIA-4734
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4734
Project: Magnolia
Issue Type: Bug
Security Level: Public
Components: admininterface
Affects Versions: 4.5.6
Reporter: Mike Wilson
Fix For: 4.5.8
See attached screenshots and look at the edit bar for the second component.
The fixed image fixes the layout problem by adding:
{code}
div.mgnlEditorBar.component, .mgnlEditorBar.placeholder {
clear: both;
}
{code}
to CSS.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
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] Deleted: (MAGNOLIA-4734) Wrong layout on edit bar when component html use floating
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zdenek Skodik deleted MAGNOLIA-4734:
Wrong layout on edit bar when component html use floating
-
Key: MAGNOLIA-4734
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4734
Project: Magnolia
Issue Type: Bug
Security Level: Public
Reporter: Mike Wilson
See attached screenshots and look at the edit bar for the second component.
The fixed image fixes the layout problem by adding:
{code}
div.mgnlEditorBar.component, .mgnlEditorBar.placeholder {
clear: both;
}
{code}
to CSS.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
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] Created: (MGNLDAM-66) Remove use of term 'value picker' in variables names and comments
Remove use of term 'value picker' in variables names and comments - Key: MGNLDAM-66 URL: http://jira.magnolia-cms.com/browse/MGNLDAM-66 Project: Magnolia DAM Module Issue Type: Task Reporter: Tobias Mattsson Fix For: 1.0 Alpha2 s011 There are still references in the code using the old name 'value picker' for the chose dialog. For instance: Value Picker Dialog / workbenchPickerDialogPresenter / ValuePickListener / pickerView. Doing a file search for 'pick' gives me 43 hits that should be changed. Please do a more thorough search than this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Updated: (MGNLUI-396) Location interface is too generic
[ http://jira.magnolia-cms.com/browse/MGNLUI-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Espen Jervidalo updated MGNLUI-396: --- Summary: Location interface is too generic (was: AbstractSubApp: getCurrentLocation should return DefaultLocation) Description: Currently the Location interface is too generic, resulting in casts to DefaultLocation throughout the framework. This can be easily fixed by making the interface more specific. move constants into interface will also get rid of some unnecessary imports. was:This will ease location handling in implementers of this Class. Currently the Location-Interface is returned and one has to cast to get the right getters. moving the DefaultLocations getters to the interface may also be a solution. Location interface is too generic - Key: MGNLUI-396 URL: http://jira.magnolia-cms.com/browse/MGNLUI-396 Project: Magnolia UI Issue Type: Task Security Level: Public Components: app framework Affects Versions: 5.0 Alpha1 Reporter: Espen Jervidalo Assignee: Espen Jervidalo Fix For: 5.0 Alpha2 s011 Currently the Location interface is too generic, resulting in casts to DefaultLocation throughout the framework. This can be easily fixed by making the interface more specific. move constants into interface will also get rid of some unnecessary imports. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Created: (MGNLUI-432) SubAppEventBusConfigurer and AppEventBusConfigurer should not reside in event package
SubAppEventBusConfigurer and AppEventBusConfigurer should not reside in event package -- Key: MGNLUI-432 URL: http://jira.magnolia-cms.com/browse/MGNLUI-432 Project: Magnolia UI Issue Type: Bug Security Level: Public Components: app framework Reporter: Tobias Mattsson Fix For: 5.0 Alpha2 s011 They should actually be part of the app api implementation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Reopened: (MGNLUI-377) Action bar has corrupted layout during app switch transition.
[ http://jira.magnolia-cms.com/browse/MGNLUI-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Zimmermann reopened MGNLUI-377: --- It works in my testing but we must prevent that: User may witness switching app flicking shortly before the animation. How about this? * Create a new CSS class zoomed-out which has scale 0 (or 0.0001) but no animation. * Apply it immediately before viewport.doSetVisibleApp(app). The vaadin size calculation should work then, and it would not be possible to see the app before the deferred animation started. Then I think it would be fare to remove the this is a hack comment. Or do you feel there is a more proper approach. Action bar has corrupted layout during app switch transition. - Key: MGNLUI-377 URL: http://jira.magnolia-cms.com/browse/MGNLUI-377 Project: Magnolia UI Issue Type: Bug Security Level: Public Affects Versions: 5.0 Alpha1 Reporter: Christopher Zimmermann Assignee: Samuli Penttilä Priority: Critical Fix For: 5.0 Alpha2 s011 This is a followup ticket to MGNLUI-352. The layout does look good when transition is complete. But it looks bad that the actionbar is gone during the transition and then pops into view. It should be visible the whole time in the state that the user left it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Updated: (MAGNOLIA-4735) System wide event bus
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Mattsson updated MAGNOLIA-4735: -- Summary: System wide event bus (was: System event bus should be in magnolia-core) Description: We currently have a system wide event bus developed for the new UI and up til now it has only been used for UI related events. Going forward this should be part of magnolia-core and be provided as a facility for any code that would benefit from sending or listening to a system wide event. Component/s: core System wide event bus - Key: MAGNOLIA-4735 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4735 Project: Magnolia Issue Type: New Feature Security Level: Public Components: core Reporter: Tobias Mattsson Fix For: 5.0 Alpha2 s011 We currently have a system wide event bus developed for the new UI and up til now it has only been used for UI related events. Going forward this should be part of magnolia-core and be provided as a facility for any code that would benefit from sending or listening to a system wide event. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Updated: (MAGNOLIA-4735) System wide event bus
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Mattsson updated MAGNOLIA-4735: -- Description: We currently have a system wide event bus developed for the new UI and up til now it has only been used for UI related events. Going forward this should be part of magnolia-core and be provided as a facility for any code that would benefit from sending or listening to a system wide event. The changes I have in mind is moving the following classes from ui-framework to magnolia-core and the package info.magnolia.event: * info.magnolia.ui.framework.event.Event * info.magnolia.ui.framework.event.EventBus * info.magnolia.ui.framework.event.EventHandler * info.magnolia.ui.framework.event.EventHandlerCollection * info.magnolia.ui.framework.event.HandlerRegistration * info.magnolia.ui.framework.event.ResettableEventBus * info.magnolia.ui.framework.event.SimpleEventBus * info.magnolia.ui.framework.event.SystemEventBusConfigurer Configuration of the system wide event bus would also move from the ui-admincentral module to the core module. Q: The system event bus is configured in the _main_ component provider. Which isn't necessarily a problem or even particularly confusing. It can become a problem though should the need for an EventBus specific to the system component provider be necessary later on. was: We currently have a system wide event bus developed for the new UI and up til now it has only been used for UI related events. Going forward this should be part of magnolia-core and be provided as a facility for any code that would benefit from sending or listening to a system wide event. System wide event bus - Key: MAGNOLIA-4735 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4735 Project: Magnolia Issue Type: New Feature Security Level: Public Components: core Reporter: Tobias Mattsson Fix For: 5.0 Alpha2 s011 We currently have a system wide event bus developed for the new UI and up til now it has only been used for UI related events. Going forward this should be part of magnolia-core and be provided as a facility for any code that would benefit from sending or listening to a system wide event. The changes I have in mind is moving the following classes from ui-framework to magnolia-core and the package info.magnolia.event: * info.magnolia.ui.framework.event.Event * info.magnolia.ui.framework.event.EventBus * info.magnolia.ui.framework.event.EventHandler * info.magnolia.ui.framework.event.EventHandlerCollection * info.magnolia.ui.framework.event.HandlerRegistration * info.magnolia.ui.framework.event.ResettableEventBus * info.magnolia.ui.framework.event.SimpleEventBus * info.magnolia.ui.framework.event.SystemEventBusConfigurer Configuration of the system wide event bus would also move from the ui-admincentral module to the core module. Q: The system event bus is configured in the _main_ component provider. Which isn't necessarily a problem or even particularly confusing. It can become a problem though should the need for an EventBus specific to the system component provider be necessary later on. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Updated: (MGNLUI-405) Simplify app registration events
[ http://jira.magnolia-cms.com/browse/MGNLUI-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Mattsson updated MGNLUI-405: --- Description: AppDescriptorRegistry performs checks on the app providers it has registered in order to send very fine grained events. It relies on providers implementing the equals method to compare them as they are registered. These fine grained events are all processed identically and so don't seem to be necessary. Simplifying this would mean that we instead of firing REGISTERED,REREGISTERED,UNREGISTERED would fire a single event meaning that the set of app descriptors has changed. This concerns the classes: * info.magnolia.ui.framework.app.registry.AppDescriptorRegistry * info.magnolia.ui.framework.app.registry.AppRegistryEvent * info.magnolia.ui.framework.app.registry.AppRegistryEventType * info.magnolia.ui.framework.app.registry.AppRegistryEventHandler was:AppDescriptorRegistry performs checks on the app providers it has registered in order to send very fine grained events. It relies on providers implementing the equals method to compare them as they are registered. These fine grained events are all processed identically and so don't seem to be necessary. Simplify app registration events Key: MGNLUI-405 URL: http://jira.magnolia-cms.com/browse/MGNLUI-405 Project: Magnolia UI Issue Type: Task Security Level: Public Components: app framework Reporter: Tobias Mattsson Fix For: 5.0 Alpha2 s011 AppDescriptorRegistry performs checks on the app providers it has registered in order to send very fine grained events. It relies on providers implementing the equals method to compare them as they are registered. These fine grained events are all processed identically and so don't seem to be necessary. Simplifying this would mean that we instead of firing REGISTERED,REREGISTERED,UNREGISTERED would fire a single event meaning that the set of app descriptors has changed. This concerns the classes: * info.magnolia.ui.framework.app.registry.AppDescriptorRegistry * info.magnolia.ui.framework.app.registry.AppRegistryEvent * info.magnolia.ui.framework.app.registry.AppRegistryEventType * info.magnolia.ui.framework.app.registry.AppRegistryEventHandler -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Updated: (MAGNOLIA-4564) Implement export in info.magnolia.jcr.util.PropertiesImportExport
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Mattsson updated MAGNOLIA-4564: -- Fix Version/s: 5.0 Alpha2 s011 (was: 5.0) Implement export in info.magnolia.jcr.util.PropertiesImportExport - Key: MAGNOLIA-4564 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4564 Project: Magnolia Issue Type: Task Security Level: Public Components: core Affects Versions: 5.0 Reporter: Daniel Lipp Fix For: 5.0 Alpha2 s011 info.magnolia.jcr.util.PropertiesImportExport (JCR-API based) is meant to replace info.magnolia.importexport.PropertiesImportExport (Content-API based). Right now export is not yet implemented for the new one. As soon as this is done the old one should get deprecated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Created: (MAGNOLIA-4736) New style properties in MetaData node should not prevent it from being removed
New style properties in MetaData node should not prevent it from being removed -- Key: MAGNOLIA-4736 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4736 Project: Magnolia Issue Type: Bug Security Level: Public Reporter: Tobias Mattsson Assignee: Tobias Mattsson Priority: Major Fix For: 5.0 Alpha2 s011 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Created: (MGNLUI-435) Port Dialogs/Forms to Vaadin7
Port Dialogs/Forms to Vaadin7 - Key: MGNLUI-435 URL: http://jira.magnolia-cms.com/browse/MGNLUI-435 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Affects Versions: 5.0 Alpha2 s011 Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev Priority: Critical Fix For: 5.0 Alpha2 s011 Port Dialogs/Forms to Vaadin7. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Created: (MGNLUI-437) Port AppLauncher to Vaadin7
Port AppLauncher to Vaadin7 --- Key: MGNLUI-437 URL: http://jira.magnolia-cms.com/browse/MGNLUI-437 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Affects Versions: 5.0 Alpha2 s011 Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev Priority: Critical Fix For: 5.0 Alpha2 s011 Port AppLauncher to Vaadin7 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Created: (MGNLUI-436) Port Actionbar to Vaadin7
Port Actionbar to Vaadin7 - Key: MGNLUI-436 URL: http://jira.magnolia-cms.com/browse/MGNLUI-436 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Affects Versions: 5.0 Alpha2 s011 Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev Priority: Critical Fix For: 5.0 Alpha2 s011 Port Actionbar to Vaadin7 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Created: (MGNLUI-433) Port MagnoliaShell to Vaadin7
Port MagnoliaShell to Vaadin7 - Key: MGNLUI-433 URL: http://jira.magnolia-cms.com/browse/MGNLUI-433 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Affects Versions: 5.0 Alpha2 s011 Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev Priority: Critical Fix For: 5.0 Alpha2 s011 Port MagnoliaShell to Vaadin7 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Created: (MGNLUI-434) Port MagnoliaTabSheet to Vaadin7
Port MagnoliaTabSheet to Vaadin7 Key: MGNLUI-434 URL: http://jira.magnolia-cms.com/browse/MGNLUI-434 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Affects Versions: 5.0 Alpha2 s011 Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev Priority: Critical Fix For: 5.0 Alpha2 s011 Port MagnoliaTabSheet to Vaadin7. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Created: (MGNLUI-440) Update Vaadin table patch for Vaadin7
Update Vaadin table patch for Vaadin7 - Key: MGNLUI-440 URL: http://jira.magnolia-cms.com/browse/MGNLUI-440 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Affects Versions: 5.0 Alpha2 s011 Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev Priority: Critical Fix For: 5.0 Alpha2 s011 Update Vaadin table patch for Vaadin7 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Created: (MGNLUI-439) Create solution for CKEditor and Vaadin7.
Create solution for CKEditor and Vaadin7. - Key: MGNLUI-439 URL: http://jira.magnolia-cms.com/browse/MGNLUI-439 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Affects Versions: 5.0 Alpha2 s011 Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev Priority: Critical Fix For: 5.0 Alpha2 s011 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Created: (MGNLUI-441) Update Vaadin version in the project to 7
Update Vaadin version in the project to 7 - Key: MGNLUI-441 URL: http://jira.magnolia-cms.com/browse/MGNLUI-441 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Affects Versions: 5.0 Alpha2 s011 Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev Priority: Critical Fix For: 5.0 Alpha2 s011 Update Vaadin versions in pom files, remove GWT dependencies, set up vaadin-maven plugin instead of gwt-maven plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Created: (MGNLUI-438) Port PagesEditor to Vaadin7.
Port PagesEditor to Vaadin7. Key: MGNLUI-438 URL: http://jira.magnolia-cms.com/browse/MGNLUI-438 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Affects Versions: 5.0 Alpha2 s011 Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev Priority: Critical Fix For: 5.0 Alpha2 s011 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Created: (MGNLUI-442) Convert current multiple browser tabs support solution with an out-of-the-box solution from Vaadin7
Convert current multiple browser tabs support solution with an out-of-the-box solution from Vaadin7 --- Key: MGNLUI-442 URL: http://jira.magnolia-cms.com/browse/MGNLUI-442 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Affects Versions: 5.0 Alpha2 s011 Reporter: Aleksandr Pchelintcev Priority: Critical Fix For: 5.0 Alpha2 s011 Convert current multiple browser tabs support solution with an out-of-the-box solution from Vaadin7 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Updated: (MGNLWORKFLOW-18) Empty nodes of finished workflow still exist (Expressions workspace)
[ http://jira.magnolia-cms.com/browse/MGNLWORKFLOW-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Antener updated MGNLWORKFLOW-18: Attachment: JCRExpressionStoreCleanupTest.java patch.diff Attached test case and patch. There is a problem with the use of org.apache.jackrabbit.commons.iterator.FilteringNodeIterator in info.magnolia.module.workflow.jcr.JCRExpressionStore#deleteAndRemoveEmptyParents The check on size()==0 cannot work because the implementation of this filtering node iterator always returns -1. It is explained in javax.jcr.RangeIterator#getSize Cheers Andy Empty nodes of finished workflow still exist (Expressions workspace) Key: MGNLWORKFLOW-18 URL: http://jira.magnolia-cms.com/browse/MGNLWORKFLOW-18 Project: Magnolia Workflow Module Issue Type: Bug Environment: Magnolia EE 4.5.6, Tomcat 7, Java 6, OS X Reporter: Andreas Antener Priority: Minor Fix For: 1.0 Alpha2 s011 Attachments: expressions.txt, JCRExpressionStoreCleanupTest.java, libs.txt, magnolia-debug.log, patch.diff The nodes in the Expressions workspace won't get deleted after a finished workflow. Steps to reproduce: - Start Magnolia (public and author) with workflow module, no repositories yet - Login with superuser - Create a page - Activate that page - Go to inbox and proceed with the activation - Check the Expressions workspace under /owfe/activation There I have 2 empty nodes now. See attachments for debug-log, libs and listing from JCR query. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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] Updated: (MAGNOLIA-4737) Empty nodes of finished workflow still exist (Expressions workspace)
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka updated MAGNOLIA-4737: -- Affects Version/s: 4.5.6 Empty nodes of finished workflow still exist (Expressions workspace) Key: MAGNOLIA-4737 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4737 Project: Magnolia Issue Type: Bug Security Level: Public Affects Versions: 4.5.6 Environment: Magnolia EE 4.5.6, Tomcat 7, Java 6, OS X Reporter: Andreas Antener Priority: Minor Fix For: 4.5.8 Attachments: expressions.txt, JCRExpressionStoreCleanupTest.java, libs.txt, magnolia-debug.log, patch.diff The nodes in the Expressions workspace won't get deleted after a finished workflow. Steps to reproduce: - Start Magnolia (public and author) with workflow module, no repositories yet - Login with superuser - Create a page - Activate that page - Go to inbox and proceed with the activation - Check the Expressions workspace under /owfe/activation There I have 2 empty nodes now. See attachments for debug-log, libs and listing from JCR query. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira 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
