[magnolia-dev] [JIRA] (MGNLDATA-229) Clean up obsolete update tasks

2013-11-25 Thread on behalf of Roman Kovařík














































Roman Kovařík
 created  MGNLDATA-229


Clean up obsolete update tasks















Issue Type:


Bug



Affects Versions:


2.2



Assignee:


Roman Kovařík



Created:


25/Nov/13 11:10 AM



Description:


Remove obsolete update tasks.




Fix Versions:


2.2.1



Project:


Magnolia Data Module



Priority:


Neutral




Reporter:


Roman Kovařík




























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] (MGNLGROOVY-100) Clean up obsolete update tasks

2013-11-25 Thread on behalf of Roman Kovařík














































Roman Kovařík
 created  MGNLGROOVY-100


Clean up obsolete update tasks















Issue Type:


Task



Affects Versions:


2.2



Assignee:


Roman Kovařík



Created:


25/Nov/13 1:00 PM



Description:


Clean up obsolete update tasks.




Fix Versions:


2.2.1



Project:


Magnolia Groovy Module



Priority:


Neutral




Reporter:


Roman Kovařík



Security Level:


Public 




























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] (MGNLPUR-114) Clean up obsolete update tasks

2013-11-25 Thread on behalf of Roman Kovařík














































Roman Kovařík
 created  MGNLPUR-114


Clean up obsolete update tasks















Issue Type:


Task



Affects Versions:


2.2



Assignee:


Roman Kovařík



Created:


25/Nov/13 2:53 PM



Description:


Clean up obsolete update tasks.




Project:


Magnolia Public User Registration



Priority:


Neutral




Reporter:


Roman Kovařík




























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] (MGNLRSSAGG-130) Clean up obsolete update tasks

2013-11-25 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLRSSAGG-130


Clean up obsolete update tasks 
















Change By:


Roman Kovařík
(26/Nov/13 8:12 AM)




Summary:


Migrate from 4.5.8 to 2.2.0
Clean up obsolete update tasks 



























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] (MGNLRSSAGG-130) Migrate from 4.5.8 to 2.2.0

2013-11-25 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLRSSAGG-130


Migrate from 4.5.8 to 2.2.0
















Change By:


Roman Kovařík
(26/Nov/13 8:12 AM)




Assignee:


Roman Kovařík





Fix Version/s:


2.2.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] (MGNLPUR-21) Provide a "profile" page (STK)

2013-11-27 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-21


Provide a "profile" page (STK)
















Change By:


Roman Kovařík
(27/Nov/13 10:25 AM)




Fix Version/s:


ideas





Fix Version/s:


1.4.x





Fix Version/s:


2.2.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] (MGNLPUR-110) Public users security subapp should be positioned in 3rd tab

2013-11-27 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-110


Public users security subapp should be positioned in 3rd tab
















Change By:


Roman Kovařík
(27/Nov/13 10:21 AM)




Labels:


ne





Fix Version/s:


ideas



























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] (MGNLPUR-110) Public users security subapp should be positioned in 3rd tab

2013-11-27 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-110


Public users security subapp should be positioned in 3rd tab
















Change By:


Roman Kovařík
(27/Nov/13 10:20 AM)




Labels:


ne





Fix Version/s:


Backlog - Next





Component/s:


app



























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] (MGNLPUR-16) UserRegistrar should be configurable

2013-11-27 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-16


UserRegistrar should be configurable
















Change By:


Roman Kovařík
(27/Nov/13 10:24 AM)




Labels:


next





Component/s:


config



























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] (MGNLPUR-38) Users get created eventhough the confirmation emails couldn't been sent

2013-11-27 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-38


Users get created eventhough the confirmation emails couldn't been sent
















Change By:


Roman Kovařík
(27/Nov/13 10:28 AM)




Labels:


maintenance





Component/s:


registration



























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] (MGNLPUR-16) UserRegistrar should be configurable

2013-11-27 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-16


UserRegistrar should be configurable
















Change By:


Roman Kovařík
(27/Nov/13 10:35 AM)




Labels:


next
maintenance



























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] (MGNLPUR-57) Review components provided by PUR

2013-11-27 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-57


Review components provided by PUR
















Change By:


Roman Kovařík
(27/Nov/13 10:34 AM)




Labels:


maintenance





Priority:


Major
Neutral





Component/s:


management



























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] (MGNLPUR-67) Password Reminder form displays ambiguous error message when a username can't be found

2013-11-27 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-67


Password Reminder form displays ambiguous error message when a username can't be found
















Change By:


Roman Kovařík
(27/Nov/13 10:41 AM)




Labels:


pur





Component/s:


registration



























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] (MGNLPUR-85) Profile update wrongly requires full name

2013-11-27 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-85


Profile update wrongly requires full name
















Change By:


Roman Kovařík
(27/Nov/13 10:42 AM)




Labels:


maintenance





Component/s:


config



























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] (MGNLPUR-65) UserManager for public does not have a realmName property

2013-11-27 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-65


UserManager for public does not have a realmName property
















Change By:


Roman Kovařík
(27/Nov/13 10:38 AM)




Labels:


pur security
quickwin





Component/s:


config



























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] (MGNLPUR-77) Use mgnl:folder instead of mgnl:content for the /public node in users workspace

2013-11-27 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-77


Use mgnl:folder instead of mgnl:content for the /public node in users workspace
















Change By:


Roman Kovařík
(27/Nov/13 10:41 AM)




Labels:


quickwin





Component/s:


management



























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] (MGNLPUR-94) ®Stamp in verification link is replaced by ®Stamp in hotmail

2013-11-27 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-94


®Stamp in verification link is replaced by ®Stamp in hotmail
















Change By:


Roman Kovařík
(27/Nov/13 10:49 AM)




Labels:


maintenance





Component/s:


registration



























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] (MGNLPUR-106) realmName node is not automatically created

2013-11-27 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-106


realmName node is not automatically created
















Change By:


Roman Kovařík
(27/Nov/13 10:58 AM)




Labels:


next





Fix Version/s:


1.4.6





Fix Version/s:


2.2.1





Fix Version/s:


1.4.x





Fix Version/s:


2.2.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] (MGNLPUR-106) realmName node is not automatically created

2013-11-27 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-106


realmName node is not automatically created
















Change By:


Roman Kovařík
(27/Nov/13 10:58 AM)




Component/s:


registration



























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] (MGNLPUR-114) Clean up obsolete update tasks

