[magnolia-dev] [JIRA] Issue Comment Edited: (MGNLSTK-557) Demo content: No dummy events for 2010
[
http://jira.magnolia-cms.com/browse/MGNLSTK-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=25777#action_25777
]
Christian Ringele edited comment on MGNLSTK-557 at 1/11/10 9:30 AM:
I had to update all events for demo Pascal gave.
So I i changed all events and added some new events, so that the span of dates
is over the complete year. Additionally there is one mont of events in the old
year, and one month in the coming year.
Like this, when the new year (2011) comes, simply all 'year' numbers have to be
changes to one year higher.
The events configured right now are:
- January 2009: 4 events
- All months of 2010: 4 events each
- January 2011: 4 events
I add here the bootstrap file of all dummy-events.
Additionally I have removed wrong generated page header image-properties from
all dummy event pages:
{code
sv:property sv:name=image sv:type=String
sv:valuedms/sv:value
/sv:property
sv:property sv:name=imageDmsUUID sv:type=String
sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value
/sv:property
sv:property sv:name=imageLocation sv:type=String
sv:valueabove/sv:value
/sv:property
}
was (Author: cringele):
I had to update all events for demo Pascal gave.
So I i changed all events and added some new events, so that the span of dates
is over the complete year. Additionally there is one mont of events in the old
year, and one month in the coming year.
Like this, when the new year (2011) comes, simply all 'year' numbers have to be
changes to one year higher.
The events configured right now are:
- January 2009: 4 events
- All months of 2010: 4 events each
- January 2011: 4 events
I add here the bootstrap file of all dummy-events.
Additionally I have removed wrong generated page header image-properties from
all dummy event pages:
{code}
sv:property sv:name=image sv:type=String
sv:valuedms/sv:value
/sv:property
sv:property sv:name=imageDmsUUID sv:type=String
sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value
/sv:property
sv:property sv:name=imageLocation sv:type=String
sv:valueabove/sv:value
/sv:property
{/code}
Demo content: No dummy events for 2010
--
Key: MGNLSTK-557
URL: http://jira.magnolia-cms.com/browse/MGNLSTK-557
Project: Magnolia Standard Templating Kit
Issue Type: Bug
Components: demoproject
Affects Versions: 1.2.1
Reporter: Christian Ringele
Assignee: Philipp Bärfuss
Fix For: 1.2.x
All dummy events in the demo content are events of the year 2009.
The events are located under: demo-project/service/dummy-events/
These events should be updated to 2010.
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Commented: (MGNLSTK-557) Demo content: No dummy events for 2010
[ http://jira.magnolia-cms.com/browse/MGNLSTK-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=25777#action_25777 ] Christian Ringele commented on MGNLSTK-557: --- I had to update all events for demo Pascal gave. So I i changed all events and added some new events, so that the span of dates is over the complete year. Additionally there is one mont of events in the old year, and one month in the coming year. Like this, when the new year (2011) comes, simply all 'year' numbers have to be changes to one year higher. The events configured right now are: - January 2009: 4 events - All months of 2010: 4 events each - January 2011: 4 events I add here the boostrap file of all dummy-events. Additionally I have removed wrong generated page header image-properties from all dummy event pages: code sv:property sv:name=image sv:type=String sv:valuedms/sv:value /sv:property sv:property sv:name=imageDmsUUID sv:type=String sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value /sv:property sv:property sv:name=imageLocation sv:type=String sv:valueabove/sv:value /sv:property /code Demo content: No dummy events for 2010 -- Key: MGNLSTK-557 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-557 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: demoproject Affects Versions: 1.2.1 Reporter: Christian Ringele Assignee: Philipp Bärfuss Fix For: 1.2.x All dummy events in the demo content are events of the year 2009. The events are located under: demo-project/service/dummy-events/ These events should be updated to 2010. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Issue Comment Edited: (MGNLSTK-557) Demo content: No dummy events for 2010
[ http://jira.magnolia-cms.com/browse/MGNLSTK-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=25777#action_25777 ] Christian Ringele edited comment on MGNLSTK-557 at 1/11/10 9:29 AM: I had to update all events for demo Pascal gave. So I i changed all events and added some new events, so that the span of dates is over the complete year. Additionally there is one mont of events in the old year, and one month in the coming year. Like this, when the new year (2011) comes, simply all 'year' numbers have to be changes to one year higher. The events configured right now are: - January 2009: 4 events - All months of 2010: 4 events each - January 2011: 4 events I add here the bootstrap file of all dummy-events. Additionally I have removed wrong generated page header image-properties from all dummy event pages: code sv:property sv:name=image sv:type=String sv:valuedms/sv:value /sv:property sv:property sv:name=imageDmsUUID sv:type=String sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value /sv:property sv:property sv:name=imageLocation sv:type=String sv:valueabove/sv:value /sv:property /code was (Author: cringele): I had to update all events for demo Pascal gave. So I i changed all events and added some new events, so that the span of dates is over the complete year. Additionally there is one mont of events in the old year, and one month in the coming year. Like this, when the new year (2011) comes, simply all 'year' numbers have to be changes to one year higher. The events configured right now are: - January 2009: 4 events - All months of 2010: 4 events each - January 2011: 4 events I add here the boostrap file of all dummy-events. Additionally I have removed wrong generated page header image-properties from all dummy event pages: code sv:property sv:name=image sv:type=String sv:valuedms/sv:value /sv:property sv:property sv:name=imageDmsUUID sv:type=String sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value /sv:property sv:property sv:name=imageLocation sv:type=String sv:valueabove/sv:value /sv:property /code Demo content: No dummy events for 2010 -- Key: MGNLSTK-557 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-557 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: demoproject Affects Versions: 1.2.1 Reporter: Christian Ringele Assignee: Philipp Bärfuss Fix For: 1.2.x All dummy events in the demo content are events of the year 2009. The events are located under: demo-project/service/dummy-events/ These events should be updated to 2010. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Issue Comment Edited: (MGNLSTK-557) Demo content: No dummy events for 2010
[ http://jira.magnolia-cms.com/browse/MGNLSTK-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=25777#action_25777 ] Christian Ringele edited comment on MGNLSTK-557 at 1/11/10 9:30 AM: I had to update all events for demo Pascal gave. So I i changed all events and added some new events, so that the span of dates is over the complete year. Additionally there is one mont of events in the old year, and one month in the coming year. Like this, when the new year (2011) comes, simply all 'year' numbers have to be changes to one year higher. The events configured right now are: - January 2009: 4 events - All months of 2010: 4 events each - January 2011: 4 events I add here the bootstrap file of all dummy-events. Additionally I have removed wrong generated page header image-properties from all dummy event pages: [code] sv:property sv:name=image sv:type=String sv:valuedms/sv:value /sv:property sv:property sv:name=imageDmsUUID sv:type=String sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value /sv:property sv:property sv:name=imageLocation sv:type=String sv:valueabove/sv:value /sv:property [/code] was (Author: cringele): I had to update all events for demo Pascal gave. So I i changed all events and added some new events, so that the span of dates is over the complete year. Additionally there is one mont of events in the old year, and one month in the coming year. Like this, when the new year (2011) comes, simply all 'year' numbers have to be changes to one year higher. The events configured right now are: - January 2009: 4 events - All months of 2010: 4 events each - January 2011: 4 events I add here the bootstrap file of all dummy-events. Additionally I have removed wrong generated page header image-properties from all dummy event pages: code sv:property sv:name=image sv:type=String sv:valuedms/sv:value /sv:property sv:property sv:name=imageDmsUUID sv:type=String sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value /sv:property sv:property sv:name=imageLocation sv:type=String sv:valueabove/sv:value /sv:property /code Demo content: No dummy events for 2010 -- Key: MGNLSTK-557 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-557 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: demoproject Affects Versions: 1.2.1 Reporter: Christian Ringele Assignee: Philipp Bärfuss Fix For: 1.2.x All dummy events in the demo content are events of the year 2009. The events are located under: demo-project/service/dummy-events/ These events should be updated to 2010. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Issue Comment Edited: (MGNLSTK-557) Demo content: No dummy events for 2010
[
http://jira.magnolia-cms.com/browse/MGNLSTK-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=25777#action_25777
]
Christian Ringele edited comment on MGNLSTK-557 at 1/11/10 9:30 AM:
I had to update all events for demo Pascal gave.
So I i changed all events and added some new events, so that the span of dates
is over the complete year. Additionally there is one mont of events in the old
year, and one month in the coming year.
Like this, when the new year (2011) comes, simply all 'year' numbers have to be
changes to one year higher.
The events configured right now are:
- January 2009: 4 events
- All months of 2010: 4 events each
- January 2011: 4 events
I add here the bootstrap file of all dummy-events.
Additionally I have removed wrong generated page header image-properties from
all dummy event pages:
{code}
sv:property sv:name=image sv:type=String
sv:valuedms/sv:value
/sv:property
sv:property sv:name=imageDmsUUID sv:type=String
sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value
/sv:property
sv:property sv:name=imageLocation sv:type=String
sv:valueabove/sv:value
/sv:property
{code}
was (Author: cringele):
I had to update all events for demo Pascal gave.
So I i changed all events and added some new events, so that the span of dates
is over the complete year. Additionally there is one mont of events in the old
year, and one month in the coming year.
Like this, when the new year (2011) comes, simply all 'year' numbers have to be
changes to one year higher.
The events configured right now are:
- January 2009: 4 events
- All months of 2010: 4 events each
- January 2011: 4 events
I add here the bootstrap file of all dummy-events.
Additionally I have removed wrong generated page header image-properties from
all dummy event pages:
{code
sv:property sv:name=image sv:type=String
sv:valuedms/sv:value
/sv:property
sv:property sv:name=imageDmsUUID sv:type=String
sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value
/sv:property
sv:property sv:name=imageLocation sv:type=String
sv:valueabove/sv:value
/sv:property
}
Demo content: No dummy events for 2010
--
Key: MGNLSTK-557
URL: http://jira.magnolia-cms.com/browse/MGNLSTK-557
Project: Magnolia Standard Templating Kit
Issue Type: Bug
Components: demoproject
Affects Versions: 1.2.1
Reporter: Christian Ringele
Assignee: Philipp Bärfuss
Fix For: 1.2.x
All dummy events in the demo content are events of the year 2009.
The events are located under: demo-project/service/dummy-events/
These events should be updated to 2010.
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Issue Comment Edited: (MGNLSTK-557) Demo content: No dummy events for 2010
[
http://jira.magnolia-cms.com/browse/MGNLSTK-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=25777#action_25777
]
Christian Ringele edited comment on MGNLSTK-557 at 1/11/10 9:30 AM:
I had to update all events for demo Pascal gave.
So I i changed all events and added some new events, so that the span of dates
is over the complete year. Additionally there is one mont of events in the old
year, and one month in the coming year.
Like this, when the new year (2011) comes, simply all 'year' numbers have to be
changes to one year higher.
The events configured right now are:
- January 2009: 4 events
- All months of 2010: 4 events each
- January 2011: 4 events
I add here the bootstrap file of all dummy-events.
Additionally I have removed wrong generated page header image-properties from
all dummy event pages:
{code}
sv:property sv:name=image sv:type=String
sv:valuedms/sv:value
/sv:property
sv:property sv:name=imageDmsUUID sv:type=String
sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value
/sv:property
sv:property sv:name=imageLocation sv:type=String
sv:valueabove/sv:value
/sv:property
{/code}
was (Author: cringele):
I had to update all events for demo Pascal gave.
So I i changed all events and added some new events, so that the span of dates
is over the complete year. Additionally there is one mont of events in the old
year, and one month in the coming year.
Like this, when the new year (2011) comes, simply all 'year' numbers have to be
changes to one year higher.
The events configured right now are:
- January 2009: 4 events
- All months of 2010: 4 events each
- January 2011: 4 events
I add here the bootstrap file of all dummy-events.
Additionally I have removed wrong generated page header image-properties from
all dummy event pages:
[code]
sv:property sv:name=image sv:type=String
sv:valuedms/sv:value
/sv:property
sv:property sv:name=imageDmsUUID sv:type=String
sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value
/sv:property
sv:property sv:name=imageLocation sv:type=String
sv:valueabove/sv:value
/sv:property
[/code]
Demo content: No dummy events for 2010
--
Key: MGNLSTK-557
URL: http://jira.magnolia-cms.com/browse/MGNLSTK-557
Project: Magnolia Standard Templating Kit
Issue Type: Bug
Components: demoproject
Affects Versions: 1.2.1
Reporter: Christian Ringele
Assignee: Philipp Bärfuss
Fix For: 1.2.x
All dummy events in the demo content are events of the year 2009.
The events are located under: demo-project/service/dummy-events/
These events should be updated to 2010.
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Issue Comment Edited: (MGNLSTK-557) Demo content: No dummy events for 2010
[
http://jira.magnolia-cms.com/browse/MGNLSTK-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=25777#action_25777
]
Christian Ringele edited comment on MGNLSTK-557 at 1/11/10 9:31 AM:
I had to update all events for demo Pascal gave.
So I i changed all events and added some new events, so that the span of dates
is over the complete year. Additionally there is one mont of events in the old
year, and one month in the coming year.
Like this, when the new year (2011) comes, simply all 'year' numbers have to be
changes to one year higher.
The events configured right now are:
- January 2009: 4 events
- All months of 2010: 4 events each
- January 2011: 4 events
I add here the bootstrap file of all dummy-events.
Additionally I have removed wrong generated page header image-properties from
all dummy event pages:
{code}
sv:property sv:name=image sv:type=String
sv:valuedms/sv:value
/sv:property
sv:property sv:name=imageDmsUUID sv:type=String
sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value
/sv:property
sv:property sv:name=imageLocation sv:type=String
sv:valueabove/sv:value
/sv:property
{code}
was (Author: cringele):
I had to update all events for demo Pascal gave.
So I i changed all events and added some new events, so that the span of dates
is over the complete year. Additionally there is one mont of events in the old
year, and one month in the coming year.
Like this, when the new year (2011) comes, simply all 'year' numbers have to be
changes to one year higher.
The events configured right now are:
- January 2009: 4 events
- All months of 2010: 4 events each
- January 2011: 4 events
I add here the bootstrap file of all dummy-events.
Additionally I have removed wrong generated page header image-properties from
all dummy event pages:
{code}
sv:property sv:name=image sv:type=String
sv:valuedms/sv:value
/sv:property
sv:property sv:name=imageDmsUUID sv:type=String
sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value
/sv:property
sv:property sv:name=imageLocation sv:type=String
sv:valueabove/sv:value
/sv:property
{code}
Demo content: No dummy events for 2010
--
Key: MGNLSTK-557
URL: http://jira.magnolia-cms.com/browse/MGNLSTK-557
Project: Magnolia Standard Templating Kit
Issue Type: Bug
Components: demoproject
Affects Versions: 1.2.1
Reporter: Christian Ringele
Assignee: Philipp Bärfuss
Fix For: 1.2.x
All dummy events in the demo content are events of the year 2009.
The events are located under: demo-project/service/dummy-events/
These events should be updated to 2010.
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Issue Comment Edited: (MGNLSTK-557) Demo content: No dummy events for 2010
[
http://jira.magnolia-cms.com/browse/MGNLSTK-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=25777#action_25777
]
Christian Ringele edited comment on MGNLSTK-557 at 1/11/10 9:31 AM:
I had to update all events for demo Pascal gave.
So I i changed all events and added some new events, so that the span of dates
is over the complete year. Additionally there is one mont of events in the old
year, and one month in the coming year.
Like this, when the new year (2011) comes, simply all 'year' numbers have to be
changes to one year higher.
The events configured right now are:
- January 2009: 4 events
- All months of 2010: 4 events each
- January 2011: 4 events
I add here the bootstrap file of all dummy-events.
Additionally I have removed wrong generated page header image-properties from
all dummy event pages:
{code}
sv:property sv:name=image sv:type=String
sv:valuedms/sv:value
/sv:property
sv:property sv:name=imageDmsUUID sv:type=String
sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value
/sv:property
sv:property sv:name=imageLocation sv:type=String
sv:valueabove/sv:value
/sv:property
{code}
was (Author: cringele):
I had to update all events for demo Pascal gave.
So I i changed all events and added some new events, so that the span of dates
is over the complete year. Additionally there is one mont of events in the old
year, and one month in the coming year.
Like this, when the new year (2011) comes, simply all 'year' numbers have to be
changes to one year higher.
The events configured right now are:
- January 2009: 4 events
- All months of 2010: 4 events each
- January 2011: 4 events
I add here the bootstrap file of all dummy-events.
Additionally I have removed wrong generated page header image-properties from
all dummy event pages:
{code}
sv:property sv:name=image sv:type=String
sv:valuedms/sv:value
/sv:property
sv:property sv:name=imageDmsUUID sv:type=String
sv:valuecb95ae34-0037-4490-90f5-160809e21542/sv:value
/sv:property
sv:property sv:name=imageLocation sv:type=String
sv:valueabove/sv:value
/sv:property
{code}
Demo content: No dummy events for 2010
--
Key: MGNLSTK-557
URL: http://jira.magnolia-cms.com/browse/MGNLSTK-557
Project: Magnolia Standard Templating Kit
Issue Type: Bug
Components: demoproject
Affects Versions: 1.2.1
Reporter: Christian Ringele
Assignee: Philipp Bärfuss
Fix For: 1.2.x
All dummy events in the demo content are events of the year 2009.
The events are located under: demo-project/service/dummy-events/
These events should be updated to 2010.
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSTK-557) Demo content: No dummy events for 2010
[ http://jira.magnolia-cms.com/browse/MGNLSTK-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MGNLSTK-557: -- Attachment: website.demo-project.service.dummy-events.xml Demo content: No dummy events for 2010 -- Key: MGNLSTK-557 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-557 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: demoproject Affects Versions: 1.2.1 Reporter: Christian Ringele Assignee: Philipp Bärfuss Fix For: 1.2.x Attachments: website.demo-project.service.dummy-events.xml All dummy events in the demo content are events of the year 2009. The events are located under: demo-project/service/dummy-events/ These events should be updated to 2010. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Commented: (MGNLSTK -563) Guidance: How do I create a Paragraph where the same content will be available on all pages?
[ http://jira.magnolia-cms.com/browse/MGNLSTK-563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=25781#action_25781 ] Zdenek Skodik commented on MGNLSTK-563: --- Hi Adam, please move this ticket under Support project and we can have a look at it. Thanks, Zdenek Guidance: How do I create a Paragraph where the same content will be available on all pages? Key: MGNLSTK-563 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-563 Project: Magnolia Standard Templating Kit Issue Type: Task Components: templates Environment: Magnolia version 4.1.1 Reporter: Adam Crow Assignee: Philipp Bärfuss I need to create a new paragraph where the custom content is the same on every page. Do I need to create a new modelClass or can the content be collected from the ftl? If you could point me in the corr3ect direction it would be appreciated, Thanks -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-3001) FactoryUtil/ClassUtil refactorings
FactoryUtil/ClassUtil refactorings -- Key: MAGNOLIA-3001 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3001 Project: Magnolia Issue Type: New Feature Components: core Reporter: Grégory Joseph Assignee: Philipp Bärfuss Fix For: 4.3 * Move these and related classes to their specific package * Extract inner classes to the package * ... -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLGROOVY-1) imports should be kept in console context
imports should be kept in console context - Key: MGNLGROOVY-1 URL: http://jira.magnolia-cms.com/browse/MGNLGROOVY-1 Project: Magnolia Groovy Module Issue Type: Improvement Components: console Reporter: Federico Grilli Assignee: Federico Grilli Priority: Minor Unlike variables, when adding an import to the console, it is not kept in the console context between command executions. Find a way to keep it in context (e.g. by hooking into groovy compilation process as we do now for default imports. See info.magnolia.module.groovy.console.MgnlGroovyConsole.MgnlImportSourceUnitOperation). -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLGROOVY-1) imports should be kept in console context
[ http://jira.magnolia-cms.com/browse/MGNLGROOVY-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MGNLGROOVY-1: - Fix Version/s: 1.1 fix version imports should be kept in console context - Key: MGNLGROOVY-1 URL: http://jira.magnolia-cms.com/browse/MGNLGROOVY-1 Project: Magnolia Groovy Module Issue Type: Improvement Components: console Reporter: Federico Grilli Assignee: Federico Grilli Priority: Minor Fix For: 1.1 Unlike variables, when adding an import to the console, it is not kept in the console context between command executions. Find a way to keep it in context (e.g. by hooking into groovy compilation process as we do now for default imports. See info.magnolia.module.groovy.console.MgnlGroovyConsole.MgnlImportSourceUnitOperation). -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLGROOVY-2) Create tree/dialog for handling scripts in adminCentral
Create tree/dialog for handling scripts in adminCentral --- Key: MGNLGROOVY-2 URL: http://jira.magnolia-cms.com/browse/MGNLGROOVY-2 Project: Magnolia Groovy Module Issue Type: Task Components: tree/dialog Reporter: Federico Grilli Assignee: Federico Grilli Fix For: 1.0 Jira subject should be self-explanatory. Scripts must have their own workspace. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Assigned: (MAGNOLIA-3002) Swappable ClassUtil
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grégory Joseph reassigned MAGNOLIA-3002:
Assignee: Grégory Joseph (was: Philipp Bärfuss)
Swappable ClassUtil
---
Key: MAGNOLIA-3002
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3002
Project: Magnolia
Issue Type: New Feature
Components: core
Reporter: Grégory Joseph
Assignee: Grégory Joseph
Fix For: 4.3
Modules need to be able to provide customized class loading mechanisms
(Groovy integration for instance, but also modules that fix certain
containers' class loading specifities, etc)
This is strongly linked to MAGNOLIA-3001, as it will provide some refactoring
of the impacted classes ({{ClassUtil}}, {{ClasspathResourcesUtil}},
{{FactoryUtil}}, ...)
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-3002) Swappable ClassUtil
Swappable ClassUtil
---
Key: MAGNOLIA-3002
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3002
Project: Magnolia
Issue Type: New Feature
Components: core
Reporter: Grégory Joseph
Assignee: Philipp Bärfuss
Fix For: 4.3
Modules need to be able to provide customized class loading mechanisms (Groovy
integration for instance, but also modules that fix certain containers' class
loading specifities, etc)
This is strongly linked to MAGNOLIA-3001, as it will provide some refactoring
of the impacted classes ({{ClassUtil}}, {{ClasspathResourcesUtil}},
{{FactoryUtil}}, ...)
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3001) FactoryUtil/ClassUtil refactorings
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=25801#action_25801 ] Hudson CI server commented on MAGNOLIA-3001: Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! [magnolia_main-trunk #1171|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1171/] Moved FactoryUtil and inner classes to their own package FactoryUtil/ClassUtil refactorings -- Key: MAGNOLIA-3001 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3001 Project: Magnolia Issue Type: New Feature Components: core Reporter: Grégory Joseph Assignee: Grégory Joseph Fix For: 4.3 * Move these and related classes to their specific package * Extract inner classes to the package * ... -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Assigned: (MAGNOLIA-3001) FactoryUtil/ClassUtil refactorings
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grégory Joseph reassigned MAGNOLIA-3001: Assignee: Grégory Joseph (was: Philipp Bärfuss) FactoryUtil/ClassUtil refactorings -- Key: MAGNOLIA-3001 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3001 Project: Magnolia Issue Type: New Feature Components: core Reporter: Grégory Joseph Assignee: Grégory Joseph Fix For: 4.3 * Move these and related classes to their specific package * Extract inner classes to the package * ... -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] Build failed in Hudson: magnolia -module-groovy » magnolia-module-groovy #42
See
http://hudson.magnolia-cms.com/job/magnolia-module-groovy/info.magnolia$magnolia-module-groovy/42/changes
Changes:
[fgrilli] MGNLGROOVY-2: class for handling scripts Tree in adminCentral +
config files. Declared new script workspace in module descriptor.
--
===[HUDSON REMOTING CAPACITY]=== channel started
Executing Maven: -B -f
http://hudson.magnolia-cms.com/job/magnolia-module-groovy/info.magnolia$magnolia-module-groovy/ws/pom.xml
clean install
[INFO] Scanning for projects...
[INFO]
[INFO] Building magnolia-module-groovy
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory
http://hudson.magnolia-cms.com/job/magnolia-module-groovy/info.magnolia$magnolia-module-groovy/ws/target
[INFO] [enforcer:enforce {execution: enforce}]
[INFO] [setproperty:set-property {execution: currentDate}]
[INFO] Property magnoliaCurrentDate set to value 11. January 2010 (scope:
project)
[INFO] Property magnoliaReleaseDate set to value 11. January 2010 (scope:
project)
[INFO] Property magnoliaNiceVersion set to value 1.0 (Snapshot: 11.01.2010
18:46:42) (scope: project)
[INFO] Property magnoliaNiceName set to value Magnolia Groovy Module (scope:
project)
[INFO] Setting property: classpath.resource.loader.class =
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] Setting property: resource.loader = 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] [remote-resources:process {execution: default}]
[INFO] inceptionYear not specified, defaulting to 2010
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 10 resources
[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO] [compiler:compile]
[INFO] Compiling 7 source files to
http://hudson.magnolia-cms.com/job/magnolia-module-groovy/info.magnolia$magnolia-module-groovy/ws/target/classes
[INFO] [compiler:testCompile {execution: compile-tests}]
[INFO] No sources to compile
[INFO] [resources:testResources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
http://hudson.magnolia-cms.com/job/magnolia-module-groovy/info.magnolia$magnolia-module-groovy/ws/src/test/resources
[INFO] skip non existing resourceDirectory
http://hudson.magnolia-cms.com/job/magnolia-module-groovy/info.magnolia$magnolia-module-groovy/ws/src/test/java
[INFO] Copying 3 resources
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] Surefire report directory:
http://hudson.magnolia-cms.com/job/magnolia-module-groovy/info.magnolia$magnolia-module-groovy/ws/target/surefire-reports
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[HUDSON] Recording test results
[INFO] [jar:jar]
[INFO] Building jar:
http://hudson.magnolia-cms.com/job/magnolia-module-groovy/info.magnolia$magnolia-module-groovy/ws/target/magnolia-module-groovy-1.0-SNAPSHOT.jar
[INFO] [assembly:single {execution: default-assembly}]
[INFO] Building zip:
http://hudson.magnolia-cms.com/job/magnolia-module-groovy/info.magnolia$magnolia-module-groovy/ws/target/magnolia-module-groovy-1.0-SNAPSHOT-bundle.zip
[INFO] Building tar :
http://hudson.magnolia-cms.com/job/magnolia-module-groovy/info.magnolia$magnolia-module-groovy/ws/target/magnolia-module-groovy-1.0-SNAPSHOT-bundle.tar.gz
[INFO] Preparing checkstyle:check
[INFO] Setting property: classpath.resource.loader.class =
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] Setting property: resource.loader = 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] **
[INFO] Starting Jakarta Velocity v1.4
[INFO] RuntimeInstance initializing.
[INFO] Default Properties File:
org/apache/velocity/runtime/defaults/velocity.properties
[INFO] Default ResourceManager initializing. (class
org.apache.velocity.runtime.resource.ResourceManagerImpl)
[INFO] Resource Loader Instantiated:
org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
[INFO] ClasspathResourceLoader : initialization starting.
[INFO] ClasspathResourceLoader : initialization complete.
[INFO] ResourceCache : initialized. (class
org.apache.velocity.runtime.resource.ResourceCacheImpl)
[INFO] Default ResourceManager initialization complete.
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Literal
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro
[INFO] Loaded System Directive:
[magnolia-dev] Build failed in Hudson: magnolia-module-groovy #42
See http://hudson.magnolia-cms.com/job/magnolia-module-groovy/42/changes
Changes:
[fgrilli] MGNLGROOVY-2: class for handling scripts Tree in adminCentral +
config files. Declared new script workspace in module descriptor.
--
A SCM change trigger started this job
Updating
http://svn.magnolia-cms.com/svn/community/modules/magnolia-module-groovy/trunk
A src/main/java/info/magnolia/module/groovy/trees
A
src/main/java/info/magnolia/module/groovy/trees/ScriptsAdminTreeConfig.java
U src/main/resources/META-INF/magnolia/groovy.xml
A
src/main/resources/mgnl-bootstrap/groovy/config.modules.groovy.dialogs.xml
A
src/main/resources/mgnl-bootstrap/groovy/config.modules.groovy.trees.xml
At revision 30725
Parsing POMs
[trunk] $ java -cp
/usr/local/hudson/data/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.324.jar:/usr/local/hudson/maven/apache-maven-2.0.10/boot/classworlds-1.1.jar
hudson.maven.agent.Main /usr/local/hudson/maven/apache-maven-2.0.10
/Library/Tomcat/work/Catalina/hudson.magnolia-cms.com/_/WEB-INF/lib/remoting-1.324.jar
/usr/local/hudson/data/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.324.jar
49701
===[HUDSON REMOTING CAPACITY]=== channel started
Executing Maven: -B -f
http://hudson.magnolia-cms.com/job/magnolia-module-groovy/ws/trunk/pom.xml
clean install
[INFO] Scanning for projects...
[INFO]
[INFO] Building magnolia-module-groovy
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory
http://hudson.magnolia-cms.com/job/magnolia-module-groovy/ws/trunk/target
[INFO] [enforcer:enforce {execution: enforce}]
[INFO] [setproperty:set-property {execution: currentDate}]
[INFO] Property magnoliaCurrentDate set to value 11. January 2010 (scope:
project)
[INFO] Property magnoliaReleaseDate set to value 11. January 2010 (scope:
project)
[INFO] Property magnoliaNiceVersion set to value 1.0 (Snapshot: 11.01.2010
18:46:42) (scope: project)
[INFO] Property magnoliaNiceName set to value Magnolia Groovy Module (scope:
project)
[INFO] Setting property: classpath.resource.loader.class =
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] Setting property: resource.loader = 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] [remote-resources:process {execution: default}]
[INFO] inceptionYear not specified, defaulting to 2010
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 10 resources
[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO] [compiler:compile]
[INFO] Compiling 7 source files to
http://hudson.magnolia-cms.com/job/magnolia-module-groovy/ws/trunk/target/classes
[INFO] [compiler:testCompile {execution: compile-tests}]
[INFO] No sources to compile
[INFO] [resources:testResources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
http://hudson.magnolia-cms.com/job/magnolia-module-groovy/ws/trunk/src/test/resources
[INFO] skip non existing resourceDirectory
http://hudson.magnolia-cms.com/job/magnolia-module-groovy/ws/trunk/src/test/java
[INFO] Copying 3 resources
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] Surefire report directory:
http://hudson.magnolia-cms.com/job/magnolia-module-groovy/ws/trunk/target/surefire-reports
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[HUDSON] Recording test results
[INFO] [jar:jar]
[INFO] Building jar:
http://hudson.magnolia-cms.com/job/magnolia-module-groovy/ws/trunk/target/magnolia-module-groovy-1.0-SNAPSHOT.jar
[INFO] [assembly:single {execution: default-assembly}]
[INFO] Building zip:
http://hudson.magnolia-cms.com/job/magnolia-module-groovy/ws/trunk/target/magnolia-module-groovy-1.0-SNAPSHOT-bundle.zip
[INFO] Building tar :
http://hudson.magnolia-cms.com/job/magnolia-module-groovy/ws/trunk/target/magnolia-module-groovy-1.0-SNAPSHOT-bundle.tar.gz
[INFO] Preparing checkstyle:check
[INFO] Setting property: classpath.resource.loader.class =
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] Setting property: resource.loader = 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] **
[INFO] Starting Jakarta Velocity v1.4
[INFO] RuntimeInstance initializing.
[INFO] Default Properties File:
org/apache/velocity/runtime/defaults/velocity.properties
[INFO] Default ResourceManager
[magnolia-dev] Hudson build is back to normal: magnolia-module-groovy #43
See http://hudson.magnolia-cms.com/job/magnolia-module-groovy/43/changes For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] Hudson build is back to normal: magnolia-module-groovy » magnolia-module-groovy #43
See http://hudson.magnolia-cms.com/job/magnolia-module-groovy/info.magnolia$magnolia-module-groovy/43/changes For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Commented: (MGNLGROOVY-2) Create tree/dialog for handling scripts in adminCentral
[ http://jira.magnolia-cms.com/browse/MGNLGROOVY-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=25802#action_25802 ] Hudson CI server commented on MGNLGROOVY-2: --- Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! [magnolia-module-groovy #43|http://hudson.magnolia-cms.com/job/magnolia-module-groovy/43/] : Moved up license header, else checkstyle and hudson with him/her complain. Create tree/dialog for handling scripts in adminCentral --- Key: MGNLGROOVY-2 URL: http://jira.magnolia-cms.com/browse/MGNLGROOVY-2 Project: Magnolia Groovy Module Issue Type: Task Components: tree/dialog Reporter: Federico Grilli Assignee: Federico Grilli Fix For: 1.0 Jira subject should be self-explanatory. Scripts must have their own workspace. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Resolved: (MGNLSTK-554) freemarker error in search results stk template
[ http://jira.magnolia-cms.com/browse/MGNLSTK-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grégory Joseph resolved MGNLSTK-554. Resolution: Fixed freemarker error in search results stk template Key: MGNLSTK-554 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-554 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: templates Affects Versions: 1.2.1 Environment: Has occurred in Windows development environment and Redhat production instances using magnolia 4.0, 4.1, 4.2.2 Reporter: Matthew Arriaga Assignee: Grégory Joseph Fix For: 1.1.3, 1.2.2, 1.3 Attachments: freemarker_stacktrace_searchResult_ftl.txt * I think there is something in my content that searchResult.ftl doesn't like. * I setup a fresh installation of 4.2.2 and imported my content and was able to reproduce the error after activating the website content to the new install. * If I put quotes around the search term the error always goes away. * I don't always get the error, only on some search terms, although the terms that cause the error, reliably do so. * The error is confusing because I can't find a pattern that indicates what the exact problem with my content is(if that is the cause). * For example... If I search for the word issues I will get 6 results. * If I drop the quotes and search for issues I get the error. * If I search for each of the 6 search result's page titles without quotes, the search results correctly display for each term. * Some search terms will correctly return more than 6 results without using quotes. * I am able to print out the count before the exception is thrown using getCount, so I know the results are there. * I tried plugging in some new numbers for the -Xss value in java_opts, hoping to address the stackoverflow but it didn't work. * I'm still learning freemarker and I am stuck! This is the error I am getting... get(result) failed on instance of info.magnolia.module.templatingkit.search.SearchResultModel The problematic instruction: -- == assignment: result=model.result! [on line 12, column 1 in templating-kit/paragraphs/features/searchResult.ftl] -- Java backtrace for programmers: -- freemarker.template.TemplateModelException: get(result) failed on instance ofinfo.magnolia.module.templatingkit.search.SearchResultModel at freemarker.ext.beans.BeanModel.get(BeanModel.java:223) ... further down the stack trace I see pages of this... Caused by: java.lang.StackOverflowError at java.util.regex.Pattern$Curly.match(Pattern.java:3736) at java.util.regex.Pattern$Curly.match1(Pattern.java:3797) at java.util.regex.Pattern$Curly.match(Pattern.java:3746) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168) at java.util.regex.Pattern$Loop.match(Pattern.java:4295) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4227) at java.util.regex.Pattern$Curly.match0(Pattern.java:3789) at java.util.regex.Pattern$Curly.match(Pattern.java:3744) at java.util.regex.Pattern$Curly.match1(Pattern.java:3797) at java.util.regex.Pattern$Curly.match(Pattern.java:3746) ... -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSTK-554) freemarker error in search results stk template
[ http://jira.magnolia-cms.com/browse/MGNLSTK-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grégory Joseph updated MGNLSTK-554: --- Fix Version/s: 1.1.3 freemarker error in search results stk template Key: MGNLSTK-554 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-554 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: templates Affects Versions: 1.2.1 Environment: Has occurred in Windows development environment and Redhat production instances using magnolia 4.0, 4.1, 4.2.2 Reporter: Matthew Arriaga Assignee: Grégory Joseph Fix For: 1.1.3, 1.2.2, 1.3 Attachments: freemarker_stacktrace_searchResult_ftl.txt * I think there is something in my content that searchResult.ftl doesn't like. * I setup a fresh installation of 4.2.2 and imported my content and was able to reproduce the error after activating the website content to the new install. * If I put quotes around the search term the error always goes away. * I don't always get the error, only on some search terms, although the terms that cause the error, reliably do so. * The error is confusing because I can't find a pattern that indicates what the exact problem with my content is(if that is the cause). * For example... If I search for the word issues I will get 6 results. * If I drop the quotes and search for issues I get the error. * If I search for each of the 6 search result's page titles without quotes, the search results correctly display for each term. * Some search terms will correctly return more than 6 results without using quotes. * I am able to print out the count before the exception is thrown using getCount, so I know the results are there. * I tried plugging in some new numbers for the -Xss value in java_opts, hoping to address the stackoverflow but it didn't work. * I'm still learning freemarker and I am stuck! This is the error I am getting... get(result) failed on instance of info.magnolia.module.templatingkit.search.SearchResultModel The problematic instruction: -- == assignment: result=model.result! [on line 12, column 1 in templating-kit/paragraphs/features/searchResult.ftl] -- Java backtrace for programmers: -- freemarker.template.TemplateModelException: get(result) failed on instance ofinfo.magnolia.module.templatingkit.search.SearchResultModel at freemarker.ext.beans.BeanModel.get(BeanModel.java:223) ... further down the stack trace I see pages of this... Caused by: java.lang.StackOverflowError at java.util.regex.Pattern$Curly.match(Pattern.java:3736) at java.util.regex.Pattern$Curly.match1(Pattern.java:3797) at java.util.regex.Pattern$Curly.match(Pattern.java:3746) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4168) at java.util.regex.Pattern$Loop.match(Pattern.java:4295) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4227) at java.util.regex.Pattern$Curly.match0(Pattern.java:3789) at java.util.regex.Pattern$Curly.match(Pattern.java:3744) at java.util.regex.Pattern$Curly.match1(Pattern.java:3797) at java.util.regex.Pattern$Curly.match(Pattern.java:3746) ... -- 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: dev-list-unsubscr...@magnolia-cms.com
