[magnolia-dev] [JIRA] Issue Comment Edited: (MGNLSTK-557) Demo content: No dummy events for 2010

[JIRA (on behalf of Christian Ringele)]

[ 
http://jira.magnolia-cms.com/browse/MGNLSTK-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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]

  dms


  cb95ae34-0037-4490-90f5-160809e21542


  above

[/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:


  dms


  cb95ae34-0037-4490-90f5-160809e21542


  above


  
> 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: 

[magnolia-dev] [JIRA] Issue Comment Edited: (MGNLSTK-557) Demo content: No dummy events for 2010

[JIRA (on behalf of Christian Ringele)]

[ 
http://jira.magnolia-cms.com/browse/MGNLSTK-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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}

  dms


  cb95ae34-0037-4490-90f5-160809e21542


  above

{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

  dms


  cb95ae34-0037-4490-90f5-160809e21542


  above

}
  
> 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: 

[magnolia-dev] [JIRA] Issue Comment Edited: (MGNLSTK-557) Demo content: No dummy events for 2010

[JIRA (on behalf of Christian Ringele)]

[ 
http://jira.magnolia-cms.com/browse/MGNLSTK-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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}

  dms


  cb95ae34-0037-4490-90f5-160809e21542


  above

{/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]

  dms


  cb95ae34-0037-4490-90f5-160809e21542


  above

[/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: 

[magnolia-dev] [JIRA] Issue Comment Edited: (MGNLSTK-557) Demo content: No dummy events for 2010

[JIRA (on behalf of Christian Ringele)]

[ 
http://jira.magnolia-cms.com/browse/MGNLSTK-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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}
 
  dms


  cb95ae34-0037-4490-90f5-160809e21542


  above

{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}

  dms


  cb95ae34-0037-4490-90f5-160809e21542


  above

{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: 

[magnolia-dev] [JIRA] Issue Comment Edited: (MGNLSTK-557) Demo content: No dummy events for 2010

[JIRA (on behalf of Christian Ringele)]

[ 
http://jira.magnolia-cms.com/browse/MGNLSTK-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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}

  dms


  cb95ae34-0037-4490-90f5-160809e21542


  above

{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}
 
  dms


  cb95ae34-0037-4490-90f5-160809e21542


  above

{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: 

[magnolia-dev] [JIRA] Issue Comment Edited: (MGNLSTK-557) Demo content: No dummy events for 2010

[JIRA (on behalf of Christian Ringele)]

[ 
http://jira.magnolia-cms.com/browse/MGNLSTK-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25777#action_25777
 ] 

Christian Ringele edited comment on MGNLSTK-557 at 1/11/10 9:32 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}

  dms


  cb95ae34-0037-4490-90f5-160809e21542


  above

{code}

or

{code}

  dms


  left

{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}

  dms


  cb95ae34-0037-4490-90f5-160809e21542


  above

{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: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-557) Demo content: No dummy events for 2010

[JIRA (on behalf of Christian Ringele)]

 [ 
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: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-572) JS files should not contain 'dot' in names -> option 'Bypass' on the resource can not work otherwise

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-572:
--

Description: 
All installed JS's containing a 'dot' in their file name are installed with a 
'minus' instead of the 'dot'. (Dot is not allowed in a content node name).
Now when activating the option 'Bypass' on the resource, it is not working 
because is searches for the JS with the 'minus' instead of the 'dot'.
This can only be solved by not having any JS's containing a 'dot' in the file 
name.

  was:
All installed JS's containing a 'dot' in their file name are installed with a 
'minus' instead of the 'dot'. (Dot is not allowed in a content node name).
Now when activating the option 'Bypass' on the resource, it is not working 
because is searches for the JS with the 'minus' instead of the 'dot'.
This can only be soved by not having any JS's containing a 'dot' in the file 
name.


> JS files should not contain 'dot' in names -> option 'Bypass' on the resource 
> can not work otherwise
> 
>
> Key: MGNLSTK-572
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-572
> Project: Magnolia Standard Templating Kit
>  Issue Type: Bug
>  Components: demoproject
>Affects Versions: 1.1.2, 1.2.2, 1.3 M1
>Reporter: Christian Ringele
>Assignee: Philipp Bärfuss
> Fix For: 1.1.3, 1.3, 1.2.x
>
>
> All installed JS's containing a 'dot' in their file name are installed with a 
> 'minus' instead of the 'dot'. (Dot is not allowed in a content node name).
> Now when activating the option 'Bypass' on the resource, it is not working 
> because is searches for the JS with the 'minus' instead of the 'dot'.
> This can only be solved by not having any JS's containing a 'dot' in the file 
> name.

-- 
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] Created: (MGNLSTK-572) JS files should not contain 'dot' in names -> option 'Bypass' on the resource can not work otherwise

[JIRA (on behalf of Christian Ringele)]

JS files should not contain 'dot' in names -> option 'Bypass' on the resource 
can not work otherwise


 Key: MGNLSTK-572
 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-572
 Project: Magnolia Standard Templating Kit
  Issue Type: Bug
  Components: demoproject
Affects Versions: 1.3 M1, 1.2.2, 1.1.2
Reporter: Christian Ringele
Assignee: Philipp Bärfuss
 Fix For: 1.1.3, 1.3, 1.2.x


All installed JS's containing a 'dot' in their file name are installed with a 
'minus' instead of the 'dot'. (Dot is not allowed in a content node name).
Now when activating the option 'Bypass' on the resource, it is not working 
because is searches for the JS with the 'minus' instead of the 'dot'.
This can only be soved by not having any JS's containing a 'dot' in the file 
name.

-- 
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: (MGNLGA-2) Testing: Link tracking doesn't work as expected

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLGA-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele resolved MGNLGA-2.


Fix Version/s: RC-6
   Resolution: Fixed

Is resolved by:

jQuery.noConflict();
(function($){
$(document).ready(function(){
...
}

> Testing: Link tracking doesn't work as expected
> ---
>
> Key: MGNLGA-2
> URL: http://jira.magnolia-cms.com/browse/MGNLGA-2
> Project: Magnolia Google Analytics
>  Issue Type: Bug
>Reporter: Christian Ringele
>Assignee: Christian Ringele
>Priority: Blocker
> Fix For: RC-6
>
> Attachments: Picture 2.png
>
>
> I am testing the GA module on the demo http://demo.magnolia-cms.com/demo 
> instance.
> Generally the tracking of the pages themselves work as expected. All the 
> pages and page hits are tracked and show up in the GA.
> The JS tracking script the module is using is a JQuery plugin (in module JS 
> 'jquery.gatracker.js'). It is supposed to track all links too: external 
> links, download links and mailto links.
> It adds if found, a prefix to the link URL: 'external' or 'downloads' or 
> 'mailtos'.
> Setup:
> - First I tried a advanced tracker function call with more defined file 
> extensions (in module init.gatracker.js').
> - Then I tried the original function call. So its the unchanged JS running as 
> provided by JQuery:
> (function($){
>   $.gaTracker('${trackerID}');
> })(jQuery);
> This call activates the link tracking with the original options defined in 
> the original JS script 'jquery.gatracker.js'.
> Results:
> - External links are never tracked
> - mailto links are never tracked
> - download links are only very seldom tracked:
> Only download links which point to a .jpg provided by the image 
> module/image-zoom generator. See attached file. 
> I think the problem is located within the js function 'function 
> decorateLink(u){'.
> The regex expression within this function does not apply to the links 
> analyzed.

-- 
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: (MGNLGA-4) Remove redundant basic install tasks from extra install tasks in version handler

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLGA-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele resolved MGNLGA-4.


Fix Version/s: RC-6
   Resolution: Fixed

Done

> Remove redundant basic install tasks from extra install tasks in version 
> handler
> 
>
> Key: MGNLGA-4
> URL: http://jira.magnolia-cms.com/browse/MGNLGA-4
> Project: Magnolia Google Analytics
>  Issue Type: Bug
>Reporter: Nils Breunese
>Assignee: Christian Ringele
>Priority: Minor
> Fix For: RC-6
>
>
> The getExtraInstallTasks() method has the following call:
> installTasks.addAll(super.getBasicInstallTasks(ctx));
> This is redundant and should be removed. Please see the thread at 
> http://www.nabble.com/Version-handler-install-tasks-td26011961.html for Jan 
> Haderka's comment.

-- 
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: (MGNLGA-3) Rename GoggleAnalyticsJSResourceModel.java to GoogleAnalyticsJSResourceModel.java

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLGA-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele resolved MGNLGA-3.


Fix Version/s: RC-6
   Resolution: Fixed

Done

> Rename GoggleAnalyticsJSResourceModel.java to 
> GoogleAnalyticsJSResourceModel.java
> -
>
> Key: MGNLGA-3
> URL: http://jira.magnolia-cms.com/browse/MGNLGA-3
> Project: Magnolia Google Analytics
>  Issue Type: Bug
>Reporter: Nils Breunese
>Assignee: Christian Ringele
>Priority: Trivial
> Fix For: RC-6
>
>   Original Estimate: 0.01d
>  Remaining Estimate: 0.01d
>
> Please refactor 
> src/main/java/info/magnolia/module/googleanalytics/model/GoggleAnalyticsJSResourceModel.java
>  to 
> src/main/java/info/magnolia/module/googleanalytics/model/GoogleAnalyticsJSResourceModel.java.

-- 
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] Created: (MAGNOLIA-3108) On Windows only: Changing property name of characters to lower/upper case results in dissapearing propertiy

[JIRA (on behalf of Christian Ringele)]

On Windows only: Changing property name of characters to lower/upper case 
results in dissapearing propertiy
---

 Key: MAGNOLIA-3108
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3108
 Project: Magnolia
  Issue Type: Bug
  Components: core
Affects Versions: 3.6.3
 Environment: Windows 2003 Server
MySQL 5.1
Magnolia 3.6.3
JCR 1.4.5 core
PM: jackrabbit-mysql-search.xml
Reporter: Christian Ringele
Assignee: Christian Ringele


When changing characters of a property's name to lower/upper case, the property 
disappears:
- Change property in JCR from 'test' to 'TEST'
The property disappears and is not stored anymore in MySql.

The same happens when adding a second propert with the same name, just having 
different character in lower/upper case:
- add property 'test'
- add property 'TEST'
-> 'test' remains and 'TEST' disappears

-- 
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-3108) On Windows only: Changing property name of characters to lower/upper case results in dissapearing propertiy

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele resolved MAGNOLIA-3108.
-

Resolution: Workaround exists

First deleting the property and then adding it again with the new name works.
Is a bit cumbersome, but worked to resolve the problem.

> On Windows only: Changing property name of characters to lower/upper case 
> results in dissapearing propertiy
> ---
>
> Key: MAGNOLIA-3108
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3108
> Project: Magnolia
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.6.3
> Environment: Windows 2003 Server
> MySQL 5.1
> Magnolia 3.6.3
> JCR 1.4.5 core
> PM: jackrabbit-mysql-search.xml
>Reporter: Christian Ringele
>Assignee: Christian Ringele
>
> When changing characters of a property's name to lower/upper case, the 
> property disappears:
> - Change property in JCR from 'test' to 'TEST'
> The property disappears and is not stored anymore in MySql.
> The same happens when adding a second propert with the same name, just having 
> different character in lower/upper case:
> - add property 'test'
> - add property 'TEST'
> -> 'test' remains and 'TEST' disappears

-- 
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] Updated: (MAGNOLIA-3108) On Windows only: Changing property name of characters to lower/upper case results in disappearing property

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MAGNOLIA-3108:


Summary: On Windows only: Changing property name of characters to 
lower/upper case results in disappearing property  (was: On Windows only: 
Changing property name of characters to lower/upper case results in disapearing 
property)

> On Windows only: Changing property name of characters to lower/upper case 
> results in disappearing property
> --
>
> Key: MAGNOLIA-3108
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3108
> Project: Magnolia
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.6.3
> Environment: Windows 2003 Server
> MySQL 5.1
> Magnolia 3.6.3
> JCR 1.4.5 core
> PM: jackrabbit-mysql-search.xml
>Reporter: Christian Ringele
>Assignee: Christian Ringele
>
> When changing characters of a property's name to lower/upper case, the 
> property disappears:
> - Change property in JCR from 'test' to 'TEST'
> The property disappears and is not stored anymore in MySql.
> The same happens when adding a second propert with the same name, just having 
> different character in lower/upper case:
> - add property 'test'
> - add property 'TEST'
> -> 'test' remains and 'TEST' disappears

-- 
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] Updated: (MAGNOLIA-3108) On Windows only: Changing property name of characters to lower/upper case results in dissapearing property

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MAGNOLIA-3108:


Summary: On Windows only: Changing property name of characters to 
lower/upper case results in dissapearing property  (was: On Windows only: 
Changing property name of characters to lower/upper case results in 
dissapearing propertiy)

> On Windows only: Changing property name of characters to lower/upper case 
> results in dissapearing property
> --
>
> Key: MAGNOLIA-3108
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3108
> Project: Magnolia
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.6.3
> Environment: Windows 2003 Server
> MySQL 5.1
> Magnolia 3.6.3
> JCR 1.4.5 core
> PM: jackrabbit-mysql-search.xml
>Reporter: Christian Ringele
>Assignee: Christian Ringele
>
> When changing characters of a property's name to lower/upper case, the 
> property disappears:
> - Change property in JCR from 'test' to 'TEST'
> The property disappears and is not stored anymore in MySql.
> The same happens when adding a second propert with the same name, just having 
> different character in lower/upper case:
> - add property 'test'
> - add property 'TEST'
> -> 'test' remains and 'TEST' disappears

-- 
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] Updated: (MAGNOLIA-3108) On Windows only: Changing property name of characters to lower/upper case results in disapearing property

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MAGNOLIA-3108:


Summary: On Windows only: Changing property name of characters to 
lower/upper case results in disapearing property  (was: On Windows only: 
Changing property name of characters to lower/upper case results in 
dissapearing property)

> On Windows only: Changing property name of characters to lower/upper case 
> results in disapearing property
> -
>
> Key: MAGNOLIA-3108
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3108
> Project: Magnolia
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.6.3
> Environment: Windows 2003 Server
> MySQL 5.1
> Magnolia 3.6.3
> JCR 1.4.5 core
> PM: jackrabbit-mysql-search.xml
>Reporter: Christian Ringele
>Assignee: Christian Ringele
>
> When changing characters of a property's name to lower/upper case, the 
> property disappears:
> - Change property in JCR from 'test' to 'TEST'
> The property disappears and is not stored anymore in MySql.
> The same happens when adding a second propert with the same name, just having 
> different character in lower/upper case:
> - add property 'test'
> - add property 'TEST'
> -> 'test' remains and 'TEST' disappears

-- 
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] Reopened: (MAGNOLIA-3108) On Windows only: Changing property name of characters to lower/upper case results in disappearing property

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele reopened MAGNOLIA-3108:
-


> On Windows only: Changing property name of characters to lower/upper case 
> results in disappearing property
> --
>
> Key: MAGNOLIA-3108
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3108
> Project: Magnolia
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.6.3
> Environment: Windows 2003 Server
> MySQL 5.1
> Magnolia 3.6.3
> JCR 1.4.5 core
> PM: jackrabbit-mysql-search.xml
>Reporter: Christian Ringele
>Assignee: Christian Ringele
>
> When changing characters of a property's name to lower/upper case, the 
> property disappears:
> - Change property in JCR from 'test' to 'TEST'
> The property disappears and is not stored anymore in MySql.
> The same happens when adding a second propert with the same name, just having 
> different character in lower/upper case:
> - add property 'test'
> - add property 'TEST'
> -> 'test' remains and 'TEST' disappears

-- 
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-3108) On Windows only: Changing property name of characters to lower/upper case results in disappearing property

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele resolved MAGNOLIA-3108.
-

Resolution: Workaround exists

Another work around is switching to the PM: jackrabbit-bundle-mysql-search.xml

For that a export/import of the data has to be done between the PM switching.

> On Windows only: Changing property name of characters to lower/upper case 
> results in disappearing property
> --
>
> Key: MAGNOLIA-3108
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3108
> Project: Magnolia
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.6.3
> Environment: Windows 2003 Server
> MySQL 5.1
> Magnolia 3.6.3
> JCR 1.4.5 core
> PM: jackrabbit-mysql-search.xml
>Reporter: Christian Ringele
>Assignee: Christian Ringele
>
> When changing characters of a property's name to lower/upper case, the 
> property disappears:
> - Change property in JCR from 'test' to 'TEST'
> The property disappears and is not stored anymore in MySql.
> The same happens when adding a second propert with the same name, just having 
> different character in lower/upper case:
> - add property 'test'
> - add property 'TEST'
> -> 'test' remains and 'TEST' disappears

-- 
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] Created: (MGNLRES-34) Code higlight editor: crashed on styles.css (many lines) in most browsers

[JIRA (on behalf of Christian Ringele)]

Code higlight editor: crashed on styles.css (many lines) in most browsers
-

 Key: MGNLRES-34
 URL: http://jira.magnolia-cms.com/browse/MGNLRES-34
 Project: Magnolia Resources Module
  Issue Type: Bug
Affects Versions: 1.4
Reporter: Christian Ringele
Assignee: Federico Grilli
 Fix For: 1.4.1


When opening the STK's styles.css within the resources module, most browsers 
crash.
It seems that the code highlighting is the cause.

Summary of tested browsers:
Browser / Windows / OsX
Firefox 4.0: crash / works
Chrome: crash / crash
IE 8.0: works / -
Safari 5: - / crash

-- 
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] Updated: (MGNLSTK-785) Footer about element can't render images without title

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-785:
--

Fix Version/s: 1.3.x

> Footer about element can't render images without title
> --
>
> Key: MGNLSTK-785
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-785
> Project: Magnolia Standard Templating Kit
>  Issue Type: Bug
>  Components: paragraphs
>Affects Versions: 1.4.4
>Reporter: Grégory Joseph
>Assignee: Christian Ringele
> Fix For: 1.3.x, 1.4.5
>
>
> In {{/templating-kit/paragraphs/footer/footerAbout.ftl}}, the following can't 
> work for assets that don't have a title:
> {code}
> [#assign imageAlt = image.title!image.@name]
> {code}
> {{image}} in this case is an instance of 
> {{info.magnolia.module.templatingkit.dam.Asset}}; a dms asset "always" has a 
> title (since the title property is automatically filled in on creation in the 
> tree), while an uploaded asset never does. The expression above thus falls 
> back to {{@name}}, which can't be interpreted either, as there is no such 
> property ({{image}} is an {{Asset}}, not a node).
> Trivial fix:
> {code}
> [#assign imageAlt = image.title!image.name]
> {code}

-- 
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
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Created: (MGNLSTK-789) Create basic AbstractSTKRenderTestCase based on AbstractRenderTestCase as a base for template script render tests

[JIRA (on behalf of Christian Ringele)]

Create basic AbstractSTKRenderTestCase based on AbstractRenderTestCase as a 
base for template script render tests 
--

 Key: MGNLSTK-789
 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-789
 Project: Magnolia Standard Templating Kit
  Issue Type: Improvement
Affects Versions: 1.4.5, 1.4.x
Reporter: Christian Ringele
Assignee: Christian Ringele
 Fix For: 1.4.5




-- 
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
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-789) Create basic AbstractSTKRenderTestCase based on AbstractRenderTestCase

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-789:
--

Summary: Create basic AbstractSTKRenderTestCase based on 
AbstractRenderTestCase  (was: Create basic AbstractSTKRenderTestCase based on 
AbstractRenderTestCase as a base for template script render tests )
Component/s: build

> Create basic AbstractSTKRenderTestCase based on AbstractRenderTestCase
> --
>
> Key: MGNLSTK-789
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-789
> Project: Magnolia Standard Templating Kit
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 1.4.5, 1.4.x
>Reporter: Christian Ringele
>Assignee: Christian Ringele
> Fix For: 1.4.5
>
>


-- 
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
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Created: (MGNLSTK-790) RedirectTemplate should provide a uuidLink and s possibility for automatic redirection to last child.

[JIRA (on behalf of Christian Ringele)]

RedirectTemplate should provide a uuidLink and s possibility for automatic 
redirection to last child. 
--

 Key: MGNLSTK-790
 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-790
 Project: Magnolia Standard Templating Kit
  Issue Type: Improvement
  Components: templates
Affects Versions: 1.4.x
Reporter: Christian Ringele
Assignee: Philipp Bärfuss
 Fix For: 1.4.x


This issue is related to (linked too): MGNLSTK-772
Of issue MGNLSTK-772 everything is implemented in 4.4.5, what was possible in a 
minor release.

So this ticket is created for the next major version, for implementing of what 
is left over to implement:
- Provide a possibility of linking by uuid and not only by path.
- Provide automatic redirect to last child (first child is implemented).


-- 
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
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-790) RedirectTemplate should provide a uuidLink and s possibility for automatic redirection to last child.

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-790:
--

Description: 
This issue is related to: MGNLSTK-772
Of issue MGNLSTK-772 everything is implemented in 4.4.5, what was possible in a 
minor release.

So this ticket is created for the next major version, for implementing of what 
is left over to implement:
- Provide a possibility of linking by uuid and not only by path.
- Provide automatic redirect to last child (first child is implemented).


  was:
This issue is related to (linked too): MGNLSTK-772
Of issue MGNLSTK-772 everything is implemented in 4.4.5, what was possible in a 
minor release.

So this ticket is created for the next major version, for implementing of what 
is left over to implement:
- Provide a possibility of linking by uuid and not only by path.
- Provide automatic redirect to last child (first child is implemented).



> RedirectTemplate should provide a uuidLink and s possibility for automatic 
> redirection to last child. 
> --
>
> Key: MGNLSTK-790
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-790
> Project: Magnolia Standard Templating Kit
>  Issue Type: Improvement
>  Components: templates
>Affects Versions: 1.4.x
>Reporter: Christian Ringele
>Assignee: Philipp Bärfuss
> Fix For: 1.4.x
>
>
> This issue is related to: MGNLSTK-772
> Of issue MGNLSTK-772 everything is implemented in 4.4.5, what was possible in 
> a minor release.
> So this ticket is created for the next major version, for implementing of 
> what is left over to implement:
> - Provide a possibility of linking by uuid and not only by path.
> - Provide automatic redirect to last child (first child is implemented).

-- 
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
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-775) All dummy events have old date: no events are showing in EventsOverview, should be updated

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-775:
--

Summary: All dummy events have old date: no events are showing in 
EventsOverview, should be updated  (was: All dummy events have old date: no 
events are shoing in EventsOverview, should be updated)

> All dummy events have old date: no events are showing in EventsOverview, 
> should be updated
> --
>
> Key: MGNLSTK-775
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-775
> Project: Magnolia Standard Templating Kit
>  Issue Type: Improvement
>  Components: demoproject
>Affects Versions: 1.4.3
>Reporter: Christian Ringele
>Assignee: Christian Ringele
> Fix For: 1.4.5
>
>
> All dummy events (located in /demo-project/service/dummy-events/) should be 
> updated date wise.
> Otherwise no events are showing up in the event-overview pages & paragraphs.

-- 
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
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Created: (DOCU-212) Handling public user generated content

[JIRA (on behalf of Christian Ringele)]

Handling public user generated content
--

 Key: DOCU-212
 URL: http://jira.magnolia-cms.com/browse/DOCU-212
 Project: Documentation
  Issue Type: Sub-task
  Security Level: Public
Reporter: Christian Ringele
Assignee: Antti Hietala


Public user generated content is not an easy topic.
When pages are server by more than one public instance, JCR clustered repo 
needs to be used.

-- 
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
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Created: (MGNLGROOVY-50) GroovyScript install task for installing groovy scripts from module's resources into the groovy repp

[JIRA (on behalf of Christian Ringele)]

GroovyScript install task for installing groovy scripts from module's resources 
into the groovy repp


 Key: MGNLGROOVY-50
 URL: http://jira.magnolia-cms.com/browse/MGNLGROOVY-50
 Project: Magnolia Groovy Module
  Issue Type: New Feature
  Components: integration
Affects Versions: 1.1.2
Reporter: Christian Ringele
Assignee: Federico Grilli
 Fix For: 1.1.3


Would be nice to have an install tasks for groovy scripts located within a 
modules resources.
By that it would be very easy providing within a module scripts, and then have 
them installed automatically by the modules 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
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Created: (MGNLSTK-806) Dummy Events should get created also for the demo-features

[JIRA (on behalf of Christian Ringele)]

Dummy Events should get created also for the demo-features
--

 Key: MGNLSTK-806
 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-806
 Project: Magnolia Standard Templating Kit
  Issue Type: Bug
  Components: demoproject
Affects Versions: 2.0
Reporter: Christian Ringele
Assignee: Christian Ringele
 Fix For: 1.4.x, 2.0




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira





For list details see
http://www.magnolia-cms.com/community/mailing-lists.html
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Created: (MGNLSTK-809) Demo project: Dummy event create in abstract 'r√©sum√©' instead of 'résumé'

[JIRA (on behalf of Christian Ringele)]

Demo project: Dummy event create in abstract 'r√©sum√©' instead of 'résumé'
---

 Key: MGNLSTK-809
 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-809
 Project: Magnolia Standard Templating Kit
  Issue Type: Bug
  Components: demoproject
Affects Versions: 1.4.5, 2.0
Reporter: Christian Ringele
Assignee: Christian Ringele
 Fix For: 1.4.6, 2.0




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

   



For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Reopened: (MGNLSTK-809) Demo project: Dummy event create in abstract 'r√©sum√©' instead of 'résumé'

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele reopened MGNLSTK-809:
---


> Demo project: Dummy event create in abstract 'r√©sum√©' instead of 'résumé'
> ---
>
> Key: MGNLSTK-809
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-809
> Project: Magnolia Standard Templating Kit
>  Issue Type: Bug
>  Components: demoproject
>Affects Versions: 1.4.5, 2.0
>Reporter: Christian Ringele
>Assignee: Christian Ringele
> Fix For: 1.4.6, 2.0
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

   



For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Created: (BLOSSOM-49) svn:ignores for all blossom modules

[JIRA (on behalf of Christian Ringele)]

svn:ignores for all blossom modules
---

 Key: BLOSSOM-49
 URL: http://jira.magnolia-cms.com/browse/BLOSSOM-49
 Project: Magnolia Blossom Module
  Issue Type: Improvement
Affects Versions: 1.2.3
Reporter: Christian Ringele
Assignee: Christian Ringele
 Fix For: 1.2.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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Created: (MGNLDATA-136) adding svn:ignores

[JIRA (on behalf of Christian Ringele)]

adding svn:ignores
--

 Key: MGNLDATA-136
 URL: http://jira.magnolia-cms.com/browse/MGNLDATA-136
 Project: Magnolia Data Module
  Issue Type: Improvement
Affects Versions: 1.6.x
Reporter: Christian Ringele
Assignee: Christian Ringele
 Fix For: 1.6.5




-- 
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: 

[magnolia-dev] [JIRA] Created: (MGNLSCH-21) adding svn:ignores to the module

[JIRA (on behalf of Christian Ringele)]

adding svn:ignores to the module


 Key: MGNLSCH-21
 URL: http://jira.magnolia-cms.com/browse/MGNLSCH-21
 Project: Magnolia Scheduler Module
  Issue Type: Improvement
Affects Versions: 1.4.2
Reporter: Christian Ringele
Assignee: Christian Ringele
 Fix For: 1.4.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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-811) STK demo events have lost correct content encoding (possibly also affects other data)

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-811:
--

Fix Version/s: 1.4.6

> STK demo events have lost correct content encoding (possibly also affects 
> other data)
> -
>
> Key: MGNLSTK-811
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-811
> Project: Magnolia Standard Templating Kit
>  Issue Type: Task
>Affects Versions: 1.4.5
>Reporter: Boris Kraft
>Assignee: Philipp Bärfuss
> Attachments: Screen Shot 2011-11-07 at 13.32.30.png
>
>
> The dummy events have an encoding problem in the content. See attached 
> screenshot. This content is in the event "abstract". The abstracts of the 
> standard content (e.g. article template) does not have the problem. 
> This is an out of the box EE 4.4.5 installation on OSX.

-- 
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: 

[magnolia-dev] [JIRA] Created: (MGNLSTK-813) 2rd Teaser in pagination carousel links to Glossary instead of Multistep form example

[JIRA (on behalf of Christian Ringele)]

2rd Teaser in pagination carousel links to Glossary instead of Multistep form 
example
-

 Key: MGNLSTK-813
 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-813
 Project: Magnolia Standard Templating Kit
  Issue Type: Bug
  Components: demoproject
Affects Versions: 1.4.5
Reporter: Christian Ringele
Assignee: Ondřej Chytil
 Fix For: 1.4.6
 Attachments: Screen shot 2011-11-16 at 10.03.51 AM.png

On the home/welcome page -> stage carousel -> second teaser
This teaser teases the new multi-step form.
But it links to the glossary page instead.
The right target would be:
http://demo.magnolia-cms.com/demo-features/special-templates/multi-step-form.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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-813) 2rd Teaser in pagination carousel links to Glossary instead of Multistep form example

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-813:
--

Attachment: Screen shot 2011-11-16 at 10.03.51 AM.png

> 2rd Teaser in pagination carousel links to Glossary instead of Multistep form 
> example
> -
>
> Key: MGNLSTK-813
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-813
> Project: Magnolia Standard Templating Kit
>  Issue Type: Bug
>  Components: demoproject
>Affects Versions: 1.4.5
>Reporter: Christian Ringele
>Assignee: Ondřej Chytil
> Fix For: 1.4.6
>
> Attachments: Screen shot 2011-11-16 at 10.03.51 AM.png
>
>
> On the home/welcome page -> stage carousel -> second teaser
> This teaser teases the new multi-step form.
> But it links to the glossary page instead.
> The right target would be:
> http://demo.magnolia-cms.com/demo-features/special-templates/multi-step-form.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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-691) Glossary Letter Template not available in Template drop-down menu

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-691:
--

Comment: was deleted

(was: This is a bug in TemplatesAvailability.
The cause is, that Glossary is catergory feature, and GlossaryTemr is section.
But the TemplatesAvilability class does not allow a section to be added below a 
feature page (which should be).

Change

{code}
if(category.equals(TemplateCategory.SECTION) || 
category.equals(TemplateCategory.HOME) || 
category.equals(TemplateCategory.FUNCTIONAL)){
return parentTemplateCategory.equals(TemplateCategory.HOME) || 
parentTemplateCategory.equals(TemplateCategory.SECTION) || 
parentTemplateCategory.equals(TemplateCategory.FUNCTIONAL));
}
{code}
to
{code}
if(category.equals(TemplateCategory.SECTION) || 
category.equals(TemplateCategory.HOME) || 
category.equals(TemplateCategory.FUNCTIONAL)){
return parentTemplateCategory.equals(TemplateCategory.HOME) || 
parentTemplateCategory.equals(TemplateCategory.SECTION) || 
parentTemplateCategory.equals(TemplateCategory.FUNCTIONAL)|| 
parentTemplateCategory.equals(TemplateCategory.FEATURE);
}
{code})