2013-11-27 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-114


Clean up obsolete update tasks
















Change By:


Roman Kovařík
(27/Nov/13 11:04 AM)




Labels:


next





Component/s:


management



























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] (MGNLPUR-12) Translations of default emails which are sent by p.u.r

2013-11-27 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-12


Translations of default emails which are sent by p.u.r
















Change By:


Roman Kovařík
(27/Nov/13 11:17 AM)




Component/s:


management



























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] (MGNLPUR-12) Translations of default emails which are sent by p.u.r

2013-11-27 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-12


Translations of default emails which are sent by p.u.r
















Change By:


Roman Kovařík
(27/Nov/13 11:15 AM)




Labels:


ideas





Assignee:


Grégory Joseph





Fix Version/s:


2.2.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] (MGNLPUR-11) default language for new users

2013-11-27 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-11


default language for new users
















Change By:


Roman Kovařík
(27/Nov/13 11:14 AM)




Fix Version/s:


2.2.x





Component/s:


config



























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] (MGNLPUR-22) make the Mail strategy more flexible

2013-11-27 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-22


make the Mail strategy more flexible
















Change By:


Roman Kovařík
(27/Nov/13 11:19 AM)




Assignee:


Zdenek Skodik





Fix Version/s:


2.2.x





Component/s:


registration



























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] (MGNLPUR-11) default language for new users

2013-11-27 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-11


default language for new users
















Change By:


Roman Kovařík
(27/Nov/13 11:18 AM)




Assignee:


Grégory Joseph



























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] (MGNLGROOVY-101) Provide Chinese translation for duplicate action

2013-11-27 Thread on behalf of Roman Kovařík














































Federico Grilli
 created  MGNLGROOVY-101


Provide Chinese translation for duplicate action















Issue Type:


Task



Affects Versions:


2.2.1



Assignee:


Cheng Hu



Created:


27/Nov/13 1:12 PM



Description:


key is groovy.browser.actions.duplicateScript




Fix Versions:


2.2.1



Project:


Magnolia Groovy Module



Priority:


Neutral




Reporter:


Federico Grilli



Security Level:


Public 




























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] (MGNLPUR-77) Use mgnl:folder instead of mgnl:content for the /public node in users workspace

2013-11-27 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-77


Use mgnl:folder instead of mgnl:content for the /public node in users workspace
















Change By:


Roman Kovařík
(27/Nov/13 1:25 PM)




Fix Version/s:


2.2.1





Fix Version/s:


1.4.6





Affects Version/s:


2.0





Affects Version/s:


1.4



























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] (MGNLPUR-115) Use mgnl:folder instead of mgnl:content for the /public node in users workspace

2013-11-27 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-115


Use mgnl:folder instead of mgnl:content for the /public node in users workspace
















Change By:


Roman Kovařík
(27/Nov/13 2:04 PM)




Fix Version/s:


1.4.x





Fix Version/s:


2.2.1





Affects Version/s:


1.4





Affects Version/s:


2.0



























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] (MGNLPUR-115) Use mgnl:folder instead of mgnl:content for the /public node in users workspace

2013-11-27 Thread on behalf of Roman Kovařík














































Jozef Chocholacek
 created  MGNLPUR-115


Use mgnl:folder instead of mgnl:content for the /public node in users workspace















Issue Type:


Improvement



Affects Versions:


2.0



Assignee:


Roman Kovařík



Components:


management



Created:


27/Nov/13 2:04 PM



Description:


PUR module is using mgnl:content nodetype for the /public node where it stores the publicly registered users. But the nodes for the core users (/system and /admin) are of the mgnl:folder type. This causes problems in the Security App for M5.

The fix should change the install tasks to use mgnl:folder instead of mgnl:content, and update tasks to change the primary node type of the existing /public node.




Fix Versions:


2.2.1



Project:


Magnolia Public User Registration



Labels:


quickwin




Priority:


Neutral




Reporter:


Jozef Chocholacek




























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] (MGNLPUR-116) Check if dependency to "magnolia-4-5-migration" is still required and possibly remove it

2013-12-02 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-116


Check if dependency to "magnolia-4-5-migration" is still required and possibly remove it
















Change By:


Roman Kovařík
(02/Dec/13 10:15 AM)




Labels:


maintenance





Component/s:


management



























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] (MGNLUI-2466) Modules should not have "trees" node in configuration anymore

2013-12-02 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLUI-2466


Modules should not have "trees" node in configuration anymore
















Change By:


Roman Kovařík
(02/Dec/13 3:06 PM)




Description:


Several modules still have "trees" nodes which used to be for the menuing in <5 versions of adminCentral. these should be removed as they are no longer used. It should be researched if there is more code to remove.It should be researched which modules still have this.I create this ticket as a parent ticket - tickets for all modules should be linked to this one.I did a search on the CE bundle and came up with modules:imaging, adminInterface, pur
 (MGNLPUR-114)
, forum, stk



























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] (MGNLPUR-21) Provide a "profile" page (STK)

2013-12-04 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-21


Provide a "profile" page (STK)
















Change By:


Roman Kovařík
(04/Dec/13 9:15 AM)




Component/s:


management



























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] (MGNLPUR-21) Provide a "profile" page (STK)

2013-12-04 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-21


Provide a "profile" page (STK)
















Change By:


Roman Kovařík
(04/Dec/13 9:12 AM)




Labels:


architecture



























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] (MGNLPUR-106) realmName node is not automatically created

2013-12-05 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-106


realmName node is not automatically created
















Change By:


Roman Kovařík
(05/Dec/13 10:08 AM)




Fix Version/s:


1.4.x





Fix Version/s:


2.2.x





Fix Version/s:


1.4.6





Fix Version/s:


2.2.1



























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] (MGNLPUR-117) As a user I can register for multiple sites

2013-12-06 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-117


As a user I can register for multiple sites
















Change By:


Roman Kovařík
(06/Dec/13 11:26 AM)




Issue Type:


New Feature
Story



























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] (MGNLPUR-117) As a user I can register for multiple sites

2013-12-06 Thread on behalf of Roman Kovařík














































Roman Kovařík
 created  MGNLPUR-117


As a user I can register for multiple sites















Issue Type:


New Feature



Assignee:


Unassigned


Components:


multisite



Created:


06/Dec/13 11:25 AM



Description:


Although MGNLPUR-89 provided configuration for multiple sites, we should ensure  that:

	user registered for one site is not logged for second site
	user registered for one site doesn't have any collision when accessing second site.
	user registered for default site can access other sites






Fix Versions:


Backlog - Next



Project:


Magnolia Public User Registration



Labels:


architecture




Priority:


Neutral




Reporter:


Roman Kovařík




























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] (MGNLPUR-106) realmName node is not automatically created

2013-12-06 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-106


realmName node is not automatically created
















Change By:


Roman Kovařík
(06/Dec/13 11:34 AM)




Description:


MGNLPUR-89 provided configuration for multiple sites. We can configure also different {{realmName}} per site. * when we try to register a user, {{PathNotFoundException}} is thrown because {{REALM_NAME}} node is not automatically created in the {{Users}} workspace.*
 the basepath for a site should be {{/public/siteName}}*
 workaround could be creating node via {{groovy/jcr browser}} 





Component/s:


multisite





Component/s:


registration



























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] (MGNLPUR-106) realmName node is not automatically created

2013-12-06 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-106


realmName node is not automatically created
















Change By:


Roman Kovařík
(06/Dec/13 11:35 AM)




Parent:


MGNLPUR-117





Issue Type:


Bug
Sub-task



























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] (MGNLPUR-117) As a public user I can register for multiple sites

2013-12-06 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-117


As a public user I can register for multiple sites
















Change By:


Roman Kovařík
(06/Dec/13 11:37 AM)




Summary:


As a
 public
 user I can register for multiple sites



























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] (MGNLPUR-118) As a public user I have my profile page

2013-12-06 Thread on behalf of Roman Kovařík














































Roman Kovařík
 created  MGNLPUR-118


As a public user I have my profile page















Issue Type:


Story



Assignee:


Unassigned


Components:


public users



Created:


06/Dec/13 11:43 AM



Description:


As a public user I have my profile page a can see profile pages of other users.




Fix Versions:


Backlog - Next



Project:


Magnolia Public User Registration



Labels:


architecture




Priority:


Neutral




Reporter:


Roman Kovařík




























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] (MGNLPUR-21) Provide a "profile" page (STK)

2013-12-06 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-21


Provide a "profile" page (STK)
















Change By:


Roman Kovařík
(06/Dec/13 11:44 AM)




Parent:


MGNLPUR-118





Issue Type:


New Feature
Sub-task



























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] (MGNLPUR-21) Provide a "profile" page (STK)

2013-12-06 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-21


Provide a "profile" page (STK)
















Change By:


Roman Kovařík
(06/Dec/13 11:47 AM)




Description:


This might be a topic more specific to STK, or the integration therewith. Templates of other modules (forum, comments, etc) could use links to "profile pages" of users.
Profile
*
 page
 template page
 takes parameter to identify user (?userId=roman)
*
suggested content components:
**
text&image (profile photo + about me)
**
image gallery
**
embedded Video
**
contact
**
...



























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] (MGNLPUR-21) Provide a "profile" page (STK)

2013-12-06 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-21


Provide a "profile" page (STK)
















Change By:


Roman Kovařík
(06/Dec/13 11:46 AM)




Labels:


architecture
 ux





Description:


This might be a topic more specific to STK, or the integration therewith. Templates of other modules (forum, comments, etc) could use links to "profile pages" of users.

Profile page template page takes parameter to identify user (?userId=roman)suggested content components:text&image (profile photo + about me)image galleryembedded Videocontact...



























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] (MGNLPUR-21) Provide a "profile" page (STK)

2013-12-06 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-21


Provide a "profile" page (STK)
















Change By:


Roman Kovařík
(06/Dec/13 12:10 PM)




Description:


This might be a topic more specific to STK, or the integration therewith. Templates of other modules (forum, comments, etc) could use links to "profile pages" of users.* page takes parameter to identify user (?userId=roman)* suggested content components:** text&image (profile photo + about me)** image gallery** embedded Video** contact** ...
Add possibility to enable/disable this feature, something like:{{config/configurations/site1/userProfileConfiguration/enableProfilePage=false}}



























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] (MGNLPUR-119) Provide sample CustomUserProfile class

2013-12-06 Thread on behalf of Roman Kovařík














































Roman Kovařík
 created  MGNLPUR-119


Provide sample CustomUserProfile class















Issue Type:


Sub-task



Assignee:


Unassigned


Components:


public users



Created:


06/Dec/13 12:21 PM



Description:


We need to extend UserProfile class with more properties like:

	contact information
	profile photo
	favourite video link
	...
before creation of new sample multistep form registration form, see .






Fix Versions:


Backlog - Next



Project:


Magnolia Public User Registration



Labels:


ux




Priority:


Neutral




Reporter:


Roman Kovařík




























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] (MGNLPUR-119) Provide sample CustomUserProfile class

2013-12-06 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-119


Provide sample CustomUserProfile class
















Change By:


Roman Kovařík
(06/Dec/13 12:22 PM)




Labels:


ux



























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] (MGNLPUR-120) Create new sample multistep registration form

2013-12-06 Thread on behalf of Roman Kovařík














































Roman Kovařík
 created  MGNLPUR-120


Create new sample multistep registration form















Issue Type:


Sub-task



Assignee:


Unassigned


Components:


registration



Created:


06/Dec/13 12:24 PM



Description:


We need to Create new sample multistep registration form with more optional informations like:

	contact information
	profile photo
	favourite video link
	...
to fill new sample UserProfile class, see MGNLPUR-119.






Fix Versions:


Backlog - Next



Project:


Magnolia Public User Registration



Priority:


Neutral




Reporter:


Roman Kovařík




























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] (MGNLPUR-120) Create new sample multistep registration form

2013-12-06 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-120


Create new sample multistep registration form
















Change By:


Roman Kovařík
(06/Dec/13 12:25 PM)




Labels:


ux



























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] (MGNLDATA-231) Add dependency to Dam module

2013-12-06 Thread on behalf of Roman Kovařík














































Roman Kovařík
 reopened  MGNLDATA-231


Add dependency to Dam module
















Please update also dependency to UI in the module descriptor.





Change By:


Roman Kovařík
(06/Dec/13 4:03 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] (MGNLPUR-121) i18n: Chinese translation problem in PUR dialog

2013-12-09 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-121


i18n: Chinese translation problem in PUR dialog
















Change By:


Roman Kovařík
(09/Dec/13 9:27 AM)




Labels:


i18n
 maintenance



























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] (MGNLPUR-121) i18n: Chinese translation problem in PUR dialog

2013-12-11 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-121


i18n: Chinese translation problem in PUR dialog
















Change By:


Roman Kovařík
(11/Dec/13 9:11 AM)




Fix Version/s:


2.2.x





Fix Version/s:


2.2.1



























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] (MGNLWORKFLOW-180) Remove permissions for no longer existing workspaces (openWFE)

2013-12-11 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLWORKFLOW-180


Remove permissions for no longer existing workspaces (openWFE)
















Change By:


Roman Kovařík
(11/Dec/13 11:16 AM)




Assignee:


Roman Kovařík
Eric Hechinger



























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] (MGNLRSSAGG-138) Remove permissions for no longer existing workspaces (openWFE)

2013-12-11 Thread on behalf of Roman Kovařík














































Tobias Mattsson
 created  MGNLRSSAGG-138


Remove permissions for no longer existing workspaces (openWFE)















Issue Type:


Bug



Affects Versions:


2.0



Assignee:


Roman Kovařík



Created:


11/Dec/13 11:14 AM



Description:


Magnolia 4.5 used the workspaces Store and Expressions to store workflow (openWFE based) related data. Those are gone since 5.0 so we should also remove permissions on those.

Tasks:

	Remove these permissions from the appropriate bootstrap files.






Fix Versions:


2.2.1



Project:


Magnolia RSS Aggregator Module



Priority:


Blocker




Reporter:


Tobias Mattsson




























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] (MGNLRSSAGG-137) Remove permissions for no longer existing workspaces (openWFE)

2013-12-11 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLRSSAGG-137


Remove permissions for no longer existing workspaces (openWFE)
















Change By:


Roman Kovařík
(11/Dec/13 11:18 AM)




Assignee:


Roman Kovařík
Eric Hechinger



























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] (MGNLWORKFLOW-180) Remove permissions for no longer existing workspaces (openWFE)

2013-12-11 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLWORKFLOW-180


Remove permissions for no longer existing workspaces (openWFE)
















Change By:


Roman Kovařík
(11/Dec/13 11:17 AM)




Assignee:


Roman Kovařík
Eric Hechinger



























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] (MGNLWORKFLOW-181) Remove permissions for no longer existing workspaces (openWFE)

2013-12-11 Thread on behalf of Roman Kovařík














































Tobias Mattsson
 created  MGNLWORKFLOW-181


Remove permissions for no longer existing workspaces (openWFE)















Issue Type:


Bug



Affects Versions:


5.0



Assignee:


Eric Hechinger



Created:


11/Dec/13 11:19 AM



Description:


Magnolia 4.5 used the workspaces Store and Expressions to store workflow (openWFE based) related data. Those are gone since 5.0 so we should also remove permissions on those.

Tasks:

	Remove these permissions from the appropriate bootstrap files.






Fix Versions:


5.2.1



Project:


Magnolia Workflow Module



Priority:


Blocker




Reporter:


Tobias Mattsson




























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] (MGNLUI-2518) Do not migrate acl if they already exist

2013-12-11 Thread on behalf of Roman Kovařík














































Eric Hechinger
 created  MGNLUI-2518


Do not migrate acl if they already exist















Issue Type:


Bug



Affects Versions:


5.1.1



Assignee:


Roman Kovařík



Components:


security app



Created:


11/Dec/13 1:08 PM



Description:


Do not migrate acl if they already exist in MoveAclPermissionsBetweenWorkspaces.




Fix Versions:


5.2.1



Project:


Magnolia UI



Priority:


Neutral




Reporter:


Eric Hechinger



Security Level:


Public 




























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] (MGNLUI-2518) Do not migrate acl if they already exist

2013-12-11 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLUI-2518


Do not migrate acl if they already exist
















Change By:


Roman Kovařík
(11/Dec/13 1:09 PM)




Assignee:


Roman Kovařík
Eric Hechinger



























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] (MGNLRSSAGG-137) Remove permissions for no longer existing workspaces (openWFE)

2013-12-12 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLRSSAGG-137


Remove permissions for no longer existing workspaces (openWFE)
















Change By:


Roman Kovařík
(12/Dec/13 10:23 AM)




Description:


Magnolia 4.5 used the workspaces Store and Expressions to store workflow (openWFE based) related data. Those are gone since 5.0 so we should also remove permissions on those.Tasks:- Remove these permissions from the appropriate bootstrap files
. 
:{code}/rss-aggregator-base/acl_Expressions/rss-aggregator-base/acl_Store{code}



























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] (MGNLWORKFLOW-180) Remove permissions for no longer existing workspaces (openWFE)

2013-12-12 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLWORKFLOW-180


Remove permissions for no longer existing workspaces (openWFE)
















Change By:


Roman Kovařík
(12/Dec/13 10:23 AM)




Description:


Magnolia 4.5 used the workspaces Store and Expressions to store workflow (openWFE based) related data. Those are gone since 5.0 so we should also remove permissions on those.Tasks:- Remove these permissions from the appropriate bootstrap files
. 
:{code}/workflow-base/acl_Expressions/workflow-base/acl_Store{code}



























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] (MGNLACTIVATION-51) Activation Tools app hangs when started on public instance

2013-12-12 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLACTIVATION-51


Activation Tools app hangs when started on public instance
















Change By:


Roman Kovařík
(12/Dec/13 2:29 PM)




Priority:


Major
Critical



























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] (MGNLACTIVATION-51) Activation Tools app hangs when started on public instance

2013-12-12 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLACTIVATION-51


Activation Tools app hangs when started on public instance
















Change By:


Roman Kovařík
(12/Dec/13 2:35 PM)




Fix Version/s:


5.2.1





Fix Version/s:


5.2.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] (MGNLACTIVATION-51) Activation Tools app hangs when started on public instance

2013-12-16 Thread on behalf of Roman Kovařík














































Roman Kovařík
 reopened  MGNLACTIVATION-51


Activation Tools app hangs when started on public instance
















Change By:


Roman Kovařík
(16/Dec/13 9:28 AM)




Resolution:


Fixed





Status:


In QA
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] (MGNLFORM-217) Clean up obsolete update tasks

2013-12-16 Thread on behalf of Roman Kovařík














































Roman Kovařík
 created  MGNLFORM-217


 Clean up obsolete update tasks















Issue Type:


Bug



Affects Versions:


2.2.1



Assignee:


Unassigned


Components:


migration & updates



