[magnolia-dev] [JIRA] Created: (MGNLUI-607) config app: fieldtype conversion error

config app: fieldtype conversion error -- Key: MGNLUI-607 URL: http://jira.magnolia-cms.com/browse/MGNLUI-607 Project: Magnolia UI Issue Type: Bug Security Level: Public Affects Versions: 5.0 Alp

[magnolia-dev] [JIRA] Created: (MGNLFORM-151) Update dependency of migration module to 1.2.1

Update dependency of migration module to 1.2.1 -- Key: MGNLFORM-151 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-151 Project: Magnolia Form Module Issue Type: Task Reporter: Samuel

[magnolia-dev] [JIRA] Created: (MSHOP-60) Update dependency of migration module to 1.2.1

Update dependency of migration module to 1.2.1 -- Key: MSHOP-60 URL: http://jira.magnolia-cms.com/browse/MSHOP-60 Project: Magnolia Shop Issue Type: Task Reporter: Samuel Schmitt

[magnolia-dev] [JIRA] Created: (MGNLPUR-84) Update dependency of migration module to 1.2.1

Update dependency of migration module to 1.2.1 -- Key: MGNLPUR-84 URL: http://jira.magnolia-cms.com/browse/MGNLPUR-84 Project: Magnolia Public User Registration Issue Type: Task Reporte

[magnolia-dev] [JIRA] Created: (MGNLCMNT-76) Update dependency of migration module to 1.2.1

Update dependency of migration module to 1.2.1 -- Key: MGNLCMNT-76 URL: http://jira.magnolia-cms.com/browse/MGNLCMNT-76 Project: Magnolia Commenting Module Issue Type: Task Security Level: Pu

[magnolia-dev] [JIRA] Created: (MGNLSTK-1079) Update dependency of migration module to 1.2.1

Update dependency of migration module to 1.2.1 -- Key: MGNLSTK-1079 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1079 Project: Magnolia Standard Templating Kit Issue Type: Task Compon

[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4797) NodeUtil.getSiblings() methods