> Glossary Letter Template not available in Template drop-down menu
> -
>
> Key: MGNLSTK-691
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-691
> Project: Magnolia Standard Templating Kit
>  Issue Type: Bug
>  Components: demoproject, templates
>Affects Versions: 1.3.5
>Reporter: Matt Dertinger
> Fix For: 1.4.x
>
> Attachments: glossary-letter-template-unavailable.png
>
>
> Hi,
> If someone mistakenly clicks on the template column for a page that uses the 
> Glossary Letter template, they won't be able to change the template back to 
> Glossary Letter.  This happens on the demoauthor.magnolia-cms.com site as 
> well.
> h2. Steps to reproduce
> # Log in to AdminCentral
> # Navigate to {{website/demo-project/service/glossary/a}}
> # {{Double-click}} on the {{template}} column
> # Notice that the Glossary Letter template is not available as an option (See 
> attached screenshot).
> Please let me know if you need more information.
> h2. Possible Remedy
> Would it be possible to update {{TemplateCategoryUtil}} to only allow 
> templates with a {{subcategory}} of {{glossaryLetter}} under pages that have 
> a template with a {{subcategory}} of {{glossary}}. In other words, the only 
> allowable template under {{stkGlossary}} should be {{stkGlossaryLetter}}.  
> Likewise, the only allowable template under {{stkGlossaryLetter}} should be 
> {{stkGlossaryTerm}}.  
> Does this make sense?
> Thanks,
> Matt

-- 
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: 

[magnolia-dev] [JIRA] Created: (MAGNOLIA-4071) Activation: keypair.properties gets created in the wrong directlory -> /apache-tomcat-6.0.32/bin/WEB-INF/config/default/keypair.properties

[JIRA (on behalf of Christian Ringele)]

Activation: keypair.properties gets created in the wrong directlory -> 
/apache-tomcat-6.0.32/bin/WEB-INF/config/default/keypair.properties
--

 Key: MAGNOLIA-4071
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4071
 Project: Magnolia
  Issue Type: Bug
  Security Level: Public
  Components: activation
Affects Versions: 4.5.1, 4.5
Reporter: Christian Ringele
Assignee: Philipp Bärfuss
 Fix For: 4.5.2


The configuration in the magnolia.properties file:
magnolia.author.key.location=WEB-INF/config/default/keypair.properties

should create the file 'keypair.properties' relative within the WEB-INF lib 
folder.
So correct would be:
apache-tomcat-6.0.32/webapps/magnoliaAuthor/WEB-INF/config/default/keypair.properties

But the file gets created in:
apache-tomcat-6.0.32/bin/WEB-INF/config/default/keypair.properties

There for depending on the write rights on the bin folder of the the file can't 
be created. Usually the webapplication process doesn't have write writes to 
tomcat's bin folder -> activation fails.


-- 
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: 

[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4068) Activation keypair file is generated in "current" directory

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-4068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MAGNOLIA-4068:


Comment: was deleted

(was: Prefixing it with:
magnolia.author.key.location=${magnolia.home}/WEB-INF/config/default/keypair.properties

Doesn't help, still the same error.
)

> Activation keypair file is generated in "current" directory
> ---
>
> Key: MAGNOLIA-4068
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4068
> Project: Magnolia
>  Issue Type: Bug
>  Security Level: Public
>  Components: activation, core
>Affects Versions: 4.5.1
>Reporter: Grégory Joseph
>Assignee: Philipp Bärfuss
>Priority: Critical
> Fix For: 4.5.2
>
>
> If you start Tomcat from the {{bin/}} directory, the result is that you'll 
> have {{/bin/WEB-INF/config/default/keypair.properties}}. Fun 
> story, if the next time around, you start the same instance from a different 
> location, the key won't be found.
> Two issues, probably:
> * the default value for {{magnolia.author.key.location}} is a relative path 
> ({{WEB-INF/config/default/keypair.properties}}. Prefixing it with 
> {{$\{magnolia.home\}}} would be a quick and simple solution.
> * the value is used with {{new File(..path..)}}; use one of the many methods 
> we have lying around to make sure we use an absolute path, or that a relative 
> path is relative to the webapp's root and not the *current directory*.

-- 
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: 

[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4071) Activation: keypair.properties gets created in the wrong directlory -> /apache-tomcat-6.0.32/bin/WEB-INF/config/default/keypair.properties

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-4071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MAGNOLIA-4071:


Comment: was deleted

(was: Prefixing it with:
magnolia.author.key.location=${magnolia.home}/WEB-INF/config/default/keypair.properties

Doesn't help, still the same error.)

> Activation: keypair.properties gets created in the wrong directlory -> 
> /apache-tomcat-6.0.32/bin/WEB-INF/config/default/keypair.properties
> --
>
> Key: MAGNOLIA-4071
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4071
> Project: Magnolia
>  Issue Type: Bug
>  Security Level: Public
>  Components: activation
>Affects Versions: 4.5, 4.5.1
>Reporter: Christian Ringele
>Assignee: Jan Haderka
> Fix For: 4.5.2
>
>
> The configuration in the magnolia.properties file:
> magnolia.author.key.location=WEB-INF/config/default/keypair.properties
> should create the file 'keypair.properties' relative within the WEB-INF lib 
> folder.
> So correct would be:
> apache-tomcat-6.0.32/webapps/magnoliaAuthor/WEB-INF/config/default/keypair.properties
> But the file gets created in:
> apache-tomcat-6.0.32/bin/WEB-INF/config/default/keypair.properties
> There for depending on the write rights on the bin folder of the the file 
> can't be created. Usually the webapplication process doesn't have write 
> writes to tomcat's bin folder -> activation fails.

-- 
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: 

[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4071) Activation: keypair.properties gets created in the wrong directlory -> /apache-tomcat-6.0.32/bin/WEB-INF/config/default/keypair.properties

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-4071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MAGNOLIA-4071:


Priority: Blocker  (was: Neutral)

> Activation: keypair.properties gets created in the wrong directlory -> 
> /apache-tomcat-6.0.32/bin/WEB-INF/config/default/keypair.properties
> --
>
> Key: MAGNOLIA-4071
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4071
> Project: Magnolia
>  Issue Type: Bug
>  Security Level: Public
>  Components: activation
>Affects Versions: 4.5, 4.5.1
>Reporter: Christian Ringele
>Assignee: Jan Haderka
>Priority: Blocker
> Fix For: 4.5.2
>
>
> The configuration in the magnolia.properties file:
> magnolia.author.key.location=WEB-INF/config/default/keypair.properties
> should create the file 'keypair.properties' relative within the WEB-INF lib 
> folder.
> So correct would be:
> apache-tomcat-6.0.32/webapps/magnoliaAuthor/WEB-INF/config/default/keypair.properties
> But the file gets created in:
> apache-tomcat-6.0.32/bin/WEB-INF/config/default/keypair.properties
> There for depending on the write rights on the bin folder of the the file 
> can't be created. Usually the webapplication process doesn't have write 
> writes to tomcat's bin folder -> activation fails.

-- 
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: 

[magnolia-dev] [JIRA] Created: (MGNLPUR-66) Protected Page does not redirect to the login page

[JIRA (on behalf of Christian Ringele)]

Protected Page does not redirect to the login page
--

 Key: MGNLPUR-66
 URL: http://jira.magnolia-cms.com/browse/MGNLPUR-66
 Project: Magnolia Public User Registration
  Issue Type: Bug
Affects Versions: 1.4.1
Reporter: Christian Ringele
Assignee: Grégory Joseph
Priority: Critical
 Fix For: 1.4.x


When trying to access:
http://demopublic.magnolia-cms.com/demo-project/members-area/protected.html

The login page does not appear.
Probably the security filter does not use correctly the client call back for 
failed ACL.
When trying to access directly the login page:
http://demopublic.magnolia-cms.com/demo-project/members-area/login.html

The login form appears correctly and a login is possible.

-- 
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: 

[magnolia-dev] [JIRA] Updated: (MGNLPUR-66) Protected Page does not redirect to the login page

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLPUR-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLPUR-66:
-

Assignee: Ondřej Chytil  (was: Grégory Joseph)

> Protected Page does not redirect to the login page
> --
>
> Key: MGNLPUR-66
> URL: http://jira.magnolia-cms.com/browse/MGNLPUR-66
> Project: Magnolia Public User Registration
>  Issue Type: Bug
>Affects Versions: 1.4.1
>Reporter: Christian Ringele
>Assignee: Ondřej Chytil
>Priority: Critical
> Fix For: 1.4.x
>
>
> When trying to access:
> http://demopublic.magnolia-cms.com/demo-project/members-area/protected.html
> The login page does not appear.
> Probably the security filter does not use correctly the client call back for 
> failed ACL.
> When trying to access directly the login page:
> http://demopublic.magnolia-cms.com/demo-project/members-area/login.html
> The login form appears correctly and a login is possible.

-- 
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: 

[magnolia-dev] [JIRA] Created: (MGNLSTK-949) Navigation: Start levels should be definable. Also the SiteNavigationModel used should be injected by IOC and not with 'new'

[JIRA (on behalf of Christian Ringele)]

Navigation: Start levels should be definable. Also the SiteNavigationModel used 
should be injected by IOC and not with 'new'


 Key: MGNLSTK-949
 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-949
 Project: Magnolia Standard Templating Kit
  Issue Type: Improvement
  Components: concept, templates
Affects Versions: 2.0.2
Reporter: Christian Ringele
Assignee: Eric Hechinger
Priority: Major
 Fix For: 2.0.3


In training, I get often confronted with a need of STK regarding the Navigation.
On many pages out there, the vertical navigation displays the same pages as the 
horizontal navigation.
For example when the horizontal provides a dropdown based Navigation, that the 
displayed drop down level is the same as the starting level of the vertical 
navigation.

The implementation within STK is, that you cant define a starting level of the 
vertical navigation. It will always start one level below what the horizontal 
navigation displays. (line 89 of SiteNavigationModel)
I think the start level of the vertical navigation should be definable.

When trying to solve this problem within the code just for a project, I 
encountered the problem that I cannot inject a different SiteNavigationModel 
without using for EVERY stk page template a different STKPageMOdel class, 
because the STKPAgeModel does a 'new' allocation of the SiteNavigationModel 
instead of getting it by Components.

Line 88 in STKPageModel
{code}
public SiteNavigationModel getNavigation() {
return new SiteNavigationModel(getDefinition().getNavigation(), 
getSiteRoot(), content);
}
{code}

-- 
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: 

[magnolia-dev] [JIRA] Created: (MGNLSTK-951) Disabling ExtrasArea without need to define class property: BodyClassResolver should first check if enabled, then cast.

[JIRA (on behalf of Christian Ringele)]

Disabling ExtrasArea without need to define class property: BodyClassResolver 
should first check if enabled, then cast.
---

 Key: MGNLSTK-951
 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-951
 Project: Magnolia Standard Templating Kit
  Issue Type: Improvement
  Components: base system, themepop
Affects Versions: 2.0.2, 2.0.1, 2.0
Reporter: Christian Ringele
Assignee: Christian Ringele
Priority: Major
 Fix For: 2.0.3


Disabling the extras area is the most common use case on templates, besides 
reconfigure it.
When disabling the extras area by adding the property enabled=false, a class 
cast exception happens in the BodyClassResolver.
Without the definition of the specific bean by the class property, the code 
does not work.
But it is really really hard for people to find out why they get the freemarker 
error without the class property, and then to find out what class to use.

The new code uses first a default AreaDefintion for checking the .isEnabled() 
value, and then casts within the if.

-- 
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: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-951) Disabling ExtrasArea without need to define class property: BodyClassResolver should first check if enabled, then cast.

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-951:
--

Patch included: [Yes]
Attachment: BodyClassResolver.txt

> Disabling ExtrasArea without need to define class property: BodyClassResolver 
> should first check if enabled, then cast.
> ---
>
> Key: MGNLSTK-951
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-951
> Project: Magnolia Standard Templating Kit
>  Issue Type: Improvement
>  Components: base system, themepop
>Affects Versions: 2.0, 2.0.1, 2.0.2
>Reporter: Christian Ringele
>Assignee: Christian Ringele
>Priority: Major
> Fix For: 2.0.3
>
> Attachments: BodyClassResolver.txt
>
>
> Disabling the extras area is the most common use case on templates, besides 
> reconfigure it.
> When disabling the extras area by adding the property enabled=false, a class 
> cast exception happens in the BodyClassResolver.
> Without the definition of the specific bean by the class property, the code 
> does not work.
> But it is really really hard for people to find out why they get the 
> freemarker error without the class property, and then to find out what class 
> to use.
> The new code uses first a default AreaDefintion for checking the .isEnabled() 
> value, and then casts within the if.

-- 
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: 

[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4413) GZip filter breaks cached forms in chrome: stange binary content at bottom

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MAGNOLIA-4413:


Attachment: StrangeBinaryContent.png

> GZip filter breaks cached forms in chrome: stange binary content at bottom
> --
>
> Key: MAGNOLIA-4413
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4413
> Project: Magnolia
>  Issue Type: Bug
>  Security Level: Public
>  Components: cache, core
>Affects Versions: 4.4.7, 4.5.2
>Reporter: Christian Ringele
>Priority: Critical
> Fix For: 4.5.x
>
> Attachments: StrangeBinaryContent.png
>
>
> Open in chrome (not logged in, needs to be server from the cache) th4e 
> contact form:
> http://demopublic.magnolia-cms.com/.magnolia/pages/adminCentral.html
> See the print screen. At the bottom stange binary content is rendered.
> Only in chrome, works in firefox and safari.
> 1. Disable the gzip filter, problem gone.
> 2 or: server the form not form cache by adding ?dijnsi to the url, problem 
> gone.
> Seems its the combination that the cahch gzipes, and the gzip filter gzipes 
> somehow also, or at least manipulates the http header wrong.

-- 
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: 

[magnolia-dev] [JIRA] Created: (MAGNOLIA-4413) GZip filter breaks cached forms in chrome: stange binary content at bottom

[JIRA (on behalf of Christian Ringele)]

GZip filter breaks cached forms in chrome: stange binary content at bottom
--

 Key: MAGNOLIA-4413
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4413
 Project: Magnolia
  Issue Type: Bug
  Security Level: Public
  Components: cache, core
Affects Versions: 4.5.2, 4.4.7
Reporter: Christian Ringele
Priority: Critical
 Fix For: 4.5.x
 Attachments: StrangeBinaryContent.png

Open in chrome (not logged in, needs to be server from the cache) th4e contact 
form:
http://demopublic.magnolia-cms.com/.magnolia/pages/adminCentral.html

See the print screen. At the bottom stange binary content is rendered.
Only in chrome, works in firefox and safari.

1. Disable the gzip filter, problem gone.
2 or: server the form not form cache by adding ?dijnsi to the url, problem gone.
Seems its the combination that the cahch gzipes, and the gzip filter gzipes 
somehow also, or at least manipulates the http header wrong.

-- 
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: 

[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4413) GZip filter breaks cached forms in chrome: stange binary content at bottom

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MAGNOLIA-4413:


Description: 
Open in chrome (not logged in, needs to be server from the cache) the contact 
form:
http://demopublic.magnolia-cms.com/demo-project/service/contact.html

See the print screen. At the bottom strange binary content is rendered.
Only in chrome, works in firefox and safari.

1. Disable the gzip filter, problem gone.
2 or: server the form not form cache by adding ?something to the url, problem 
gone.
Seems its the combination that the cahche gzipes, and the gzip filter gzipes 
somehow also, or at least manipulates the http header wrong.

  was:
Open in chrome (not logged in, needs to be server from the cache) th4e contact 
form:
http://demopublic.magnolia-cms.com/.magnolia/pages/adminCentral.html

See the print screen. At the bottom stange binary content is rendered.
Only in chrome, works in firefox and safari.

1. Disable the gzip filter, problem gone.
2 or: server the form not form cache by adding ?dijnsi to the url, problem gone.
Seems its the combination that the cahch gzipes, and the gzip filter gzipes 
somehow also, or at least manipulates the http header wrong.


> GZip filter breaks cached forms in chrome: stange binary content at bottom
> --
>
> Key: MAGNOLIA-4413
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4413
> Project: Magnolia
>  Issue Type: Bug
>  Security Level: Public
>  Components: cache, core
>Affects Versions: 4.4.7, 4.5.2
>Reporter: Christian Ringele
>Priority: Critical
> Attachments: StrangeBinaryContent.png
>
>
> Open in chrome (not logged in, needs to be server from the cache) the contact 
> form:
> http://demopublic.magnolia-cms.com/demo-project/service/contact.html
> See the print screen. At the bottom strange binary content is rendered.
> Only in chrome, works in firefox and safari.
> 1. Disable the gzip filter, problem gone.
> 2 or: server the form not form cache by adding ?something to the url, problem 
> gone.
> Seems its the combination that the cahche gzipes, and the gzip filter gzipes 
> somehow also, or at least manipulates the http header wrong.

-- 
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: 

[magnolia-dev] [JIRA] Created: (MGNLFORM-128) Class FormParagraph should be FormComponent

[JIRA (on behalf of Christian Ringele)]

Class FormParagraph should be FormComponent
---

 Key: MGNLFORM-128
 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-128
 Project: Magnolia Form Module
  Issue Type: Improvement
Affects Versions: 1.4.1
Reporter: Christian Ringele
 Fix For: 1.4.2


The class info.magnolia.module.form.templates.components.FormParagraph should 
be renamed to info.magnolia.module.form.templates.components.FormComponent

-- 
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: 

[magnolia-dev] [JIRA] Created: (MGNLSTK-953) Adding on a template definition to promos area a script triggers loosing 'inheritance' configuration form site definition

[JIRA (on behalf of Christian Ringele)]

Adding on a template definition to promos area a script triggers loosing 
'inheritance' configuration form site definition 
--

 Key: MGNLSTK-953
 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-953
 Project: Magnolia Standard Templating Kit
  Issue Type: Bug
  Components: base system
Affects Versions: 2.0.2
Reporter: Christian Ringele
Assignee: Ondřej Chytil
Priority: Critical
 Fix For: 2.0.3
 Attachments: InheritedPromosGone.png

Reproduce (see print screen):
- Go on demo (or any bundle) to the stkSection
- add to the areas the node 'promos'
- point in the promos to any other templateScript (for test you can use the 
original defined in the site def).
-> all inherited promos are gone

Seems as the 'inherited' node is not merged properly from the site definition. 
At least for the promos area.
I suspect a direct method call on the template bean instead on the proxy object.

(When adding an node into the promos area 'inheritance' with enabled:true, it 
works again)

-- 
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: 

[magnolia-dev] [JIRA] Updated: (MGNLPUR-68) ACL of anonymous wrong set -> no deny of the protected page

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLPUR-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLPUR-68:
-

Summary: ACL of anonymous wrong set -> no deny of the protected page  (was: 
ACL of anonymous wrong set -> no deny protected page)

> ACL of anonymous wrong set -> no deny of the protected page
> ---
>
> Key: MGNLPUR-68
> URL: http://jira.magnolia-cms.com/browse/MGNLPUR-68
> Project: Magnolia Public User Registration
>  Issue Type: Bug
>Affects Versions: 1.4.1
>Reporter: Christian Ringele
>Assignee: Ondřej Chytil
>Priority: Critical
> Fix For: 1.4.2
>
>
> The anonymous role has no deny on the protect page on a public:
> http://demopublic.magnolia-cms.com/demo-project/members-area/protected.html
> The login screen does not appear.

-- 
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: 

[magnolia-dev] [JIRA] Created: (MGNLPUR-68) ACL of anonymous wrong set -> no deny protected page

[JIRA (on behalf of Christian Ringele)]

ACL of anonymous wrong set -> no deny protected page


 Key: MGNLPUR-68
 URL: http://jira.magnolia-cms.com/browse/MGNLPUR-68
 Project: Magnolia Public User Registration
  Issue Type: Bug
Affects Versions: 1.4.1
Reporter: Christian Ringele
Assignee: Ondřej Chytil
Priority: Critical
 Fix For: 1.4.2


The anonymous role has no deny on the protect page on a public:
http://demopublic.magnolia-cms.com/demo-project/members-area/protected.html

The login screen does not appear.

-- 
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: 

[magnolia-dev] [JIRA] Created: (MAGNOLIA-4422) securityCallback is not working for custom pattern: PUR pattern not working

[JIRA (on behalf of Christian Ringele)]

securityCallback is not working for custom pattern: PUR pattern not working
---

 Key: MAGNOLIA-4422
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4422
 Project: Magnolia
  Issue Type: Bug
  Security Level: Public
  Components: core
Affects Versions: 4.5.2
Reporter: Christian Ringele
Assignee: Ondřej Chytil
Priority: Critical
 Fix For: 4.5.x


After setting the ACL of the PUR right (MGNLPUR-68), the standard login form 
appears and not the PUR login form:
http://demopublic.magnolia-cms.com/demo-project/members-area/protected.html?something

Seems as the public securityCallback pattern is ignored.

Besides:
Its not viewable&changeable anymore, to what 'location' the default 'form' 
pattern is matched to.
So it can't be changed, and for beginners it can't be known where it will apply 
to.

-- 
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: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-820) Review the configuration of the pages under demo-features/modules/public-user-registration

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-820:
--