Created:


16/Dec/13 10:23 AM



Description:


Update from 1.4:



2013-12-16 10:14:17,544 ERROR info.magnolia.module.InstallContextImpl   : > Error while installing or updating form module. Task 'Confirm mail type' failed. (NullPointerException: )
java.lang.NullPointerException
	at info.magnolia.module.delta.BootstrapFileUtil.getElementAsStream(BootstrapFileUtil.java:104)
	at info.magnolia.module.delta.PartialBootstrapTask.getNodeStream(PartialBootstrapTask.java:120)
	at info.magnolia.module.delta.PartialBootstrapTask.execute(PartialBootstrapTask.java:108)
	at info.magnolia.module.ModuleManagerImpl.applyDeltas(ModuleManagerImpl.java:512)
	at info.magnolia.module.ModuleManagerImpl.installOrUpdateModule(ModuleManagerImpl.java:494)
	at info.magnolia.module.ModuleManagerImpl$1.doExec(ModuleManagerImpl.java:277)
	at info.magnolia.context.MgnlContext$VoidOp.exec(MgnlContext.java:415)
	at info.magnolia.context.MgnlContext$VoidOp.exec(MgnlContext.java:412)
	at info.magnolia.context.MgnlContext.doInSystemContext(MgnlContext.java:386)
	at info.magnolia.module.ModuleManagerImpl.performInstallOrUpdate(ModuleManagerImpl.java:271)
	at info.magnolia.module.ui.ModuleManagerWebUI$2.run(ModuleManagerWebUI.java:127)
	at java.lang.Thread.run(Thread.java:662)






Fix Versions:


2.2.x



Project:


Magnolia Form Module



Labels:


maintenance




Priority:


Major




Reporter:


Roman Kovařík



Security Level:


Public 




























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] (MGNLRSSAGG-140) Update from 1.3 fails

2013-12-16 Thread on behalf of Roman Kovařík














































Roman Kovařík
 created  MGNLRSSAGG-140


Update from 1.3 fails















Issue Type:


Bug



Affects Versions:


2.2.1



Assignee:


Unassigned


Created:


16/Dec/13 10:31 AM



Description:




Could not install or update rssaggregator module. Task 'Planet feed subcriptions dialog.' failed. (IOException: Can't find resource to bootstrap at /mgnl-bootstrap/rssaggregator/dialogs/config.modules.rssaggregator.dialogs.feedSubscriptions.xml)






Fix Versions:


2.2.2



Project:


Magnolia RSS Aggregator Module



Priority:


Major




Reporter:


Roman Kovařík




























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] (MGNLGS-69) Make sure configuration between migrated and fresh instance is the same

2013-12-16 Thread on behalf of Roman Kovařík














































Roman Kovařík
 created  MGNLGS-69


Make sure configuration between migrated and fresh instance is the same















Issue Type:


Bug



Affects Versions:


2.0



Assignee:


Roman Kovařík



Created:


17/Dec/13 8:34 AM



Description:


http://hudson.magnolia-cms.com/view/X/job/magnolia-4-5-migration_with_integration_tests/ws/magnolia-migration-integration/diff-reports/modules.google-sitemap.html




Fix Versions:


2.1



Project:


Magnolia Google Sitemap Module



Labels:


maintenance




Priority:


Neutral




Reporter:


Roman Kovařík




























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] (MGNLDATA-236) Make sure configuration between migrated and fresh instance is the same

2013-12-16 Thread on behalf of Roman Kovařík














































Roman Kovařík
 created  MGNLDATA-236


Make sure configuration between migrated and fresh instance is the same















Issue Type:


Bug



Affects Versions:


2.2.1



Assignee:


Roman Kovařík



Created:


17/Dec/13 8:40 AM



Description:


http://hudson.magnolia-cms.com/view/X/job/magnolia-4-5-migration_with_integration_tests/ws/magnolia-migration-integration/diff-reports/modules.data.html




Fix Versions:


2.2.1



Project:


Magnolia Data Module



Labels:


maintenance




Priority:


Neutral




Reporter:


Roman Kovařík




























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] (MGNLRSSAGG-142) Make sure configuration between migrated and fresh instance is the same

2013-12-17 Thread on behalf of Roman Kovařík














































Roman Kovařík
 created  MGNLRSSAGG-142


Make sure configuration between migrated and fresh instance is the same















Issue Type:


Bug



Affects Versions:


2.2.1



Assignee:


Roman Kovařík



Components:


rss_importer



Created:


17/Dec/13 9:36 AM



Description:


http://hudson.magnolia-cms.com/view/X/job/magnolia-4-5-migration_with_integration_tests/ws/magnolia-migration-integration/diff-reports/modules.data.html




Fix Versions:


2.2.1



Project:


Magnolia RSS Aggregator Module



Labels:


maintenance




Priority:


Neutral




Reporter:


Roman Kovařík




























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] (MGNLRSSAGG-142) Make sure configuration between migrated and fresh instance is the same

2013-12-17 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLRSSAGG-142


Make sure configuration between migrated and fresh instance is the same
















Change By:


Roman Kovařík
(17/Dec/13 10:11 AM)




Description:


4.5.12 -> 5.2.1
http://hudson.magnolia-cms.com/view/X/job/magnolia-4-5-migration_with_integration_tests/ws/magnolia-migration-integration/diff-reports/modules.data.html
5.1 -> 5.2.1http://hudson.magnolia-cms.com/view/X/job/m_4-5-migration_2.0.x-branch_with_integration_tests/ws/magnolia-migration-integration/diff-reports/modules.data.html



























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] (MGNLRSSAGG-140) Update from 1.3 fails

2013-12-17 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLRSSAGG-140


Update from 1.3 fails
















Change By:


Roman Kovařík
(17/Dec/13 10:37 AM)




Labels:


maintenance





Assignee:


Roman Kovařík





Fix Version/s:


2.1.1





Fix Version/s:


2.2.2



























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] (MGNLFORM-217) Clean up obsolete update tasks

2013-12-17 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLFORM-217


 Clean up obsolete update tasks
















Change By:


Roman Kovařík
(17/Dec/13 10:36 AM)




Assignee:


Roman Kovařík





Fix Version/s:


2.2.1





Fix Version/s:


2.2.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] (MGNLFORM-217) Clean up obsolete update tasks

2013-12-17 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLFORM-217


 Clean up obsolete update tasks
















Change By:


Roman Kovařík
(17/Dec/13 12:07 PM)




Affects Version/s:


2.2





Affects Version/s:


2.2.1



























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] (MGNLADMLEG-49) Make sure configuration between migrated and fresh instance is the same

2013-12-18 Thread on behalf of Roman Kovařík














































Roman Kovařík
 created  MGNLADMLEG-49


Make sure configuration between migrated and fresh instance is the same















Issue Type:


Bug



Affects Versions:


5.2



Assignee:


Roman Kovařík



Created:


18/Dec/13 11:10 AM



Description:


http://hudson.magnolia-cms.com/view/X/job/m_4-5-migration_2.0.x-branch_with_integration_tests/ws/magnolia-migration-integration/diff-reports/modules.adminInterface.html

http://hudson.magnolia-cms.com/view/X/job/magnolia-4-5-migration_with_integration_tests/ws/magnolia-migration-integration/diff-reports/modules.adminInterface.html




Fix Versions:


5.2.1



Project:


Magnolia Admininterface Legacy Module (4.x compatibility)



Priority:


Neutral




Reporter:


Roman Kovařík



Security Level:


Public 




























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] (MGNLFORUM-204) Make sure configuration between migrated and fresh instance is the same

2013-12-18 Thread on behalf of Roman Kovařík














































Roman Kovařík
 created  MGNLFORUM-204


Make sure configuration between migrated and fresh instance is the same















Issue Type:


Bug



Affects Versions:


3.2



Assignee:


Roman Kovařík



Components:


VersionHandler



Created:


18/Dec/13 1:34 PM



Description:


http://hudson.magnolia-cms.com/view/X/job/magnolia-4-5-migration_with_integration_tests/ws/magnolia-migration-integration/diff-reports/modules.adminInterface.html

http://hudson.magnolia-cms.com/view/X/job/m_4-5-migration_2.0.x-branch_with_integration_tests/ws/magnolia-migration-integration/diff-reports/modules.adminInterface.html




Fix Versions:


3.2.1



Project:


Magnolia Forum Module



Priority:


Neutral




Reporter:


Roman Kovařík



Security Level:


Public 




























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] (MGNLADMLEG-48) PageMVCServlet should be using AggregationState or normalize URLs and be stricter when looking up which page to serve

2013-12-18 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLADMLEG-48


PageMVCServlet should be using AggregationState or normalize URLs and be stricter when looking up which page to serve
















Change By:


Roman Kovařík
(18/Dec/13 1:59 PM)




Fix Version/s:


5.2.x





Fix Version/s:


5.2.1



























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] (MGNLDATA-238) Exclude shop data types from automatic app creation

2013-12-19 Thread on behalf of Roman Kovařík














































Roman Kovařík
 created  MGNLDATA-238


Exclude shop data types from automatic app creation















Issue Type:


Bug



Affects Versions:


2.2.1



Assignee:


Unassigned


Created:


19/Dec/13 10:58 AM



Description:


Exclude in DataModuleVersionHandler:

	shopSupplier
	shopProduct
	shop



in DataTypesToContentAppsTask and AddFolderSupportToDataAppsTask.




Fix Versions:


2.2.x



Project:


Magnolia Data Module



Priority:


Neutral




Reporter:


Roman Kovařík




























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] (MGNLDATA-237) Exclude shop data types from automatic app creation

2013-12-19 Thread on behalf of Roman Kovařík














































Roman Kovařík
 created  MGNLDATA-237


Exclude shop data types from automatic app creation















Issue Type:


Bug



Affects Versions:


2.2.1



Assignee:


Unassigned


Created:


19/Dec/13 10:56 AM



Description:


Exclude in DataModuleVersionHandler:

	shopSupplier
	shopProduct
	shop



in DataTypesToContentAppsTask and AddFolderSupportToDataAppsTask.




Fix Versions:


2.2.x



Project:


Magnolia Data Module



Priority:


Neutral




Reporter:


Roman Kovařík




























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] (MGNLDATA-238) Exclude shop data types from automatic app creation

2013-12-19 Thread on behalf of Roman Kovařík














































Roman Kovařík
 deleted  MGNLDATA-238


Exclude shop data types from automatic app creation
























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] (MGNLUI-2534) Messages App doesn't show result of send action

2013-12-19 Thread on behalf of Roman Kovařík














































Roman Kovařík
 created  MGNLUI-2534


 Messages App doesn't show result of send action















Issue Type:


Improvement



Affects Versions:


5.2.1



Assignee:


Unassigned


Created:


19/Dec/13 11:54 AM



Description:



	We don't see result when sending an email to a another user or group (We cannot be sure that email was really sent).






Fix Versions:


5.2.x



Project:


Magnolia UI



Priority:


Neutral




Reporter:


Roman Kovařík



Security Level:


Public 




























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] (MGNLACTIVATION-74) Wrong configuration of XAA after upgrade from 4.5.x

2013-12-20 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLACTIVATION-74


Wrong configuration of XAA after upgrade from 4.5.x
















Change By:


Roman Kovařík
(20/Dec/13 10:17 AM)




Description:


{
{Activation}} is new module in {{Magnolia 5}} so clean install of {{Activation Module}} is performed when migration from {{Magnolia 4.5.x}} which rebootstraps {{XAA}} configuration.{
code}2013-12-19 14:01:36,140 ERROR dule.exchangetransactional.TransactionalSyndicator: Non EE subscriber detected.info.magnolia.cms.exchange.ExchangeException: Non EE subscriber detected.	at info.magnolia.module.exchangetransactional.TransactionalSyndicator$2.run(TransactionalSyndicator.java:181)	at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)	at java.lang.Thread.run(Thread.java:662){code}Content is activated on public.Tested on:* 4.5.12 -> 5.2* 4.5.14 -> 5.2.1* 4.5.15-SNAPSHOT -> 5.2.1



























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] (MGNLDMS-277) When activating folder all documents are activated as well

2014-01-03 Thread on behalf of Roman Kovařík














































Roman Kovařík
 reopened  MGNLDMS-277


When activating folder all documents are activated as well
















Although only the parent folder is activated, whole content is sent to public while activating.





Change By:


Roman Kovařík
(03/Jan/14 1:57 PM)




Resolution:


Cannot Reproduce





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] (MGNLACTIVATION-76) Temporary file should be written only once during activation

2014-01-06 Thread on behalf of Roman Kovařík














































Joerg von Frantzius
 created  MGNLACTIVATION-76


