[magnolia-dev] [JIRA] Resolved: (MAGNOLIA-2809) Update task incorrectly moves 'templatePath' nodes of templates to parameters subnode
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Teresa Miyar resolved MAGNOLIA-2809.
Resolution: Fixed
> Update task incorrectly moves 'templatePath' nodes of templates to parameters
> subnode
> -
>
> Key: MAGNOLIA-2809
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2809
> Project: Magnolia
> Issue Type: Bug
> Components: templating, updatemechanism
>Affects Versions: 4.0
>Reporter: Grégory Joseph
>Assignee: Teresa Miyar
>Priority: Blocker
> Fix For: 4.1.1, 4.0.3
>
>
> There are 2 conflicting tasks for templates:
> # renamed {{path}} to {{templatePath}} - that is 100% correct
> # move non-default template parameters to the {{parameters}} subnode. The bug
> is that this task consider {{path}} to be the property to keep, while these
> have just been renamed to {{templatePath}}.
> Fixing this will require careful writing of update tasks for both 4.0.3 *and*
> 4.1.1
> (!) workaround: move the {{templatePath}} nodedata of your templates from the
> {{parameters}} subnode back into the template node itself.
--
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/home/community/mailing-lists.html
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Assigned: (MAGNOLIA-2851) PageIterator tag wrongly iterates over children of the current paragraph instead of the page.
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Teresa Miyar reassigned MAGNOLIA-2851: -- Assignee: Teresa Miyar (was: Grégory Joseph) > PageIterator tag wrongly iterates over children of the current paragraph > instead of the page. > - > > Key: MAGNOLIA-2851 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2851 > Project: Magnolia > Issue Type: Bug > Components: taglibs >Reporter: Grégory Joseph >Assignee: Teresa Miyar > Fix For: 4.1.1, 4.0.3 > > -- 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/home/community/mailing-lists.html To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2816) png and swf mimetypes have ; in their value when updating from a version prior to 3.6.3
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24023#action_24023
]
Hudson CI server commented on MAGNOLIA-2816:
Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif!
[magnolia_main-trunk
#962|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/962/]
fix version should be 4.0.3 not 4.0.2
fix version should be 4.0.3 not 4.0.2
> png and swf mimetypes have ; in their value when updating from a version
> prior to 3.6.3
> ---
>
> Key: MAGNOLIA-2816
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2816
> Project: Magnolia
> Issue Type: Bug
> Components: core
>Reporter: Grégory Joseph
>Assignee: Teresa Miyar
> Fix For: 4.1.1, 3.6.7, 4.0.3
>
>
> The bootstrap file is fine, but the update tasks registered for 3.6.4 set
> these mime types to {{image/png;}} and {{application/x-shockwave-flash;}}
> respectively, where the {{;}} should not be there.
--
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/home/community/mailing-lists.html
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2809) Update task incorrectly moves 'templatePath' nodes of templates to parameters subnode
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24024#action_24024
]
Hudson CI server commented on MAGNOLIA-2809:
Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif!
[magnolia_main-trunk
#962|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/962/]
added fix for the right versions 4.0.3 and 4.1.1
> Update task incorrectly moves 'templatePath' nodes of templates to parameters
> subnode
> -
>
> Key: MAGNOLIA-2809
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2809
> Project: Magnolia
> Issue Type: Bug
> Components: templating, updatemechanism
>Affects Versions: 4.0
>Reporter: Grégory Joseph
>Assignee: Teresa Miyar
>Priority: Blocker
> Fix For: 4.1.1, 4.0.3
>
>
> There are 2 conflicting tasks for templates:
> # renamed {{path}} to {{templatePath}} - that is 100% correct
> # move non-default template parameters to the {{parameters}} subnode. The bug
> is that this task consider {{path}} to be the property to keep, while these
> have just been renamed to {{templatePath}}.
> Fixing this will require careful writing of update tasks for both 4.0.3 *and*
> 4.1.1
> (!) workaround: move the {{templatePath}} nodedata of your templates from the
> {{parameters}} subnode back into the template node itself.
--
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/home/community/mailing-lists.html
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2814) Mail command class not modified by update mechanism
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24025#action_24025
]
Hudson CI server commented on MAGNOLIA-2814:
Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif!
[magnolia_main-trunk
#962|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/962/]
update mail command for the appropriate versions
> Mail command class not modified by update mechanism
> ---
>
> Key: MAGNOLIA-2814
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2814
> Project: Magnolia
> Issue Type: Bug
> Components: admininterface, mail, updatemechanism
>Affects Versions: 4.1
>Reporter: Grégory Joseph
>Assignee: Teresa Miyar
>Priority: Critical
> Fix For: 4.1.1, 4.0.3
>
>
> When updating the docu instance from 3.6.5 to 4.1.1 (snapshot), somehow, the
> mail command's class property was *not* updated!
> After the update, it was still {{info.magnolia.cms.mail.commands.MailCommand}}
--
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/home/community/mailing-lists.html
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2135) Public instance: repository content filtered based on virtualhost
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24022#action_24022 ] Hudson CI server commented on MAGNOLIA-2135: Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! [magnolia_main-trunk #962|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/962/] content filtered based on virtualhost > Public instance: repository content filtered based on virtualhost > - > > Key: MAGNOLIA-2135 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2135 > Project: Magnolia > Issue Type: Improvement > Components: core >Affects Versions: 3.5.4 >Reporter: Fabrizio Giustina >Assignee: Fabrizio Giustina > Fix For: 4.1.1 > > > Related to MAGNOLIA-2134: > we should also provide a way to "filter" content in the website repository, > making trees for different websites hidden for specific virtualhost. > For example if we use a single public instance in order to serve site-one and > site-two we would like to accept requests for: > http://www.site-one.xxx/site-one/home.html > but not for > http://www.site-one.xxx/site-two/home.html -- 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/home/community/mailing-lists.html To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2813) defaultPublicURI is set to quickstart page even if there are already content and templates, thus breaking updates of existing sites
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24026#action_24026 ] Hudson CI server commented on MAGNOLIA-2813: Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! [magnolia_main-trunk #962|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/962/] set a warning message for the user if the defaultpublicuri is wrong on updates > defaultPublicURI is set to quickstart page even if there are already content > and templates, thus breaking updates of existing sites > --- > > Key: MAGNOLIA-2813 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2813 > Project: Magnolia > Issue Type: Bug > Components: admininterface >Affects Versions: 4.0 >Reporter: Grégory Joseph >Assignee: Teresa Miyar > Fix For: 4.1.1, 4.0.3 > > > An update task registered for 4.0 overrides the defaultPublicURI on *public* > instances. What is this for? Shouldn't do like the website tree class does - > do this only if the site is empty ? This happens even if there is content and > templates. > Updating the docu site from 3.5.8 to 4.1.1 broke the default public uri > mapping, for example. -- 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/home/community/mailing-lists.html To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2849) Cache: cache keys based on host names, not only original uri
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24021#action_24021 ] Hudson CI server commented on MAGNOLIA-2849: Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! [magnolia_main-trunk #962|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/962/] make default cache policy configurable in order to use different cache keys depending on host names > Cache: cache keys based on host names, not only original uri > > > Key: MAGNOLIA-2849 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2849 > Project: Magnolia > Issue Type: Improvement >Reporter: Fabrizio Giustina >Assignee: Fabrizio Giustina >Priority: Minor > Fix For: 4.1.1 > > > If multiple hosts are mapped to the same magnolia instance you may need to > have different cache entries for the same url but different hosts. > Cache uses only the original uri for cache keys, so if you map the default > uri to different pages depending on the host, you will end up with the same > content cached and served for any host. In this situation we should allow to > use also the request host name for the cache key. -- 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/home/community/mailing-lists.html To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2814) Mail command class not modified by update mechanism
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24029#action_24029
]
Hudson CI server commented on MAGNOLIA-2814:
Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif!
[magnolia_main-4.0-branch
#53|http://hudson.magnolia-cms.com/job/magnolia_main-4.0-branch/53/]
merge with trunk r27343 update mail command for the appropriate versions
> Mail command class not modified by update mechanism
> ---
>
> Key: MAGNOLIA-2814
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2814
> Project: Magnolia
> Issue Type: Bug
> Components: admininterface, mail, updatemechanism
>Affects Versions: 4.1
>Reporter: Grégory Joseph
>Assignee: Teresa Miyar
>Priority: Critical
> Fix For: 4.1.1, 4.0.3
>
>
> When updating the docu instance from 3.6.5 to 4.1.1 (snapshot), somehow, the
> mail command's class property was *not* updated!
> After the update, it was still {{info.magnolia.cms.mail.commands.MailCommand}}
--
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/home/community/mailing-lists.html
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2813) defaultPublicURI is set to quickstart page even if there are already content and templates, thus breaking updates of existing sites
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24030#action_24030 ] Hudson CI server commented on MAGNOLIA-2813: Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! [magnolia_main-4.0-branch #53|http://hudson.magnolia-cms.com/job/magnolia_main-4.0-branch/53/] merged with trunk r27334 removed the task setdefaulturi fromthe update merged with trunk r27334 set a warning message for the user if the defaultpublicuri is wrong on updates > defaultPublicURI is set to quickstart page even if there are already content > and templates, thus breaking updates of existing sites > --- > > Key: MAGNOLIA-2813 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2813 > Project: Magnolia > Issue Type: Bug > Components: admininterface >Affects Versions: 4.0 >Reporter: Grégory Joseph >Assignee: Teresa Miyar > Fix For: 4.1.1, 4.0.3 > > > An update task registered for 4.0 overrides the defaultPublicURI on *public* > instances. What is this for? Shouldn't do like the website tree class does - > do this only if the site is empty ? This happens even if there is content and > templates. > Updating the docu site from 3.5.8 to 4.1.1 broke the default public uri > mapping, for example. -- 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/home/community/mailing-lists.html To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2816) png and swf mimetypes have ; in their value when updating from a version prior to 3.6.3
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24027#action_24027
]
Hudson CI server commented on MAGNOLIA-2816:
Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif!
[magnolia_main-4.0-branch
#53|http://hudson.magnolia-cms.com/job/magnolia_main-4.0-branch/53/]
merged with trunk r27120 fix version should be 4.0.3 not 4.0.2
> png and swf mimetypes have ; in their value when updating from a version
> prior to 3.6.3
> ---
>
> Key: MAGNOLIA-2816
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2816
> Project: Magnolia
> Issue Type: Bug
> Components: core
>Reporter: Grégory Joseph
>Assignee: Teresa Miyar
> Fix For: 4.1.1, 3.6.7, 4.0.3
>
>
> The bootstrap file is fine, but the update tasks registered for 3.6.4 set
> these mime types to {{image/png;}} and {{application/x-shockwave-flash;}}
> respectively, where the {{;}} should not be there.
--
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/home/community/mailing-lists.html
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2809) Update task incorrectly moves 'templatePath' nodes of templates to parameters subnode
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24028#action_24028
]
Hudson CI server commented on MAGNOLIA-2809:
Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif!
[magnolia_main-4.0-branch
#53|http://hudson.magnolia-cms.com/job/magnolia_main-4.0-branch/53/]
merged with trunk r27347 added fix for the right versions 4.0.3 and 4.1.1
> Update task incorrectly moves 'templatePath' nodes of templates to parameters
> subnode
> -
>
> Key: MAGNOLIA-2809
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2809
> Project: Magnolia
> Issue Type: Bug
> Components: templating, updatemechanism
>Affects Versions: 4.0
>Reporter: Grégory Joseph
>Assignee: Teresa Miyar
>Priority: Blocker
> Fix For: 4.1.1, 4.0.3
>
>
> There are 2 conflicting tasks for templates:
> # renamed {{path}} to {{templatePath}} - that is 100% correct
> # move non-default template parameters to the {{parameters}} subnode. The bug
> is that this task consider {{path}} to be the property to keep, while these
> have just been renamed to {{templatePath}}.
> Fixing this will require careful writing of update tasks for both 4.0.3 *and*
> 4.1.1
> (!) workaround: move the {{templatePath}} nodedata of your templates from the
> {{parameters}} subnode back into the template node itself.
--
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/home/community/mailing-lists.html
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Resolved: (MGNLINTEMPL-8) Sample user "tim" can't login
[ http://jira.magnolia-cms.com/browse/MGNLINTEMPL-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Teresa Miyar resolved MGNLINTEMPL-8. Resolution: Fixed > Sample user "tim" can't login > - > > Key: MGNLINTEMPL-8 > URL: http://jira.magnolia-cms.com/browse/MGNLINTEMPL-8 > Project: Magnolia In-place templating Module > Issue Type: Bug >Affects Versions: 1.0.1 >Reporter: Grégory Joseph >Assignee: Teresa Miyar > Fix For: 1.0.2 > > -- 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/home/community/mailing-lists.html To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Resolved: (MAGNOLIA-2851) PageIterator tag wrongly iterates over children of the current paragraph instead of the page.
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Teresa Miyar resolved MAGNOLIA-2851. Resolution: Fixed > PageIterator tag wrongly iterates over children of the current paragraph > instead of the page. > - > > Key: MAGNOLIA-2851 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2851 > Project: Magnolia > Issue Type: Bug > Components: taglibs >Reporter: Grégory Joseph >Assignee: Teresa Miyar > Fix For: 4.1.1, 4.0.3 > > -- 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/home/community/mailing-lists.html To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2851) PageIterator tag wrongly iterates over children of the current paragraph instead of the page.
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24031#action_24031 ] Hudson CI server commented on MAGNOLIA-2851: Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! [magnolia_main-4.0-branch #54|http://hudson.magnolia-cms.com/job/magnolia_main-4.0-branch/54/] merged with trunk r27286 now use AggregationState.getMainContent() > PageIterator tag wrongly iterates over children of the current paragraph > instead of the page. > - > > Key: MAGNOLIA-2851 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2851 > Project: Magnolia > Issue Type: Bug > Components: taglibs >Reporter: Grégory Joseph >Assignee: Teresa Miyar > Fix For: 4.1.1, 4.0.3 > > -- 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/home/community/mailing-lists.html To unsubscribe, E-mail to:
