[magnolia-dev] [JIRA] Reopened: (MGNLUI-502) Pulse shellap only opens the second time you click on the icon.
[ http://jira.magnolia-cms.com/browse/MGNLUI-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Lipp reopened MGNLUI-502: There's not commits on this ticket. Pls provide some information on how this ticket was fixed. Pulse shellap only opens the second time you click on the icon. --- Key: MGNLUI-502 URL: http://jira.magnolia-cms.com/browse/MGNLUI-502 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Components: pulse Affects Versions: 5.0 Alpha2 s011 Reporter: Christopher Zimmermann Assignee: Aleksandr Pchelintcev Fix For: 5.0 Alpha2 s011 The first time you click on pulse shell app icon, nothing appears to happen. From then on, when you click on it, it loads properly. -- 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-502) Pulse shellap only opens the second time you click on the icon.
[ http://jira.magnolia-cms.com/browse/MGNLUI-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Lipp updated MGNLUI-502: --- Comment: was deleted (was: There's not commits on this ticket. Pls provide some information on how this ticket was fixed.) Pulse shellap only opens the second time you click on the icon. --- Key: MGNLUI-502 URL: http://jira.magnolia-cms.com/browse/MGNLUI-502 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Components: pulse Affects Versions: 5.0 Alpha2 s011 Reporter: Christopher Zimmermann Assignee: Aleksandr Pchelintcev Fix For: 5.0 Alpha2 s011 The first time you click on pulse shell app icon, nothing appears to happen. From then on, when you click on it, it loads properly. -- 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-489) Pulse shellapp has improper margins
[ http://jira.magnolia-cms.com/browse/MGNLUI-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Lipp reopened MGNLUI-489: Don't get how that issue was fixed. Pulse shellapp has improper margins --- Key: MGNLUI-489 URL: http://jira.magnolia-cms.com/browse/MGNLUI-489 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Components: pulse Reporter: Christopher Zimmermann Assignee: Aleksandr Pchelintcev -- 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: (FRISBEE-5) Use with Magnolia 4.5
Use with Magnolia 4.5 - Key: FRISBEE-5 URL: http://jira.magnolia-cms.com/browse/FRISBEE-5 Project: Frisbee Issue Type: Bug Reporter: Florian Haselmayer Assignee: Maurizio Müller Priority: Major Installation with CE 4.5 is not plug and play. Will there be an update? -- 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-571) com.vaadin.terminal.gwt.DefaultWidgetSet has been deprecated in favor of com.vaadin.DefaultWidgetSet
com.vaadin.terminal.gwt.DefaultWidgetSet has been deprecated in favor of com.vaadin.DefaultWidgetSet Key: MGNLUI-571 URL: http://jira.magnolia-cms.com/browse/MGNLUI-571 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Affects Versions: 5.0 Alpha2 s011 Reporter: Espen Jervidalo Assignee: Espen Jervidalo Fix For: 5.0 Alpha2 s012 -- 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: (MGNLACTIVATION-7) Implement basic activation
Implement basic activation -- Key: MGNLACTIVATION-7 URL: http://jira.magnolia-cms.com/browse/MGNLACTIVATION-7 Project: Magnolia Activation Module Issue Type: Task Reporter: Federico Grilli Assignee: Federico Grilli Priority: Critical Fix For: 5.0 Alpha2 s012 See http://wiki.magnolia-cms.com/display/DEV/Concept+-+Basic+Activation -- 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-564) DefaultProperty: introduce generics
[ http://jira.magnolia-cms.com/browse/MGNLUI-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Espen Jervidalo reopened MGNLUI-564: DefaultProperty: introduce generics --- Key: MGNLUI-564 URL: http://jira.magnolia-cms.com/browse/MGNLUI-564 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Affects Versions: 5.0 Alpha2 s011 Reporter: Espen Jervidalo Assignee: Espen Jervidalo Fix For: 5.0 Alpha2 s012 -- 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-564) DefaultProperty: introduce generics and deprecate Constructor resolving type from value
[ http://jira.magnolia-cms.com/browse/MGNLUI-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Espen Jervidalo updated MGNLUI-564: --- Summary: DefaultProperty: introduce generics and deprecate Constructor resolving type from value (was: DefaultProperty: introduce generics) DefaultProperty: introduce generics and deprecate Constructor resolving type from value --- Key: MGNLUI-564 URL: http://jira.magnolia-cms.com/browse/MGNLUI-564 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Affects Versions: 5.0 Alpha2 s011 Reporter: Espen Jervidalo Assignee: Espen Jervidalo Fix For: 5.0 Alpha2 s012 -- 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: (MGNLINTEMPL-27) Added optional dependency to observation module
Added optional dependency to observation module --- Key: MGNLINTEMPL-27 URL: http://jira.magnolia-cms.com/browse/MGNLINTEMPL-27 Project: Magnolia In-place templating Module Issue Type: Task Affects Versions: 1.3.1 Reporter: Milan Divilek Assignee: Milan Divilek Fix For: 1.3.3 MGNLINTEMPL-22 brings observation command which need observation module version 1.3.1. So we need add optional dependency to observation module into inplace-templating module descriptor. -- 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: (MGNLINTEMPL-28) Move bootstrap file for versionResourceOnChange into bootstrap folder
Move bootstrap file for versionResourceOnChange into bootstrap folder
-
Key: MGNLINTEMPL-28
URL: http://jira.magnolia-cms.com/browse/MGNLINTEMPL-28
Project: Magnolia In-place templating Module
Issue Type: Task
Affects Versions: 1.3.1
Reporter: Milan Divilek
Assignee: Milan Divilek
Fix For: 1.3.3
Move
config.modules.observation.config.listenerConfigurations.versionResourceOnChange.xml
bootstrap file from the {{info/magnolia/module/inplacetemplating/setup }} into
/mgnl-bootstrap/observation/ folder. This is need to do for better organization
of config files. This we can done because bootstrap-files which are not placed
in /mgnl-bootstrap/inplace-templating are not installed automatically.
--
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-572) Constructor of DefaultProperty is way too strict about null-values.
Constructor of DefaultProperty is way too strict about null-values. --- Key: MGNLUI-572 URL: http://jira.magnolia-cms.com/browse/MGNLUI-572 Project: Magnolia UI Issue Type: Bug Security Level: Public Affects Versions: 5.0 Alpha2 s012 Reporter: Aleksandr Pchelintcev Assignee: Espen Jervidalo Priority: Critical Fix For: 5.0 Alpha2 s012 DefaultProperty(String propertyName, T value) throws an Exception in case of null-value and in some cases those are passed into 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: (MGNLUI-572) Constructor of DefaultProperty is way too strict about null-values.
[ http://jira.magnolia-cms.com/browse/MGNLUI-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Pchelintcev updated MGNLUI-572: - Parent: MGNLUI-485 Issue Type: Sub-task (was: Bug) Constructor of DefaultProperty is way too strict about null-values. --- Key: MGNLUI-572 URL: http://jira.magnolia-cms.com/browse/MGNLUI-572 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Affects Versions: 5.0 Alpha2 s012 Reporter: Aleksandr Pchelintcev Assignee: Espen Jervidalo Priority: Critical Fix For: 5.0 Alpha2 s012 DefaultProperty(String propertyName, T value) throws an Exception in case of null-value and in some cases those are passed into 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] Created: (MGNLUI-573) Add references to the original in the parts of EasyUploads add-on used in the project.
Add references to the original in the parts of EasyUploads add-on used in the project. -- Key: MGNLUI-573 URL: http://jira.magnolia-cms.com/browse/MGNLUI-573 Project: Magnolia UI Issue Type: Bug Security Level: Public Affects Versions: 5.0 Alpha2 s012 Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev Fix For: 5.0 Alpha2 s012 -- 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-573) Add references to the original in the parts of EasyUploads add-on used in the project.
[ http://jira.magnolia-cms.com/browse/MGNLUI-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Pchelintcev updated MGNLUI-573: - Parent: MGNLUI-485 Issue Type: Sub-task (was: Bug) Add references to the original in the parts of EasyUploads add-on used in the project. -- Key: MGNLUI-573 URL: http://jira.magnolia-cms.com/browse/MGNLUI-573 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Affects Versions: 5.0 Alpha2 s012 Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev Fix For: 5.0 Alpha2 s012 -- 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-4543) Inheritance of binaries in area nodes does not work
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frank Sommer updated MAGNOLIA-4543:
---
Affects Version/s: 4.5.6
4.5.5
Inheritance of binaries in area nodes does not work
---
Key: MAGNOLIA-4543
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4543
Project: Magnolia
Issue Type: Bug
Security Level: Public
Components: templating
Affects Versions: 4.5.4, 4.5.5, 4.5.6
Reporter: Frank Sommer
Assignee: Philipp Bärfuss
In my dialog of the footer area I have a dam control to add an image to the
footer. If I use the media to provide an image the image will be shown on
homepage and the childpages. If I use the upload control, the image will only
shown on the homepage not on the child pages. While debugging I see that the
binary property of the area node is not available, all other properties are
available.
I could reproduce this on Demoauthor instance.
# add {{img src=$\{stkfn.getAssetLink(content, upload)!\} /}} to the
{{footer.ftl}}
# add a dam control named {{upload}} to the footer dialog
--
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-4543) Inheritance of binaries in area nodes does not work
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kovařík updated MAGNOLIA-4543:
Fix Version/s: 4.5.8
Inheritance of binaries in area nodes does not work
---
Key: MAGNOLIA-4543
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4543
Project: Magnolia
Issue Type: Bug
Security Level: Public
Components: templating
Affects Versions: 4.5.4, 4.5.5, 4.5.6
Reporter: Frank Sommer
Assignee: Philipp Bärfuss
Fix For: 4.5.8
In my dialog of the footer area I have a dam control to add an image to the
footer. If I use the media to provide an image the image will be shown on
homepage and the childpages. If I use the upload control, the image will only
shown on the homepage not on the child pages. While debugging I see that the
binary property of the area node is not available, all other properties are
available.
I could reproduce this on Demoauthor instance.
# add {{img src=$\{stkfn.getAssetLink(content, upload)!\} /}} to the
{{footer.ftl}}
# add a dam control named {{upload}} to the footer dialog
--
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: (MGNLSTK-1071) Propagate MGNLSTK-1069 changes to 2.5 head
Propagate MGNLSTK-1069 changes to 2.5 head -- Key: MGNLSTK-1071 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1071 Project: Magnolia Standard Templating Kit Issue Type: Task Affects Versions: 2.5 Alpha2 s011 Reporter: Eric Hechinger Assignee: Eric Hechinger Fix For: 2.5 Alpha2 s012 -- 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: (MGNLMIGRATION-213) UpdateExtendsMigrationTask fails on relative paths
[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Schmitt updated MGNLMIGRATION-213: - Priority: Major (was: Neutral) UpdateExtendsMigrationTask fails on relative paths -- Key: MGNLMIGRATION-213 URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-213 Project: Magnolia Migration Issue Type: Bug Components: Migration Task Affects Versions: 1.2 Reporter: Ondřej Chytil Priority: Major Fix For: 1.2.1 See linked support ticket for details. -- 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: (MGNLMIGRATION-199) Template Script Migration report is not correctly setup in the main migration page
[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Schmitt updated MGNLMIGRATION-199: - Assignee: Jozef Chocholacek Template Script Migration report is not correctly setup in the main migration page -- Key: MGNLMIGRATION-199 URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-199 Project: Magnolia Migration Issue Type: Improvement Components: Report Affects Versions: 1.2 Reporter: Samuel Schmitt Assignee: Jozef Chocholacek Fix For: 1.2.1 Attachments: Screenshot_1_8_13_10_09_AM.png When you open the report (from the ZIP) the part regarding the Template Script Migration is a bit weird. First you see in the list of modules TemplateMigration, but this is not a module. Template Migration report must have an independant section... and maybe must be renamed Template SCRIPT migration. Second, you have another section called Components. This section displays links to Components templates script migration report BUT also to Pages template script migration report. Maybe it will be more clear if we create a section called Template Script Migration report where the first link is the link TemplateMigration and then the list of links to the pages and components. -- 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: (MGNLSTK-1073) The configuration of STK between a new instance and a migrated instance must be the same
The configuration of STK between a new instance and a migrated instance must be the same Key: MGNLSTK-1073 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1073 Project: Magnolia Standard Templating Kit Issue Type: Task Reporter: Samuel Schmitt Priority: Major Fix For: 2.0.9 -- 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: (MGNLSTK-1072) Rebootstrap the latest configuration of STK generated by migration module 1.2.1
Rebootstrap the latest configuration of STK generated by migration module 1.2.1 --- Key: MGNLSTK-1072 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1072 Project: Magnolia Standard Templating Kit Issue Type: Task Reporter: Samuel Schmitt Priority: Major Fix For: 2.0.9 Right now the bootstraps found in STK are generated by the migration module version 1.1.2. In order to align configuration of a fresh instance and of a migrated instance, the configuration of STK generated by the migration module must be exported and added to STK. h5. How to do it First migration 1.2.1 must be finalized. Take a the latest 4.4.x and migrate it with migration 1.2.1 to 4.5.8. Export the config of STK and add it to the mgnl-bootstrap folder. -- 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-1072) Rebootstrap the latest configuration of STK generated by migration module 1.2.1
[ http://jira.magnolia-cms.com/browse/MGNLSTK-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Schmitt updated MGNLSTK-1072: Parent: MGNLSTK-1073 Issue Type: Sub-task (was: Task) Rebootstrap the latest configuration of STK generated by migration module 1.2.1 --- Key: MGNLSTK-1072 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1072 Project: Magnolia Standard Templating Kit Issue Type: Sub-task Reporter: Samuel Schmitt Priority: Major Fix For: 2.0.9 Right now the bootstraps found in STK are generated by the migration module version 1.1.2. In order to align configuration of a fresh instance and of a migrated instance, the configuration of STK generated by the migration module must be exported and added to STK. h5. How to do it First migration 1.2.1 must be finalized. Take a the latest 4.4.x and migrate it with migration 1.2.1 to 4.5.8. Export the config of STK and add it to the mgnl-bootstrap folder. -- 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: (MGNLSTK-1074) Add in a version handler the delta between the previous config (done with migration 1.1.2) and the new done with migration 1.2.1
Add in a version handler the delta between the previous config (done with migration 1.1.2) and the new done with migration 1.2.1 Key: MGNLSTK-1074 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1074 Project: Magnolia Standard Templating Kit Issue Type: Sub-task Reporter: Samuel Schmitt Priority: Major Fix For: 2.0.9 Both configuration must be compared and the delta must be represented by a task in the version handler. -- 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-521) Security App: Edit group causes com.vaadin.data.Buffered$SourceException
[ http://jira.magnolia-cms.com/browse/MGNLUI-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Lipp reopened MGNLUI-521: Not clear how that ticket had been fixed. Security App: Edit group causes com.vaadin.data.Buffered$SourceException Key: MGNLUI-521 URL: http://jira.magnolia-cms.com/browse/MGNLUI-521 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Affects Versions: 5.0 Alpha2 s011 Reporter: Christopher Zimmermann Assignee: Aleksandr Pchelintcev Fix For: 5.0 Alpha2 s011 Open Security app. Click Groups tab. Click Edit group. Nothing happens in ui. get a stack trace. 2013-01-07 13:50:38,865 WARN info.magnolia.ui.framework.event.SimpleEventBus : Exception caught when dispatching event: null com.vaadin.data.Buffered$SourceException at com.vaadin.ui.AbstractField.setPropertyDataSource(AbstractField.java:634) at info.magnolia.ui.admincentral.field.builder.AbstractFieldBuilder.setPropertyDataSource(AbstractFieldBuilder.java:126) at info.magnolia.ui.admincentral.field.builder.SelectFieldBuilder.setPropertyDataSource(SelectFieldBuilder.java:204) at info.magnolia.ui.admincentral.field.builder.AbstractFieldBuilder.getField(AbstractFieldBuilder.java:100) at info.magnolia.ui.admincentral.form.builder.FormBuilder.buildForm(FormBuilder.java:87) at info.magnolia.ui.admincentral.form.FormPresenterImpl.start(FormPresenterImpl.java:125) at info.magnolia.ui.admincentral.dialog.FormDialogPresenterImpl.start(FormDialogPresenterImpl.java:104) at info.magnolia.ui.admincentral.dialog.action.EditDialogAction.execute(EditDialogAction.java:85) at info.magnolia.ui.admincentral.actionbar.ActionbarPresenter.createAndExecuteAction(ActionbarPresenter.java:286) at info.magnolia.ui.admincentral.workbench.ContentWorkbenchPresenter$2.onActionbarItemClicked(ContentWorkbenchPresenter.java:151) at info.magnolia.ui.admincentral.event.ActionbarItemClickedEvent.dispatch(ActionbarItemClickedEvent.java:65) at info.magnolia.ui.admincentral.event.ActionbarItemClickedEvent.dispatch(ActionbarItemClickedEvent.java:43) at info.magnolia.ui.framework.event.SimpleEventBus.fireEvent(SimpleEventBus.java:78) Caused by: Caused by: com.vaadin.data.util.converter.Converter$ConversionException: Unable to convert value of type java.util.ArrayList to presentation type interface java.util.Set. No converter is set and the types are not compatible. at com.vaadin.data.util.converter.ConverterUtil.convertFromModel(ConverterUtil.java:98) at com.vaadin.ui.AbstractField.convertFromModel(AbstractField.java:705) at com.vaadin.ui.AbstractField.convertFromModel(AbstractField.java:690) at com.vaadin.ui.AbstractField.setPropertyDataSource(AbstractField.java:626) -- 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