Fix Version/s: 2.0.4
   (was: 2.0.x)
 Priority: Critical  (was: Neutral)

> Review the configuration of the pages under 
> demo-features/modules/public-user-registration
> --
>
> Key: MGNLSTK-820
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-820
> Project: Magnolia Standard Templating Kit
>  Issue Type: Bug
>Affects Versions: 1.4
>Reporter: Samuel Schmitt
>Priority: Critical
> Fix For: 2.0.4
>
>
> PUR is not correctly setup in demo-features, checkout the linked issues from 
> PUR.

-- 
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: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-959) protected page in Demo project is not protected due to incorrect setting of ACLs of Anonymous user

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-959:
--

Fix Version/s: 2.0.4
   (was: 2.0.x)

> protected page in Demo project is not protected due to incorrect setting of 
> ACLs of Anonymous user
> --
>
> Key: MGNLSTK-959
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-959
> Project: Magnolia Standard Templating Kit
>  Issue Type: Bug
>  Components: demoproject
>Affects Versions: 2.0.1
>Reporter: Christian Ringele
>Priority: Major
> Fix For: 2.0.4
>
>
> The anonymous role has no deny on the protect page on a public:
> http://demopublic.magnolia-cms.com/demo-project/members-area/protected.html
> The login screen does not appear.

-- 
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: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-959) protected page in Demo project is not protected due to incorrect setting of ACLs of Anonymous user

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-959:
--

Priority: Critical  (was: Major)

> protected page in Demo project is not protected due to incorrect setting of 
> ACLs of Anonymous user
> --
>
> Key: MGNLSTK-959
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-959
> Project: Magnolia Standard Templating Kit
>  Issue Type: Bug
>  Components: demoproject
>Affects Versions: 2.0.1
>Reporter: Christian Ringele
>Priority: Critical
> Fix For: 2.0.4
>
>
> The anonymous role has no deny on the protect page on a public:
> http://demopublic.magnolia-cms.com/demo-project/members-area/protected.html
> The login screen does not appear.

-- 
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: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-854) STK: event and news overview section headers should provide complete dialog with images

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-854:
--

Fix Version/s: 2.0.4
   (was: 2.0.x)
 Priority: Major  (was: Neutral)

> STK: event and news overview section headers should provide complete dialog 
> with images
> ---
>
> Key: MGNLSTK-854
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-854
> Project: Magnolia Standard Templating Kit
>  Issue Type: Task
>Affects Versions: 2.0.1
>Reporter: Natascha Desmarais
>Priority: Major
> Fix For: 2.0.4
>
>
> Dialog:
> In the STK prototype the event and news section headers display images. While 
> the demo-project also contains those images in the section header, the dialog 
> only provides the possibility to enter a title and abstract. This should be 
> fixed for 4.5 as per Boris' request.
> Might be worth fixing this for the 1.4 branch of STK as well if we release a 
> 1.4.7 version.
> http://localhost:8080/magnoliaAuthor/demo-features/special-templates/glossary.html
> No image editable in Header (this issue is discussed with Natascha, it used 
> to be possible to ad an image for the header)
> ---
> http://localhost:8080/magnoliaAuthor/demo-features.html
> Cannot edit or delete stage teaser at all
> You can get it working if you add an height on the #stage element. Seems 
> there is some problems with positioning (relative/absolute). The content is 
> not displayed (preview and edit-mode)
> ---
> http://localhost:8080/magnoliaAuthor/demo-features/special-templates/image-gallery.html
> cannot do anything with images
> The images are just not displayed here.
> ---
> http://localhost:8080/magnoliaAuthor/demo-features/content-templates/glossary-term.html
> Glossary term is a content category page template but the header don't allow 
> me to edit the typical content item header info e.g. the image.

-- 
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: 

[magnolia-dev] [JIRA] Created: (MGNLSTK-965) STK must be in sync with static prototype changes for every minor release

[JIRA (on behalf of Christian Ringele)]

STK must be in sync with static prototype changes for every minor release
-

 Key: MGNLSTK-965
 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-965
 Project: Magnolia Standard Templating Kit
  Issue Type: Bug
  Components: concept, paragraphs, templates
Affects Versions: 2.0.3, 2.0.2
Reporter: Christian Ringele
Priority: Blocker
 Fix For: 2.0.4


In between every minor release there could be changes within the html static 
prototype.
The static prototype get released together with the STK. There for the STK must 
always be aligned/in sync with the static prototype.
This is a repeating task for every minor&major version.

I'll link a issue, which just postponed to a later version. This should never 
happen:
STK 2.0.3 is not in sync with prototype 2.0.3

The process to do:
- See if there were any check ins into the prototype
- If so a divv whill show it that were css or html changes
-- css changes -> can just be copy & pasted into the theme module
-- html changes -> accordinf ftl must be found and change implemented


Be careful, right now all changes till prototype 2.0.1 must be taking in 
account.

-- 
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: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-946) Update STK & Theme Pop with latest changes from prototype

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-946:
--

Priority: Critical  (was: Major)

> Update STK & Theme Pop with latest changes from prototype
> -
>
> Key: MGNLSTK-946
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-946
> Project: Magnolia Standard Templating Kit
>  Issue Type: Sub-task
>Affects Versions: 2.0.2
>Reporter: Natascha Desmarais
>Assignee: Eric Hechinger
>Priority: Critical
> Fix For: 2.0.4
>
>
> r56830 from the 25th of April brought some changes to styles.css and possibly 
> FTLs - to be checked and brought in sync.

-- 
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: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-836) Resource not found issue

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-836:
--

 Assignee: (was: Natascha Desmarais)
Fix Version/s: 2.0.4
   (was: 2.0.x)
 Priority: Major  (was: Neutral)

This should be finally resolved and not postpones to the future again and again.

> Resource not found issue
> 
>
> Key: MGNLSTK-836
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-836
> Project: Magnolia Standard Templating Kit
>  Issue Type: Bug
>  Components: themepop
>Affects Versions: 2.0
>Reporter: Federico Grilli
>Priority: Major
> Fix For: 2.0.4
>
>
> When rendering some pages one notices several of
> {code}WARN  info.magnolia.rendering.engine.RenderingFilter: Resource not 
> found: [/templating-kit/themes/pop/img/temp] {code}
> due to the fact that {{style.css}} is referring to the non existing 
> {{img/temp}} path for a couple of background images in the {{#wow}} and the 
> {{div.superpromos}} selectors. For the time being I'll just comment them out. 
> Natascha will then contact Aperto about this.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira





For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-965) STK must be in sync with static prototype changes for every minor and major release

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-965:
--

Summary: STK must be in sync with static prototype changes for every minor 
and major release  (was: STK must be in sync with static prototype changes for 
every minor release)

> STK must be in sync with static prototype changes for every minor and major 
> release
> ---
>
> Key: MGNLSTK-965
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-965
> Project: Magnolia Standard Templating Kit
>  Issue Type: Bug
>  Components: concept, paragraphs, templates
>Affects Versions: 2.0.2, 2.0.3
>Reporter: Christian Ringele
>Priority: Blocker
> Fix For: 2.0.4
>
>
> In between every minor release there could be changes within the html static 
> prototype.
> The static prototype get released together with the STK. There for the STK 
> must always be aligned/in sync with the static prototype.
> This is a repeating task for every minor&major version.
> I'll link a issue, which just postponed to a later version. This should never 
> happen:
> STK 2.0.3 is not in sync with prototype 2.0.3
> The process to do:
> - See if there were any check ins into the prototype
> - If so a divv whill show it that were css or html changes
> -- css changes -> can just be copy & pasted into the theme module
> -- html changes -> accordinf ftl must be found and change implemented
> Be careful, right now all changes till prototype 2.0.1 must be taking in 
> account.

-- 
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: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-953) Adding on a template definition to promos area a script triggers loosing 'inheritance' configuration form site definition

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-953:
--

Priority: Critical  (was: Major)

> Adding on a template definition to promos area a script triggers loosing 
> 'inheritance' configuration form site definition 
> --
>
> Key: MGNLSTK-953
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-953
> Project: Magnolia Standard Templating Kit
>  Issue Type: Bug
>  Components: base system
>Affects Versions: 2.0.2
>Reporter: Christian Ringele
>Assignee: Ondřej Chytil
>Priority: Critical
> Fix For: 2.0.4
>
> Attachments: InheritedPromosGone.png
>
>
> Reproduce (see print screen):
> - Go on demo (or any bundle) to the stkSection
> - add to the areas the node 'promos'
> - point in the promos to any other templateScript (for test you can use the 
> original defined in the site def).
> -> all inherited promos are gone
> Seems as the 'inherited' node is not merged properly from the site 
> definition. At least for the promos area.
> I suspect a direct method call on the template bean instead on the proxy 
> object.
> (When adding an node into the promos area 'inheritance' with enabled:true, it 
> works again)

-- 
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: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-949) Navigation: Start levels should be definable. Also the SiteNavigationModel used should be injected by IOC and not with 'new'

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-949:
--

Priority: Critical  (was: Major)

At least the IOC part should be changed, thats one line of code using 
components instead of new allocation.

> Navigation: Start levels should be definable. Also the SiteNavigationModel 
> used should be injected by IOC and not with 'new'
> 
>
> Key: MGNLSTK-949
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-949
> Project: Magnolia Standard Templating Kit
>  Issue Type: Improvement
>  Components: concept, templates
>Affects Versions: 2.0.2
>Reporter: Christian Ringele
>Assignee: Eric Hechinger
>Priority: Critical
> Fix For: 2.0.4
>
>
> In training, I get often confronted with a need of STK regarding the 
> Navigation.
> On many pages out there, the vertical navigation displays the same pages as 
> the horizontal navigation.
> For example when the horizontal provides a dropdown based Navigation, that 
> the displayed drop down level is the same as the starting level of the 
> vertical navigation.
> The implementation within STK is, that you cant define a starting level of 
> the vertical navigation. It will always start one level below what the 
> horizontal navigation displays. (line 89 of SiteNavigationModel)
> I think the start level of the vertical navigation should be definable.
> When trying to solve this problem within the code just for a project, I 
> encountered the problem that I cannot inject a different SiteNavigationModel 
> without using for EVERY stk page template a different STKPageMOdel class, 
> because the STKPAgeModel does a 'new' allocation of the SiteNavigationModel 
> instead of getting it by Components.
> Line 88 in STKPageModel
> {code}
> public SiteNavigationModel getNavigation() {
> return new SiteNavigationModel(getDefinition().getNavigation(), 
> getSiteRoot(), content);
> }
> {code}

-- 
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: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-957) Internal link component throws freemarker exception if target is not available

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-957:
--

Priority: Major  (was: Neutral)

This is a very common case, so it should have higher prio.

> Internal link component throws freemarker exception if target is not available
> --
>
> Key: MGNLSTK-957
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-957
> Project: Magnolia Standard Templating Kit
>  Issue Type: Bug
>  Components: demoproject
>Affects Versions: 2.0.2
>Reporter: Frank Sommer
>Priority: Major
> Fix For: 2.0.4
>
>
> Tested on demoauthor instance. Try to reference a not existing page in a 
> internal link component and a freemarker stack trace will occure.
> {{stkFunctions.getReferencedContent(content, "link", 
> RepositoryConstants.WEBSITE)}} throws an uncatched runtime exception.