Temporary file should be written only once during activation















Issue Type:


Improvement



Assignee:


Unassigned


Created:


06/Jan/14 1:06 PM



Description:


As noted in MGNLACTIVATION-42, currently the temporary file with activated content is written once per subscriber. So if e.g. a folder with files amounting to 500MB is activated on 4 subscribers, there are effectively 2GB written to disk in the process of activation.

If possible, the temporary file should be written only once per activation in order to reduce disk IO.

The actual writing of the file happens in info.magnolia.module.activation.Transporter.prepareTempFile(ActivationContent).




Fix Versions:


5.2.x



Project:


Magnolia Activation Module



Priority:


Neutral




Reporter:


Joerg von Frantzius




























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] (MGNLACTIVATION-77) Generate timestamp for activation as close to actual transfer as possible

2014-01-06 Thread on behalf of Roman Kovařík














































Joerg von Frantzius
 created  MGNLACTIVATION-77


Generate timestamp for activation as close to actual transfer as possible















Issue Type:


Bug



Affects Versions:


5.1



Assignee:


Unassigned


Created:


06/Jan/14 1:08 PM



Description:


In info.magnolia.module.exchangesimple.BaseSyndicatorImpl.transportActivatedData(ActivationContent, URLConnection, String), a timestamp of current author time is gathered, and later on sent to public instances together with the activation request. The activation request is then refused by the public instance if the public's current time diverges from this author timestamp by more than 30s, presumably in order to verify author and public clocks are in sync.

Unfortunately, the timestamp on author is created before the temporary file with activation data is created in Transporter.transport(). Given a recursive activation with huge amounts of binary data (multiple GB) plus some load on author and public, these 30s can too easily be exceeded.

The timestamp on author should be created as shortly as possible before the actual sending of the activation HTTP request. Otherwise, the clock sync check will fail when creating the temp file takes longer than 30s, which probably isn't desired.




Fix Versions:


5.2.x



Project:


Magnolia Activation Module



Labels:


maintenance
support




Priority:


Neutral




Reporter:


Joerg von Frantzius




























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] (MGNLACTIVATION-43) Temporary file should be written only once during activation

2014-01-06 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLACTIVATION-43


Temporary file should be written only once during activation
















Change By:


Roman Kovařík
(06/Jan/14 1:08 PM)




Affects Version/s:


5.2.1



























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] (MGNLDMS-277) When activating folder all documents are activated as well

2014-01-06 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLDMS-277


When activating folder all documents are activated as well
















Change By:


Roman Kovařík
(06/Jan/14 1:22 PM)




Attachment:


config.modules.dms.trees.dms.xml



























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] (MGNLACTIVATION-74) Wrong configuration of XAA after upgrade from 4.5.x

2014-01-06 Thread on behalf of Roman Kovařík














































Roman Kovařík
 reopened  MGNLACTIVATION-74


Wrong configuration of XAA after upgrade from 4.5.x
















Wrong package name of Receive filter after upgrade from exchange-simple. 
http://hudson.magnolia-cms.com/view/X/job/magnolia-4-5-migration_with_integration_tests/ws/magnolia-migration-integration/diff-reports/server.filters.html





Change By:


Roman Kovařík
(06/Jan/14 3:02 PM)




Resolution:


Fixed





Status:


Resolved
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] (MGNLPUR-123) Make sure configuration between migrated and fresh instance is the same

2014-01-06 Thread on behalf of Roman Kovařík














































Roman Kovařík
 created  MGNLPUR-123


Make sure configuration between migrated and fresh instance is the same















Issue Type:


Bug



Affects Versions:


2.2



Assignee:


Unassigned


Components:


management



Created:


06/Jan/14 3:37 PM



Description:


http://hudson.magnolia-cms.com/view/X/job/magnolia-4-5-migration_with_integration_tests/ws/magnolia-migration-integration/diff-reports/modules.public-user-registration.html

http://hudson.magnolia-cms.com/view/X/job/m_4-5-migration_2.0.x-branch_with_integration_tests/ws/magnolia-migration-integration/diff-reports/modules.public-user-registration.html




Fix Versions:


2.2.2



Project:


Magnolia Public User Registration



Labels:


maintenance




Priority:


Neutral




Reporter:


Roman Kovařík




























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] (MGNLUI-2557) Visualize content which is read only

2014-01-09 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLUI-2557


Visualize content which is read only
















Change By:


Roman Kovařík
(09/Jan/14 12:24 PM)




Description:


We can see, reed only icon
 next to the status icon in the website tree
 when the page is read-only In {{Magnolia 4.5 }}.We should visualize this also in {{Magnolia 5}}.



























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] (MGNLUI-2557) Visualize content which is read only

2014-01-09 Thread on behalf of Roman Kovařík














































Roman Kovařík
 created  MGNLUI-2557


Visualize content which is read only















Issue Type:


Improvement



Affects Versions:


5.0



Assignee:


Roman Kovařík



Components:


pages app



Created:


09/Jan/14 12:23 PM



Description:


We can see, reed only icon when the page is read-only In {{Magnolia 4.5 }}.
We should visualize this also in Magnolia 5.




Fix Versions:


5.2.2



Project:


Magnolia UI



Priority:


Neutral




Reporter:


Roman Kovařík



Security Level:


Public 




























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] (MGNLUI-2557) Visualize content which is read only

2014-01-09 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLUI-2557


Visualize content which is read only
















Change By:


Roman Kovařík
(09/Jan/14 12:27 PM)




Description:


We can see, reed only icon next to the status icon in the
 website
 tree when the page is read-only
 In
 in
 {{Magnolia 4.5 }}
 (not only website tree)
.We should visualize this also in {{Magnolia 5}}.



























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] (MGNLUI-2557) Visualize content which is read only

2014-01-09 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLUI-2557


Visualize content which is read only
















Change By:


Roman Kovařík
(09/Jan/14 12:58 PM)




Description:


We can see, reed only icon next to the status icon in the tree when the page is read-only in {{Magnolia 4.5}} (not only website tree).We should visualize this also in {{Magnolia 5}}.
Investigation: already implemented, but doesn't work:{code}Caused by: java.security.AccessControlException: add_node,remove,set_property	at org.apache.jackrabbit.core.SessionImpl.checkPermission(SessionImpl.java:708)	at info.magnolia.jcr.wrapper.DelegateSessionWrapper.checkPermission(DelegateSessionWrapper.java:109)	at info.magnolia.jcr.wrapper.DelegateSessionWrapper.checkPermission(DelegateSessionWrapper.java:109)	at info.magnolia.jcr.wrapper.DelegateSessionWrapper.checkPermission(DelegateSessionWrapper.java:109)	at info.magnolia.ui.workbench.column.StatusColumnFormatter.generateCell(StatusColumnFormatter.java:97)	at com.vaadin.ui.Table.parseItemIdToCells(Table.java:2312)	at com.vaadin.ui.Table.getVisibleCellsNoCache(Table.java:2173)	at com.vaadin.ui.Table.refreshRenderedCells(Table.java:1694{code}



























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] (MGNLUI-2557) Visualize content which is read only

2014-01-09 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLUI-2557


Visualize content which is read only
















Change By:


Roman Kovařík
(09/Jan/14 1:00 PM)




Component/s:


workbench





Component/s:


app framework



























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] (MGNLUI-2557) Visualize content which is read only

2014-01-09 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLUI-2557


Visualize content which is read only
















Change By:


Roman Kovařík
(09/Jan/14 1:00 PM)




Component/s:


app framework





Component/s:


pages app



























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] (MGNLUI-2557) Visualize content which is read only

2014-01-09 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLUI-2557


Visualize content which is read only
















Change By:


Roman Kovařík
(09/Jan/14 3:10 PM)




Attachment:


statusColumn.png



























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] (MGNLUI-2557) Visualize content which is read only

2014-01-09 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLUI-2557


Visualize content which is read only
















Change By:


Roman Kovařík
(09/Jan/14 3:12 PM)




Description:


We can see, reed only icon next to the status icon in the tree when the page is read-only in {{Magnolia 4.5}} (not only website tree).We should visualize this also in {{Magnolia 5}}.Investigation: already implemented, but
 doesn
:# It
'
t work
s disabled by default # It's buggy
:{code}Caused by: java.security.AccessControlException: add_node,remove,set_property	at org.apache.jackrabbit.core.SessionImpl.checkPermission(SessionImpl.java:708)	at info.magnolia.jcr.wrapper.DelegateSessionWrapper.checkPermission(DelegateSessionWrapper.java:109)	at info.magnolia.jcr.wrapper.DelegateSessionWrapper.checkPermission(DelegateSessionWrapper.java:109)	at info.magnolia.jcr.wrapper.DelegateSessionWrapper.checkPermission(DelegateSessionWrapper.java:109)	at info.magnolia.ui.workbench.column.StatusColumnFormatter.generateCell(StatusColumnFormatter.java:97)	at com.vaadin.ui.Table.parseItemIdToCells(Table.java:2312)	at com.vaadin.ui.Table.getVisibleCellsNoCache(Table.java:2173)	at com.vaadin.ui.Table.refreshRenderedCells(Table.java:1694{code}
# If enabled and fixed, status icon overlaps permission icon.



























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] (MGNLUI-2557) Show permissions in status column

2014-01-10 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLUI-2557


Show permissions in status column
















Change By:


Roman Kovařík
(10/Jan/14 10:39 AM)




Summary:


Visualize content which is read only
Show permissions in status column





Issue Type:


Improvement
Bug





Description:


We can see
, reed
 read
 only icon next to the status icon in the tree when the page is read-only in {{Magnolia 4.5}} (not only website tree).We should visualize this also in {{Magnolia 5}}.Investigation: already implemented, but:# It's disabled by default # It's buggy:{code}Caused by: java.security.AccessControlException: add_node,remove,set_property	at org.apache.jackrabbit.core.SessionImpl.checkPermission(SessionImpl.java:708)	at info.magnolia.jcr.wrapper.DelegateSessionWrapper.checkPermission(DelegateSessionWrapper.java:109)	at info.magnolia.jcr.wrapper.DelegateSessionWrapper.checkPermission(DelegateSessionWrapper.java:109)	at info.magnolia.jcr.wrapper.DelegateSessionWrapper.checkPermission(DelegateSessionWrapper.java:109)	at info.magnolia.ui.workbench.column.StatusColumnFormatter.generateCell(StatusColumnFormatter.java:97)	at com.vaadin.ui.Table.parseItemIdToCells(Table.java:2312)	at com.vaadin.ui.Table.getVisibleCellsNoCache(Table.java:2173)	at com.vaadin.ui.Table.refreshRenderedCells(Table.java:1694{code}# If enabled and fixed, status icon overlaps permission icon.



























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] (MGNLFORM-222) Make sure configuration between migrated and fresh instance is the same

2014-01-10 Thread on behalf of Roman Kovařík














































Roman Kovařík
 created  MGNLFORM-222


Make sure configuration between migrated and fresh instance is the same















Issue Type:


Bug



Affects Versions:


2.2.1



Assignee:


Roman Kovařík



Components:


migration & updates



Created:


10/Jan/14 11:38 AM



Description:


http://hudson.magnolia-cms.com/view/X/job/m_4-5-migration_2.0.x-branch_with_integration_tests/ws/magnolia-migration-integration/diff-reports/modules.form.html

http://hudson.magnolia-cms.com/view/X/job/magnolia-4-5-migration_with_integration_tests/ws/magnolia-migration-integration/diff-reports/modules.form.html




Fix Versions:


2.2.2



Project:


Magnolia Form Module



Labels:


maintenance




Priority:


Neutral




Reporter:


Roman Kovařík



Security Level:


Public 




























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] (MGNLPUR-117) As a public user I can register for multiple sites

2014-01-10 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-117


As a public user I can register for multiple sites
















Change By:


Roman Kovařík
(10/Jan/14 1:42 PM)




Labels:


architecture
 next



























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] (MGNLPUR-118) As a public user I have my profile page

2014-01-10 Thread on behalf of Roman Kovařík














































Roman Kovařík
 updated  MGNLPUR-118


As a public user I have my profile page
















Change By:


Roman Kovařík
(10/Jan/14 1:41 PM)




Labels:


architecture
 next



























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] (MGNLFORM-222) Make sure configuration between migrated and fresh instance is the same

2014-01-10 Thread on behalf of Roman Kovařík














































Roman Kovařík
 reopened  MGNLFORM-222


Make sure configuration between migrated and fresh instance is the same
















Change By:


Roman Kovařík
(10/Jan/14 2:18 PM)




Resolution:


Fixed





Status:


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





<    5   6   7   8   9   10   11   12   13   14   >