[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Kovařík updated MAGNOLIA-4797: Description: Implement NodeUtil.getSiblingsXXX(...) methods: - Iterable getSiblingsAfter(N

[magnolia-dev] [JIRA] Created: (MAGNOLIA-4796) Cannot upload resources

Cannot upload resources --- Key: MAGNOLIA-4796 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4796 Project: Magnolia Issue Type: Bug Security Level: Public Environment: http://demoauthor.magnolia-cms.co

[magnolia-dev] [JIRA] Created: (MAGNOLIA-4797) NodeUtil.getSiblings() methods

NodeUtil.getSiblings() methods --- Key: MAGNOLIA-4797 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4797 Project: Magnolia Issue Type: Task Security Level: Public Components: core

[magnolia-dev] [JIRA] Created: (MGNLSTK-1078) 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-1078

[magnolia-dev] [JIRA] Created: (MGNLSTK-1077) Rebootstrap the latest configuration of Demo-project generated by migration module 1.2.1

Rebootstrap the latest configuration of Demo-project generated by migration module 1.2.1 Key: MGNLSTK-1077 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1077

[magnolia-dev] [JIRA] Updated: (MGNLSTK-1076) The content of Demo-project between a new instance and a migrated instance must be the same

[ http://jira.magnolia-cms.com/browse/MGNLSTK-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Schmitt updated MGNLSTK-1076: Description: As discussed for STK (MGNLSTK-1073), when the migration module change its logi

[magnolia-dev] [JIRA] Created: (MGNLSTK-1076) The content of Demo-project between a new instance and a migrated instance must be the same

The content of Demo-project between a new instance and a migrated instance must be the same --- Key: MGNLSTK-1076 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1076

[magnolia-dev] [JIRA] Updated: (MGNLMIGRATION-217) Footer content is not correctly migrated, the footer is transformed into a component but it should be an area

[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka updated MGNLMIGRATION-217: -- Summary: Footer content is not correctly migrated, the footer is transformed into

[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4774) fckEditor does not pull Alt Text for images

[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Simak updated MAGNOLIA-4774: - Fix Version/s: 4.4.10 > fckEditor does not pull Alt Text for images > --

[magnolia-dev] [JIRA] Updated: (MGNLINTEMPL-28) Move bootstrap file for versionResourceOnChange into bootstrap folder

[ http://jira.magnolia-cms.com/browse/MGNLINTEMPL-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka updated MGNLINTEMPL-28: --- Description: Move {{config.modules.observation.config.listenerConfigurations.versionResourc

[magnolia-dev] [JIRA] Updated: (MGNLDAM-82) Create a DamDownloadServlet in ordor to download DAM content content

[ http://jira.magnolia-cms.com/browse/MGNLDAM-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Hechinger updated MGNLDAM-82: -- Description: Like for MGNLDAM-81, Create a DamDownloadServlet (Equivalent of DMSDownloadServlet)

[magnolia-dev] [JIRA] Updated: (MGNLMIGRATION-217) Footer content is not correctly migrated, the footer is transformed as an component but it should be an area

[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Schmitt updated MGNLMIGRATION-217: - Description: The task that transform the primary type ({{info.magnolia.migr

[magnolia-dev] [JIRA] Reopened: (MGNLMIGRATION-80) When using template script from Magnolia modules, provide areas of these templates without parsing the FTL.

[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka reopened MGNLMIGRATION-80: -- - I fail to see how is [this|http://git.magnolia-cms.com/gitweb/?p=modules/4-5-migrati

[magnolia-dev] [JIRA] Updated: (MGNLMIGRATION-217) Footer content is not correctly migrated, the footer is transformed as an component but it should be an area

[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Schmitt updated MGNLMIGRATION-217: - Description: The task that transform the primary type ({{info.magnolia.migr

[magnolia-dev] [JIRA] Deleted: (MGNLUI-546) Create activate/deactivate actions

[ http://jira.magnolia-cms.com/browse/MGNLUI-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli deleted MGNLUI-546: --- > Create activate/deactivate actions > -- > > Key:

[magnolia-dev] [JIRA] Reopened: (MGNLMIGRATION-136) ftl migration: Some migrated ftl-files are empty - all content deleted

[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka reopened MGNLMIGRATION-136: --- What are the changes like [this one|http://git.magnolia-cms.com/gitweb/?p=modules/4

[magnolia-dev] [JIRA] Created: (MGNLMIGRATION-218) Config Migration: metaNavigation area in the site definition is missing the editable=false property

Config Migration: metaNavigation area in the site definition is missing the editable=false property --- Key: MGNLMIGRATION-218 URL: http://jira.magnolia-cms.com/browse

[magnolia-dev] [JIRA] Created: (MAGNOLIA-4795) Remove deprecated Content API from the VersionCommand

Remove deprecated Content API from the VersionCommand - Key: MAGNOLIA-4795 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4795 Project: Magnolia Issue Type: Task Security Level: Pu

[magnolia-dev] [JIRA] Created: (MAGNOLIA-4794) Write test for RuleBasedCommand

Write test for RuleBasedCommand --- Key: MAGNOLIA-4794 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4794 Project: Magnolia Issue Type: Task Security Level: Public Reporter: Jozef Chocholacek

[magnolia-dev] [JIRA] Created: (MGNLUI-606) info.magnolia.ui.vaadin.integration.jcr whole package need review

info.magnolia.ui.vaadin.integration.jcr whole package need review - Key: MGNLUI-606 URL: http://jira.magnolia-cms.com/browse/MGNLUI-606 Project: Magnolia UI Issue Type: Task

[magnolia-dev] [JIRA] Reopened: (MGNLMIGRATION-211) Transformation of extra area is not correct, custom template scripts previously set on extras must be set to extras1 and extras2

[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Natascha Desmarais reopened MGNLMIGRATION-211: -- Title and description are missing from the extras area - afaik these a

[magnolia-dev] Re: Blossom servlet like behaviour

Thank you for your answer Tobias. I will stick to servlets when returning JSON responses. Thanks, Ron -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=276e1968-1651-4c1e-9294-5f02c3a68140 For

[magnolia-dev] [JIRA] Updated: (MGNLMIGRATION-217) Footer content is not correctly migrated, the footer is transformed as an component but it should be an area

[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Schmitt updated MGNLMIGRATION-217: - Description: The task that transform the primary type ({{info.magnolia.migr

[magnolia-dev] [JIRA] Updated: (MGNLMIGRATION-217) Footer content is not correctly migrated, the footer is transformed as an component but it should be an area

[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samuel Schmitt updated MGNLMIGRATION-217: - Description: The task that transform the primary type ({{info.magnolia.migr

[magnolia-dev] [JIRA] Created: (MGNLMIGRATION-217) Footer content is not correctly migrated, the footer is transformed as an component but it should be an area

Footer content is not correctly migrated, the footer is transformed as an component but it should be an area Key: MGNLMIGRATION-217 URL: http://jira.magno

[magnolia-dev] [JIRA] Created: (MAGNOLIA-4793) Define the behavior of MarkNodeAsDeletedCommand when versioning is unavailable

Define the behavior of MarkNodeAsDeletedCommand when versioning is unavailable -- Key: MAGNOLIA-4793 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4793 Project: Magnolia

[magnolia-dev] Re: No template definition registered for id: js

[quote]However, this might be also due to the fact that we don't remove the old resources (you might have some modifications in there that you need) and demo-project is still referencing all.js for example.[/quote] Agh, I need a coffee. What I meant to say is that the theme is probably still re

[magnolia-dev] Re: No template definition registered for id: js

Hello Will Thanks for specifying what your script does :) Just to clarify, the migration tool helps you to migrate all modules that involve templating mechanisms (config and scripts), but themes are not included in this. Themes are varying too much in order to be able to determine a common pat

[magnolia-dev] [JIRA] Reopened: (MGNLMIGRATION-171) Migration module breaks code which is using <> (pointy brackets) instead of [] (square brackets) when combined on in a single expression

[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka reopened MGNLMIGRATION-171: --- Where/how was this solved? There's no commit associated with this issue anywhere.

[magnolia-dev] [JIRA] Updated: (MGNLIMG-38) outputting into jpg format fails if processed image is a gif or png

[ http://jira.magnolia-cms.com/browse/MGNLIMG-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Zimmermann updated MGNLIMG-38: -- Fix Version/s: 2.3 Alpha2 s012 (was: 2.0) Affec