-- 
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: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-880) STK prototype: All %template%Header dialog should be renamed to %template%Intro dialogs. Change SectionBanner dialog back to sectionHeader.

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-880:
--

Assignee: Christian Ringele

> STK prototype: All %template%Header dialog should be renamed to 
> %template%Intro dialogs. Change SectionBanner dialog back to sectionHeader. 
> 
>
> Key: MGNLSTK-880
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-880
> Project: Magnolia Standard Templating Kit
>  Issue Type: Sub-task
>Affects Versions: 2.0.1
>Reporter: Christian Ringele
>Assignee: Christian Ringele
> Fix For: 2.0.4
>
>


-- 
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: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-880) STK prototype: All %template%Header dialog should be renamed to %template%Intro dialogs. Change SectionBanner dialog back to sectionHeader.

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-880:
--

Affects Version/s: 2.0
   (was: 2.0.1)

> STK prototype: All %template%Header dialog should be renamed to 
> %template%Intro dialogs. Change SectionBanner dialog back to sectionHeader. 
> 
>
> Key: MGNLSTK-880
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-880
> Project: Magnolia Standard Templating Kit
>  Issue Type: Sub-task
>Affects Versions: 2.0
>Reporter: Christian Ringele
>Assignee: Christian Ringele
> Fix For: 2.0.4
>
>


-- 
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: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-880) STK prototype: All %template%Header dialog should be renamed to %template%Intro dialogs. Change sectionBanner dialog back to sectionHeader.

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-880:
--

Summary: STK prototype: All %template%Header dialog should be renamed to 
%template%Intro dialogs. Change sectionBanner dialog back to sectionHeader.   
(was: STK prototype: All %template%Header dialog should be renamed to 
%template%Intro dialogs. Change SectionBanner dialog back to sectionHeader. )

> STK prototype: All %template%Header dialog should be renamed to 
> %template%Intro dialogs. Change sectionBanner dialog back to sectionHeader. 
> 
>
> Key: MGNLSTK-880
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-880
> Project: Magnolia Standard Templating Kit
>  Issue Type: Sub-task
>Affects Versions: 2.0
>Reporter: Christian Ringele
>Assignee: Christian Ringele
> Fix For: 2.0.4
>
>


-- 
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: 

[magnolia-dev] [JIRA] Created: (MGNLSTK-972) ThemeInstallTask should not depend on an existing theme configuration

[JIRA (on behalf of Christian Ringele)]

ThemeInstallTask should not depend on an existing theme configuration
-

 Key: MGNLSTK-972
 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-972
 Project: Magnolia Standard Templating Kit
  Issue Type: Bug
  Components: themepop
Affects Versions: 2.0.3, 2.0.2, 2.0.1, 2.0, 1.4.7
Reporter: Christian Ringele
Priority: Major
 Fix For: 2.0.x


The ThemeInstallTask expects an existing Theme configuration within the 
module's bootstrap files.
{code}
 new BootstrapSingleResource("", "", "/mgnl-bootstrap/theme-" + themeName + 
"/config.modules.standard-templating-kit.config.themes." + themeName + ".xml", 
ImportUUIDBehavior.IMPORT_UUID_COLLISION_REPLACE_EXISTING).execute(ctx);
{code}
When creating a new theme, there can't exist a theme configuration yet.
This is one of the most often stumbles for people when creating a custom theme.

The ThemeInstallTask should use a custom task, which first checks if the 
resource exists within the jar/module.

-- 
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: 

[magnolia-dev] [JIRA] Created: (MGNLSTK-973) ThemeInstallTask will never update a mobile theme configuration, missing boostratp task

[JIRA (on behalf of Christian Ringele)]

ThemeInstallTask will never update a mobile theme configuration, missing 
boostratp task
---

 Key: MGNLSTK-973
 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-973
 Project: Magnolia Standard Templating Kit
  Issue Type: Bug
  Components: themepop
Affects Versions: 2.0.3, 2.0.2, 2.0.1, 2.0
Reporter: Christian Ringele
Priority: Critical
 Fix For: 2.0.x


The concept of the ThemeVersionHandler is to reinstall the whole theme on any 
update of the module.

But the ThemeInstallTask just bootstraps the base theme configuration, but not 
a mobile theme.
This didn't show up, because on module installation both configurations are 
bootstrapped by the BaseInstallTasks of the DefaultModuleVersionHandler 
(basicInstallTasks.add(new ModuleBootstrapTask());).

But on update, only the 'base' theme (the one defined in the themes module 
descriptor) is re-bootstrapped:
{code}
new BootstrapSingleResource("", "", "/mgnl-bootstrap/theme-" + themeName + 
"/config.modules.standard-templating-kit.config.themes." + themeName + ".xml", 
ImportUUIDBehavior.IMPORT_UUID_COLLISION_REPLACE_EXISTING).execute(ctx);
{code}

Solution:
I think most proper solution would be defining two properties within the module 
descriptor, one for the base theme, and one for the mobile theme.
{code}
  

themeName
pop


mobileThemeName
pop-mobile

  
{code}
Using an custom task which checks if the property 'mobileThemeName' is defined, 
and if so bootstraps it.
(For the case you're not using a mobile theme)

-- 
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: 

[magnolia-dev] [JIRA] Created: (MGNLSTK-988) STKPager calculates wrong -> newsOverview component displays wrong amount of itmes.

[JIRA (on behalf of Christian Ringele)]

STKPager calculates wrong -> newsOverview component displays wrong amount of 
itmes.
---

 Key: MGNLSTK-988
 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-988
 Project: Magnolia Standard Templating Kit
  Issue Type: Bug
  Components: paragraphs
Affects Versions: 2.0.4
Reporter: Christian Ringele
Assignee: Ondřej Chytil
Priority: Major
 Fix For: 2.0.5
 Attachments: Screen Shot 2012-08-09 at 11.49.57 AM.png, Screen Shot 
2012-08-09 at 11.50.21 AM.png, Screen Shot 2012-08-09 at 11.50.38 AM.png

The STKPages does not calculate the offset right.

Reproduce:
- Add in /demo-project/news-and-events/news-overview three more news pages by 
copy the existing.
- Configure the news overview components on the 
/demo-project/news-and-events/news-overview with max results 5.

-> fist pager should display 5 elements, the second one.
Result is, that the first displays two, and the second one.

I think the problem is within the offset calculation in:
info.magnolia.module.templatingkit.util.STKPager.getOffset()
But don't have time to dig into.

Any Components extending the 
info.magnolia.module.templatingkit.paragraphs.AbstractItemListModel will have 
this problem:
stkNewsOverview, stkEventsOverview

-- 
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: 

[magnolia-dev] [JIRA] Created: (MGNLPUR-70) Protected Page does not redirect to PUR login form

[JIRA (on behalf of Christian Ringele)]

Protected Page does not redirect to PUR login form
--

 Key: MGNLPUR-70
 URL: http://jira.magnolia-cms.com/browse/MGNLPUR-70
 Project: Magnolia Public User Registration
  Issue Type: Bug
Affects Versions: 1.4.1
Reporter: Christian Ringele
Assignee: Ondřej Chytil
Priority: Major
 Fix For: 1.4.x


Either its the configuration of the securityClientCall back that the PUR nodule 
adds, or its the redirecting filter itself.

When accessing the page:
http://demopublic.magnolia-cms.com/demo-project/members-area/protected.html
it should redirect to the PUR's login page, which it doesn't.

-- 
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: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-335) Paragraph to display list of documents from DMS

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-335:
--

Fix Version/s: 2.0
Affects Version/s: 2.0
   1.4.7

> Paragraph to display list of documents from DMS
> ---
>
> Key: MGNLSTK-335
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-335
> Project: Magnolia Standard Templating Kit
>  Issue Type: New Feature
>  Components: paragraphs
>Affects Versions: 1.4.7, 2.0
>Reporter: Christian Ringele
>Assignee: Christian Ringele
>Priority: Major
> Fix For: 2.0
>
>
> A paragraph is needed, which generates automatically a linkList containing 
> all files in a DMS folder. It should be possible to restrict the resultset 
> based on file extension (for instance, only show pdf's). Such a paragraph was 
> available in SiteDesigner.
> In a later step, instead of selecting a folder from DMS, we should also allow 
> to search for categories (this would require an integration of DMS with the 
> categories module such that we can use the same categories in the WCM and the 
> DMS).

-- 
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: 

[magnolia-dev] [JIRA] Updated: (MGNLGA-5) Default configuration only works with ETK out of the box

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLGA-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLGA-5:
---

Fix Version/s: 1.1

> Default configuration only works with ETK out of the box
> 
>
> Key: MGNLGA-5
> URL: http://jira.magnolia-cms.com/browse/MGNLGA-5
> Project: Magnolia Google Analytics
>  Issue Type: Bug
>Affects Versions: 1.0
>Reporter: Christian Ringele
>Assignee: Christian Ringele
> Fix For: 1.1
>
>
> In CE environment, the standard served sieDefinition is 'site'.
> There for the 'default' GA config is not matching and never used.
> Work around:
> Rename the 'default' GA-config to 'site'

-- 
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: 

[magnolia-dev] [JIRA] Created: (MAGNOLIA-4591) GZip filter adds strange binary characters to any form of form module, only showing in Chrome.

[JIRA (on behalf of Christian Ringele)]

GZip filter adds strange binary characters to any form of form module, only 
showing in Chrome.
--

 Key: MAGNOLIA-4591
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4591
 Project: Magnolia
  Issue Type: Bug
  Security Level: Public
  Components: cache, core
Affects Versions: 4.5.6, 4.5.5, 4.5.4, 4.5.3, 4.5.2, 4.5.1, 4.5, 4.4.9, 
4.4.8, 4.4.7, 4.4.6, 4.4.5, 4.4.4, 4.4.3
Reporter: Christian Ringele
Assignee: Jan Haderka
Priority: Critical
 Fix For: 4.5.7
 Attachments: BinaryCharacters_Localhost.png

Any form page of the form module produces strange binary characters to the 
rendered output.
This can't be Apache, because it also appears on localhost running without 
Apache in front.
Turn of gzip filter, characters gone.

Reproduce:
- Download newest Magnolia version
- Deploy locally
- Open contact form in chrome
- Scroll down

Toggle with the GZip filter.



-- 
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: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-785) footerAbout template script can't render images without title

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-785:
--

Fix Version/s: 1.3.6
   (was: 1.3.x)
   (was: 1.4.5)

> footerAbout template script can't render images without title
> -
>
> Key: MGNLSTK-785
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-785
> Project: Magnolia Standard Templating Kit
>  Issue Type: Bug
>  Components: paragraphs
>Affects Versions: 1.3.5, 1.4.4
>Reporter: Grégory Joseph
>Assignee: Christian Ringele
> Fix For: 1.3.6
>
>
> In {{/templating-kit/paragraphs/footer/footerAbout.ftl}}, the following can't 
> work for assets that don't have a title:
> {code}
> [#assign imageAlt = image.title!image.@name]
> {code}
> {{image}} in this case is an instance of 
> {{info.magnolia.module.templatingkit.dam.Asset}}; a dms asset "always" has a 
> title (since the title property is automatically filled in on creation in the 
> tree), while an uploaded asset never does. The expression above thus falls 
> back to {{@name}}, which can't be interpreted either, as there is no such 
> property ({{image}} is an {{Asset}}, not a node).
> Trivial fix:
> {code}
> [#assign imageAlt = image.title!image.name]
> {code}

-- 
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: 

[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3359) NodeBuilderAPI - Ops: Method renameProperty() from Ops class does not set the right value

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MAGNOLIA-3359:


Fix Version/s: 4.3.9
   (was: 4.3.x)
   (was: 4.4)

> NodeBuilderAPI - Ops: Method renameProperty() from Ops class does not set the 
> right value
> -
>
> Key: MAGNOLIA-3359
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3359
> Project: Magnolia
>  Issue Type: Bug
>  Security Level: Public
>  Components: core
>Affects Versions: 4.3.8
>Reporter: Christian Ringele
>Assignee: Christian Ringele
>Priority: Major
> Fix For: 4.3.9
>
> Attachments: magnolia-core.patch, Screen shot 2010-11-03 at 4.15.43 
> PM.png
>
>
> The value of the renamed node is not the value of the old node, but the path 
> to the passed NodeData object (see print screen).
> I've written test cases and a solution in the Ops class and attached it as a 
> patch.

-- 
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: 

[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3375) VirtualURIFilter: permanent redirect adds always the port to the url -> port 80 is displayed on safari

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MAGNOLIA-3375:


Fix Version/s: 4.3.9
   (was: 4.3.x)
   (was: 4.4)

> VirtualURIFilter: permanent redirect adds always the port to the url -> port 
> 80 is displayed on safari
> --
>
> Key: MAGNOLIA-3375
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3375
> Project: Magnolia
>  Issue Type: Bug
>  Security Level: Public
>  Components: core
>Affects Versions: 4.3.8, 4.4.x, 5.0
>Reporter: Christian Ringele
>Assignee: Christian Ringele
>Priority: Major
> Fix For: 4.3.9
>
> Attachments: magnolia-core.patch, Screen shot 2010-11-09 at 10.22.24 
> AM.png, Screen shot 2010-11-09 at 10.22.31 AM.png, Screen shot 2010-11-09 at 
> 10.22.38 AM.png
>
>
> The permanent redirect adds always the port to the response if its port 80 
> (standard http port), firefox and IE hides the port in the URL.
> On Safari it shows up -> port 80 appears after a permanent redirect 
> (printscreen '/home/' is removed by perms-redirect).

-- 
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: 

[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3366) CreateNodePathTask: ItemType should be defineable

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MAGNOLIA-3366:


Fix Version/s: 4.3.9
   (was: 4.3.x)
   (was: 4.4)

> CreateNodePathTask: ItemType should be defineable 
> --
>
> Key: MAGNOLIA-3366
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3366
> Project: Magnolia
>  Issue Type: Improvement
>  Security Level: Public
>  Components: updatemechanism
>Affects Versions: 4.3.8, 4.4.x, 5.0
>Reporter: Christian Ringele
>Assignee: Christian Ringele
>Priority: Minor
> Fix For: 4.3.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: 

[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4087) STK: Update all JS and their structure aligned to prototype - missing parts

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MAGNOLIA-4087:


Fix Version/s: 4.5.7
   (was: 4.5.x)

> STK: Update all JS and their structure aligned to prototype - missing parts
> ---
>
> Key: MAGNOLIA-4087
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4087
> Project: Magnolia
>  Issue Type: Task
>  Security Level: Public
>Affects Versions: 4.5
>Reporter: Natascha Desmarais
>Assignee: Christian Ringele
> Fix For: 4.5.7
>
>
> The javascripts need to be checked for content updates (considering 
> timestamps from our last update to the prototype on the scriptloaders for 
> example - especially check for mobile as well, I recall some last minute 
> tweaks to those plugins and libs)

-- 
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: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-1014) TemplatesAvailability reacts on node name and not on hte defined id

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-1014:
---

Attachment: TemplateAvailability-WrongID-Config.png
TemplateAvailability-WrongID-StillAvailable.png
TemplateAvailability-WrongNodeName-NotAvailable.png

> TemplatesAvailability reacts on node name and not on hte defined id
> ---
>
> Key: MGNLSTK-1014
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1014
> Project: Magnolia Standard Templating Kit
>  Issue Type: Bug
>  Components: base system
>Affects Versions: 2.0.7
>Reporter: Christian Ringele
>Assignee: Ondřej Chytil
> Fix For: 2.0.x
>
> Attachments: TemplateAvailability-WrongID-Config.png, 
> TemplateAvailability-WrongID-StillAvailable.png, 
> TemplateAvailability-WrongNodeName-NotAvailable.png, 
> TemplateAvailability-WrongNodeName.png
>
>
> The a site-defintion/templates/prototype a available page templates can be 
> defined.
> Its a list of page templates defined with an id, same pattern as dialogs or 
> availableComponents id's.
> The ID is ignored, but the node name of the configuration is taken into 
> account.
> It should use the id instead.

-- 
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: 

[magnolia-dev] [JIRA] Updated: (MGNLSTK-1014) TemplatesAvailability reacts on node name and not on hte defined id

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLSTK-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLSTK-1014:
---

Attachment: TemplateAvailability-WrongNodeName.png

> TemplatesAvailability reacts on node name and not on hte defined id
> ---
>
> Key: MGNLSTK-1014
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1014
> Project: Magnolia Standard Templating Kit
>  Issue Type: Bug
>  Components: base system
>Affects Versions: 2.0.7
>Reporter: Christian Ringele
>Assignee: Ondřej Chytil
> Fix For: 2.0.x
>
> Attachments: TemplateAvailability-WrongID-Config.png, 
> TemplateAvailability-WrongID-StillAvailable.png, 
> TemplateAvailability-WrongNodeName-NotAvailable.png, 
> TemplateAvailability-WrongNodeName.png
>
>
> The a site-defintion/templates/prototype a available page templates can be 
> defined.
> Its a list of page templates defined with an id, same pattern as dialogs or 
> availableComponents id's.
> The ID is ignored, but the node name of the configuration is taken into 
> account.
> It should use the id instead.

-- 
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: 

[magnolia-dev] [JIRA] Created: (MGNLSTK-1014) TemplatesAvailability reacts on node name and not on hte defined id

[JIRA (on behalf of Christian Ringele)]

TemplatesAvailability reacts on node name and not on hte defined id
---

 Key: MGNLSTK-1014
 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1014
 Project: Magnolia Standard Templating Kit
  Issue Type: Bug
  Components: base system
Affects Versions: 2.0.7
Reporter: Christian Ringele
Assignee: Ondřej Chytil
 Fix For: 2.0.x
 Attachments: TemplateAvailability-WrongID-Config.png, 
TemplateAvailability-WrongID-StillAvailable.png, 
TemplateAvailability-WrongNodeName-NotAvailable.png, 
TemplateAvailability-WrongNodeName.png

The a site-defintion/templates/prototype a available page templates can be 
defined.
Its a list of page templates defined with an id, same pattern as dialogs or 
availableComponents id's.

The ID is ignored, but the node name of the configuration is taken into account.
It should use the id instead.



-- 
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: 

[magnolia-dev] [JIRA] Created: (MGNLIMG-100) Loading image from JCR using AbstractLoader will result in adding the alpha value as a color to generated JPGs

[JIRA (on behalf of Christian Ringele)]

Loading image from JCR using AbstractLoader will result in adding the alpha 
value as a color to generated JPGs
--

 Key: MGNLIMG-100
 URL: http://jira.magnolia-cms.com/browse/MGNLIMG-100
 Project: Magnolia Imaging Module
  Issue Type: Bug
  Components: image operations
Affects Versions: 2.2.1
Reporter: Christian Ringele
Assignee: Grégory Joseph
Priority: Critical
 Fix For: 2.x
 Attachments: AbstractLoader.java.patch, Generator.png, 
OrigImage-PlacedIntoDMS.jpg, out1-works.png, out1-worksNot.jpg

Description:
Calling an image generator which uses a FromContent (extends AbstractLoader) 
operation will result in wrong JPGs.
If storing PNGs it works fine. As PNGs have a alpha channel, the alpha value is 
correctly applied.
Storing a JPG, it seems as the ImageIO.write() method writes the alpha value as 
a color and not ignoring it as it should.

Reproduce:
1. Import the generator attached to this issue. Just containing one operation, 
the load operation.
2. Add a test image to DMS.
3. execute this code with correct paths:
{code}
final ImagingModuleConfig config = (ImagingModuleConfig) 
ModuleRegistry.Factory.getInstance().getModuleInstance("imaging");
final ImageGenerator generator = 
config.getGenerators().get("myOperationChainBResize");

Session dmsSession = MgnlContext.getJCRSession("dms");
Node origImage = dmsSession.getNode("/test/orig");

final Content content = info.magnolia.cms.util.ContentUtil.asContent(origImage);

final ParameterProvider parameterProvider = new 
ContentParameterProvider(new SimpleEqualityContentWrapper(content));
final BufferedImage bufferedImage = generator.generate(parameterProvider);

ImageIO.write(bufferedImage, "png", new 
File("/Users/cringele/Documents/temp_stuff/image-test/create/out1-works.png"));
ImageIO.write(bufferedImage, "jpg", new 
File("/Users/cringele/Documents/temp_stuff/image-test/create/out1-worksNot.jpg"));
{code}
You can also write the stream back into JCR, the result is the same. So for 
testing much easier into a file.

Source of the problem:
info.magnolia.imaging.operations.load.AbstractLoader.apply(BufferedImage, P)
{code}
if (source != null) {
throw new ImagingException("This operation currently does not support 
overlaying images");
}
final BufferedImage loaded = loadSource(filterParams);
if (loaded == null) {
throw new ImagingException("Could not load image for " + filterParams);
}

//This line is the source of the problem. Using BufferedImage.TYPE_INT_RGB 
would work because it wouldn't contain any alpha channel. Of course just for 
testing applicable.
final BufferedImage img = new BufferedImage(loaded.getWidth(), 
loaded.getHeight(), BufferedImage.TYPE_INT_ARGB_PRE);
final Graphics2D g = img.createGraphics();

if (backgroundColor != null) {
g.setColor(backgroundColor);
g.fill(new Rectangle(0, 0, img.getWidth(), img.getHeight()));
}
g.drawImage(loaded, null, 0, 0);
// TODO would this make any difference ? g.drawRenderedImage(loaded, null);

g.dispose();
return img;
{code}

Proof of the problem source:
First possibility: Execute this code just passing back the loaded BufferedImage
{code}
if (source != null) {
throw new ImagingException("This operation currently does not support 
overlaying images");
}
final BufferedImage loaded = loadSource(filterParams);
if (loaded == null) {
throw new ImagingException("Could not load image for " + filterParams);
}
return loaded;
{code}

Second possibility: Pass back the created BufferedImage (img) withour loagin 
the orig image on top.
Like this you can compare alpha value in PNG to color in JPG.
{code}
if (source != null) {
throw new ImagingException("This operation currently does not support 
overlaying images");
}
final BufferedImage loaded = loadSource(filterParams);
if (loaded == null) {
throw new ImagingException("Could not load image for " + filterParams);
}
final BufferedImage img = new BufferedImage(loaded.getWidth(), 
loaded.getHeight(), BufferedImage.TYPE_INT_ARGB_PRE);
final Graphics2D g = img.createGraphics();

if (backgroundColor != null) {
g.setColor(backgroundColor);
g.fill(new Rectangle(0, 0, img.getWidth(), img.getHeight()));
}
//Image not loaded on top of it
//g.drawImage(loaded, null, 0, 0);
// TODO would this make any difference ? g.drawRenderedImage(loaded, null);

g.dispose();
return img;
{code}

It seems to be a known problem:
http://stackoverflow.com/questions/8410996/java-bufferedimage-saves-with-unwanted-background-color
Trying out the solution they suggest did not work.

Was not able to supply a patch with a final solution. Added a pacth as a 
workaround.

-- 
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/Administrat

[magnolia-dev] [JIRA] Updated: (MGNLIMG-100) Loading image from JCR using AbstractLoader will result in adding the alpha value as a color to generated JPGs

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLIMG-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLIMG-100:
--

Attachment: out1-works.png
out1-worksNot.jpg

Look at the non working image with Gimp or Photoshop.

> Loading image from JCR using AbstractLoader will result in adding the alpha 
> value as a color to generated JPGs
> --
>
> Key: MGNLIMG-100
> URL: http://jira.magnolia-cms.com/browse/MGNLIMG-100
> Project: Magnolia Imaging Module
>  Issue Type: Bug
>  Components: image operations
>Affects Versions: 2.2.1
>Reporter: Christian Ringele
>Assignee: Grégory Joseph
>Priority: Critical
> Fix For: 2.x
>
> Attachments: AbstractLoader.java.patch, Generator.png, 
> OrigImage-PlacedIntoDMS.jpg, out1-works.png, out1-worksNot.jpg
>
>
> Description:
> Calling an image generator which uses a FromContent (extends AbstractLoader) 
> operation will result in wrong JPGs.
> If storing PNGs it works fine. As PNGs have a alpha channel, the alpha value 
> is correctly applied.
> Storing a JPG, it seems as the ImageIO.write() method writes the alpha value 
> as a color and not ignoring it as it should.
> Reproduce:
> 1. Import the generator attached to this issue. Just containing one 
> operation, the load operation.
> 2. Add a test image to DMS.
> 3. execute this code with correct paths:
> {code}
> final ImagingModuleConfig config = (ImagingModuleConfig) 
> ModuleRegistry.Factory.getInstance().getModuleInstance("imaging");
> final ImageGenerator generator = 
> config.getGenerators().get("myOperationChainBResize");
> Session dmsSession = MgnlContext.getJCRSession("dms");
> Node origImage = dmsSession.getNode("/test/orig");
> final Content content = 
> info.magnolia.cms.util.ContentUtil.asContent(origImage);
> final ParameterProvider parameterProvider = new 
> ContentParameterProvider(new SimpleEqualityContentWrapper(content));
> final BufferedImage bufferedImage = generator.generate(parameterProvider);
> ImageIO.write(bufferedImage, "png", new 
> File("/Users/cringele/Documents/temp_stuff/image-test/create/out1-works.png"));
> ImageIO.write(bufferedImage, "jpg", new 
> File("/Users/cringele/Documents/temp_stuff/image-test/create/out1-worksNot.jpg"));
> {code}
> You can also write the stream back into JCR, the result is the same. So for 
> testing much easier into a file.
> Source of the problem:
> info.magnolia.imaging.operations.load.AbstractLoader.apply(BufferedImage, P)
> {code}
> if (source != null) {
> throw new ImagingException("This operation currently does not support 
> overlaying images");
> }
> final BufferedImage loaded = loadSource(filterParams);
> if (loaded == null) {
> throw new ImagingException("Could not load image for " + filterParams);
> }
> //This line is the source of the problem. Using BufferedImage.TYPE_INT_RGB 
> would work because it wouldn't contain any alpha channel. Of course just for 
> testing applicable.
> final BufferedImage img = new BufferedImage(loaded.getWidth(), 
> loaded.getHeight(), BufferedImage.TYPE_INT_ARGB_PRE);
> final Graphics2D g = img.createGraphics();
> if (backgroundColor != null) {
> g.setColor(backgroundColor);
> g.fill(new Rectangle(0, 0, img.getWidth(), img.getHeight()));
> }
> g.drawImage(loaded, null, 0, 0);
> // TODO would this make any difference ? g.drawRenderedImage(loaded, null);
> g.dispose();
> return img;
> {code}
> Proof of the problem source:
> First possibility: Execute this code just passing back the loaded 
> BufferedImage
> {code}
> if (source != null) {
> throw new ImagingException("This operation currently does not support 
> overlaying images");
> }
> final BufferedImage loaded = loadSource(filterParams);
> if (loaded == null) {
> throw new ImagingException("Could not load image for " + filterParams);
> }
> return loaded;
> {code}
> Second possibility: Pass back the created BufferedImage (img) withour loagin 
> the orig image on top.
> Like this you can compare alpha value in PNG to color in JPG.
> {code}
> if (source != null) {
> throw new ImagingException("This operation currently does not support 
> overlaying images");
> }
> final BufferedImage loaded = loadSource(filterParams);
> if (loaded == null) {
> throw new ImagingException("Could not load image for " + filterParams);
> }
> final BufferedImage img = new BufferedImage(loaded.getWidth(), 
> loaded.getHeight(), BufferedImage.TYPE_INT_ARGB_PRE);
> final Graphics2D g = img.createGraphics();
> if (backgroundColor != null) {
> g.setColor(backgroundColor);
> g.fill(new Rectangle(0, 0, img.getWidth(), img.getHeight()));
> }
> //Image not loaded on top of it
> //g.drawImage(loaded, null, 0, 0);
> // TODO would this make any

[magnolia-dev] [JIRA] Updated: (MGNLIMG-100) Loading image from JCR using AbstractLoader will result in adding the alpha value as a color to generated JPGs

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MGNLIMG-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MGNLIMG-100:
--

Attachment: Output-using-BufferedImage.TYPE_INT_RGB.jpg

using BufferedImage.TYPE_INT_RGB to create the image.

> Loading image from JCR using AbstractLoader will result in adding the alpha 
> value as a color to generated JPGs
> --
>
> Key: MGNLIMG-100
> URL: http://jira.magnolia-cms.com/browse/MGNLIMG-100
> Project: Magnolia Imaging Module
>  Issue Type: Bug
>  Components: image operations
>Affects Versions: 2.2.1
>Reporter: Christian Ringele
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AbstractLoader.java.patch, Generator.png, 
> OrigImage-PlacedIntoDMS.jpg, out1-works.png, out1-worksNot.jpg, 
> Output-using-BufferedImage.TYPE_INT_RGB.jpg
>
>
> Description:
> Calling an image generator which uses a FromContent (extends AbstractLoader) 
> operation will result in wrong JPGs.
> If storing PNGs it works fine. As PNGs have a alpha channel, the alpha value 
> is correctly applied.
> Storing a JPG, it seems as the ImageIO.write() method writes the alpha value 
> as a color and not ignoring it as it should.
> Reproduce:
> 1. Import the generator attached to this issue. Just containing one 
> operation, the load operation.
> 2. Add a test image to DMS.
> 3. execute this code with correct paths:
> {code}
> final ImagingModuleConfig config = (ImagingModuleConfig) 
> ModuleRegistry.Factory.getInstance().getModuleInstance("imaging");
> final ImageGenerator generator = 
> config.getGenerators().get("myOperationChainBResize");
> Session dmsSession = MgnlContext.getJCRSession("dms");
> Node origImage = dmsSession.getNode("/test/orig");
> final Content content = 
> info.magnolia.cms.util.ContentUtil.asContent(origImage);
> final ParameterProvider parameterProvider = new 
> ContentParameterProvider(new SimpleEqualityContentWrapper(content));
> final BufferedImage bufferedImage = generator.generate(parameterProvider);
> ImageIO.write(bufferedImage, "png", new 
> File("/Users/cringele/Documents/temp_stuff/image-test/create/out1-works.png"));
> ImageIO.write(bufferedImage, "jpg", new 
> File("/Users/cringele/Documents/temp_stuff/image-test/create/out1-worksNot.jpg"));
> {code}
> You can also write the stream back into JCR, the result is the same. So for 
> testing much easier into a file.
> Source of the problem:
> info.magnolia.imaging.operations.load.AbstractLoader.apply(BufferedImage, P)
> {code}
> if (source != null) {
> throw new ImagingException("This operation currently does not support 
> overlaying images");
> }
> final BufferedImage loaded = loadSource(filterParams);
> if (loaded == null) {
> throw new ImagingException("Could not load image for " + filterParams);
> }
> //This line is the source of the problem. Using BufferedImage.TYPE_INT_RGB 
> would work because it wouldn't contain any alpha channel. Of course just for 
> testing applicable.
> final BufferedImage img = new BufferedImage(loaded.getWidth(), 
> loaded.getHeight(), BufferedImage.TYPE_INT_ARGB_PRE);
> final Graphics2D g = img.createGraphics();
> if (backgroundColor != null) {
> g.setColor(backgroundColor);
> g.fill(new Rectangle(0, 0, img.getWidth(), img.getHeight()));
> }
> g.drawImage(loaded, null, 0, 0);
> // TODO would this make any difference ? g.drawRenderedImage(loaded, null);
> g.dispose();
> return img;
> {code}
> Proof of the problem source:
> First possibility: Execute this code just passing back the loaded 
> BufferedImage
> {code}
> if (source != null) {
> throw new ImagingException("This operation currently does not support 
> overlaying images");
> }
> final BufferedImage loaded = loadSource(filterParams);
> if (loaded == null) {
> throw new ImagingException("Could not load image for " + filterParams);
> }
> return loaded;
> {code}
> Second possibility: Pass back the created BufferedImage (img) withour loagin 
> the orig image on top.
> Like this you can compare alpha value in PNG to color in JPG.
> {code}
> if (source != null) {
> throw new ImagingException("This operation currently does not support 
> overlaying images");
> }
> final BufferedImage loaded = loadSource(filterParams);
> if (loaded == null) {
> throw new ImagingException("Could not load image for " + filterParams);
> }
> final BufferedImage img = new BufferedImage(loaded.getWidth(), 
> loaded.getHeight(), BufferedImage.TYPE_INT_ARGB_PRE);
> final Graphics2D g = img.createGraphics();
> if (backgroundColor != null) {
> g.setColor(backgroundColor);
> g.fill(new Rectangle(0, 0, img.getWidth(), img.getHeight()));
> }
> //Image not loaded on top of it
> //g.drawImage(loaded, null, 0, 0);
> // TODO would this m

[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4087) STK: Update all JS and their structure aligned to prototype - missing parts

[JIRA (on behalf of Christian Ringele)]

 [ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Ringele updated MAGNOLIA-4087:


Fix Version/s: 4.5
   (was: 4.5.7)

> STK: Update all JS and their structure aligned to prototype - missing parts
> ---
>
> Key: MAGNOLIA-4087
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4087
> Project: Magnolia
>  Issue Type: Task
>  Security Level: Public
>Affects Versions: 4.5
>Reporter: Natascha Desmarais
>Assignee: Christian Ringele
> Fix For: 4.5
>
>
> The javascripts need to be checked for content updates (considering 
> timestamps from our last update to the prototype on the scriptloaders for 
> example - especially check for mobile as well, I recall some last minute 
> tweaks to those plugins and libs)

-- 
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: 

[magnolia-dev] [JIRA] (MGNLSTK-1102) TemplatesAvailablility ignores TemplateConfig ID value. ID value is not populated, cause bean has no setter and getter.

[JIRA (on behalf of Christian Ringele)]

Christian Ringele
 created  MGNLSTK-1102


TemplatesAvailablility ignores TemplateConfig ID value. ID value is not populated, cause bean has no setter and getter.















Issue Type:


Bug



Affects Versions:


2.0.8



Assignee:


Ondrej Chytil



Attachments:


TemplatesAvailability_IgnoredID.png



Components:


base system



Created:


26/Feb/13 10:25 AM



Description:


In the site definitions TemplateAvailablility, the id value is completly ignored.
the bean does not contain any if value it could operate upon.

The class
info.magnolia.module.templatingkit.sites.TemplateConfig
does not contain an id variable and their according population.
Therefor the info.magnolia.module.templatingkit.sites.TemplateAvailability can not operate on the id value, but operates wrongly on the tempate name.

That would mean, that only one template with the same name can be provided, firs found first served.




Fix Versions:


2.0.x



Project:


Magnolia Standard Templating Kit



Priority:


Major




Reporter:


Christian Ringele




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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: 

[magnolia-dev] [JIRA] (MGNLSTK-1131) stkRedirect should have control title for possibility defining a title in different languages.

[JIRA (on behalf of Christian Ringele)]

Christian Ringele
 created  MGNLSTK-1131


stkRedirect should have control title for possibility defining a title in different languages.















Issue Type:


Improvement



Assignee:


Ondrej Chytil



Created:


12/Mar/13 8:57 AM



Description:


As the title can only be set over the adminCentral, therefor the page dialog should contain a title property. Without it the author can't set a title in different languages. The control should also have the 'i18n = true' property.




Project:


Magnolia Standard Templating Kit



Priority:


Neutral




Reporter:


Christian Ringele




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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: 

[magnolia-dev] [JIRA] (MGNLSTK-453) 'Bookmark' part of text-features available on all pages?

[JIRA (on behalf of Christian Ringele)]

Christian Ringele
 reopened  MGNLSTK-453


'Bookmark' part of text-features available on all pages?
















Correct status and fix version to set.





Change By:


Christian Ringele
(25/Mar/13 2:02 PM)




Resolution:


Fixed





Status:


Closed
Reopened



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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: 

[magnolia-dev] [JIRA] (MGNLSTK-453) 'Bookmark' part of text-features available on all pages?

[JIRA (on behalf of Christian Ringele)]

Christian Ringele
 updated  MGNLSTK-453


'Bookmark' part of text-features available on all pages?
















Change By:


Christian Ringele
(25/Mar/13 2:03 PM)




Fix Version/s:


1.x



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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: 

[magnolia-dev] [JIRA] (MGNLSTK-422) AllowedBodyClasses in BodyClassResolver.java should probably be configurable within STK?

[JIRA (on behalf of Christian Ringele)]

Christian Ringele
 updated  MGNLSTK-422


AllowedBodyClasses in BodyClassResolver.java should probably be configurable within STK?
















Change By:


Christian Ringele
(25/Mar/13 2:05 PM)




Fix Version/s:


1.x



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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: 

[magnolia-dev] [JIRA] (MGNLSTK-422) AllowedBodyClasses in BodyClassResolver.java should probably be configurable within STK?

[JIRA (on behalf of Christian Ringele)]

Christian Ringele
 reopened  MGNLSTK-422


AllowedBodyClasses in BodyClassResolver.java should probably be configurable within STK?
















Correct status and fix version to set.





Change By:


Christian Ringele
(25/Mar/13 2:04 PM)




Resolution:


Fixed





Status:


Closed
Reopened



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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: 

[magnolia-dev] [JIRA] (MGNLSTK-436) Make inplace templating more usable

[JIRA (on behalf of Christian Ringele)]

Christian Ringele
 updated  MGNLSTK-436


Make inplace templating more usable
















Change By:


Christian Ringele
(25/Mar/13 2:12 PM)




Fix Version/s:


1.x



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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: 

[magnolia-dev] [JIRA] (MGNLSTK-435) Paragraph for easy access to data in data module (or standard model classes for it)

[JIRA (on behalf of Christian Ringele)]

Christian Ringele
 updated  MGNLSTK-435


Paragraph for easy access to data in data module (or standard model classes for it)
















Change By:


Christian Ringele
(25/Mar/13 2:11 PM)




Fix Version/s:


1.x



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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: