[magnolia-dev] [JIRA] Commented: (MGNLOPENID-6) Replace startup tasks by regular install tasks to avoid configuration being overridden

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLOPENID-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30664#action_30664
 ] 

Hudson CI server commented on MGNLOPENID-6:
---

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-module-openid 
#7|http://hudson.magnolia-cms.com/job/magnolia-module-openid/7/]
 

 Replace startup tasks by regular install tasks to avoid configuration being 
 overridden
 --

 Key: MGNLOPENID-6
 URL: http://jira.magnolia-cms.com/browse/MGNLOPENID-6
 Project: Magnolia OpenID Module
  Issue Type: Improvement
Reporter: Grégory Joseph
Assignee: Grégory Joseph
 Fix For: 1.0




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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2251) Deletion should not de-activate immediately

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30666#action_30666
 ] 

Hudson CI server commented on MAGNOLIA-2251:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.4-branch 
#55|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/55/]
 MAGNOLIA-2251 Unused import.


 Deletion should not de-activate immediately
 ---

 Key: MAGNOLIA-2251
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2251
 Project: Magnolia
  Issue Type: Task
  Components: activation
Reporter: Grégory Joseph
Assignee: Jan Haderka
 Fix For: Green


 Possible paths:
 - trash
 - metadata
 This change should then possibly be applied to moving as well, consolidating 
 the way (de)activation works.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3259) Override for the extends feature

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30611#action_30611
 ] 

Hudson CI server commented on MAGNOLIA-3259:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-trunk 
#2065|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/2065/]
 MAGNOLIA-3259 Extends override - first cut.


 Override for the extends feature
 

 Key: MAGNOLIA-3259
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3259
 Project: Magnolia
  Issue Type: Bug
  Components: content2bean, core
Affects Versions: 4.3.4
Reporter: Jan Haderka
Assignee: Jan Haderka
 Fix For: 4.3.x


 The {{extends}} aggregates all the collection content by default. However in 
 some cases it is necessary to actually override the content of such 
 collections otherwise incorrect values will be inherited by extending node.

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





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

[magnolia-dev] [JIRA] Commented: (MGNLFORM-61) Show a clearer error message for failed noHTML validation

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLFORM-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30618#action_30618
 ] 

Hudson CI server commented on MGNLFORM-61:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-module-form_1.1-branch 
#2|http://hudson.magnolia-cms.com/job/magnolia-module-form_1.1-branch/2/]
 merging r37971 from trunk: Add some translations for form validation 
failure messages (touches MGNLFORM-61)


 Show a clearer error message for failed noHTML validation
 ---

 Key: MGNLFORM-61
 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-61
 Project: Magnolia Form Module
  Issue Type: Improvement
Affects Versions: 1.1.4
Reporter: Felix Rabe
Assignee: Tobias Mattsson
 Fix For: 1.1.4


 The file 
 {{/magnolia-module-form/src/main/resources/info/magnolia/module/form/messages_en.properties}}
  contains no line for the noHTML error message, showing a potentially 
 confusing invalid input instead.  Proposed change:
 {noformat}
  form.user.errorMessage.number = must be a number
 +form.user.errorMessage.noHTML = characters  are not allowed
  form.user.errorMessage.generic= Internal error, form could not be sent
 {noformat}
 I have applied this change locally and it works for me.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3334) FckEditor images not handled correctly without context path in URL

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30626#action_30626
 ] 

Hudson CI server commented on MAGNOLIA-3334:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.3-branch 
#108|http://hudson.magnolia-cms.com/job/magnolia_main-4.3-branch/108/]
 MAGNOLIA-3334
Rollback for 4.3.


 FckEditor images not handled correctly without context path in URL
 --

 Key: MAGNOLIA-3334
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3334
 Project: Magnolia
  Issue Type: Bug
  Components: core, fckeditor
Affects Versions: 4.3.7
Reporter: Ondřej Chytil
Assignee: Ondřej Chytil
 Fix For: 4.4.x

 Attachments: magnolia-module-fckeditor.patch


 When inserting images in fckEditor from DMS without context path in URL image 
 is rendered on page after saving but not in edit mode of fckEditor or in 
 preview window.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3310) UnicodeNormalizationFilter seems to be messing up the virtualUriMappings

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30627#action_30627
 ] 

Hudson CI server commented on MAGNOLIA-3310:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.4-branch 
#53|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/53/]
 MAGNOLIA-3310
Rollback for 4.4.


 UnicodeNormalizationFilter seems to be messing up the virtualUriMappings
 

 Key: MAGNOLIA-3310
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3310
 Project: Magnolia
  Issue Type: Bug
  Components: core
Affects Versions: 4.3.6
Reporter: Ernst Bunders
Assignee: Ondřej Chytil
Priority: Critical
 Fix For: 4.3.8


 Hello
 I discovered a problem with a virtual uri mapping (of type forward)and the 
 UnicodeNormalizationFilter. What i try to do is the following:
 I have a processed css file that creates the css for a configurable theme. 
 The theme also has a dialog that lets you do all kinds of theme settings.
 The theme css is called with some parameters: the uuid of the page node (to 
 resolve the theme config), and a version parameter (to create uniuque urls 
 for each 'version' of the theme).
 What i want is a virtalUriMapping for this css request, so i can call it 
 without request parameters, making it more cachable. Here is the 
 virtualUriMapping config:
 class: info.magnolia.cms.beans.config.RegexpVirtualURIMapping
 fromURI:  ^/themes/([^/]+)/([0-9]+)/theme\.css$
 toURI:  
 forward:/resources/vpro/themes/pip/css/theme.css?uuid=$1lastmodified=$2
 this way i can call my css from the template like: 
 http://localhost:8080/pip/themes/1fb8d8e1-d625-4c24-95a3-904e0102eddd/1286288160080/theme.css
 And the request is forwarded to: 
 /resources/vpro/themes/pip/css/theme.css?uuid=1fb8d8e1-d625-4c24-95a3-904e0102edddlastmodified=1286288160080
 So that works but oh lala: when the css model class kicks into action: no 
 more request parameters.
 I put some breakpoints here and there and this is what i see:
 - Every request object is wrapped with a 
 info.magnolia.cms.filters.UnicodeNormalizationFilter.UnicodeNormalizerRequestWrapper
  by the UnicodeNormalizationFilter filter.
 - this method has a method getParameterMap(), that will look into the wrapped 
 request and fetch the parameters only once.
 - so the first time the VirtualUriFilter is hit, the request wrapper is 
 wrapping a request with no parameters. So the 
 UnicodeNormalizerRequestWrapper.parameters map is empty.
 - The virtualUriMapping is found, the 'forward:' prefix is found, and a 
 request dispatcher is created (with proper requestUri and queryString values).
 - the request is forwarded.
 - At this point i would expect a new request to be created and reinserted 
 into the whole requests handling pipeline. So the next time 
 UnicodeNormalizationFilter is hit, i expect the request to be unwrapped. To 
 my surprise this is not the case. the request is wrapped already, and the 
 wrapper still has the parameters map (with zero entries)  from the first 
 request.
 The wrapper now wraps two requests! In it's field 'original' there is the 
 request with url:  
 http://localhost:8080/pip/themes/1fb8d8e1-d625-4c24-95a3-904e0102eddd/1286288160080/theme.css
  (the first request), and in it's field 'request' (inherited from 
 HttpServletRequestWrapper) a request with url: 
 /resources/vpro/themes/pip/css/theme.css and queryString: 
 uuid=1fb8d8e1-d625-4c24-95a3-904e0102edddlastmodified=1286288160080 ( the 
 new request)
 All a bit surprising, and It seems to me that the wrapper is still around at 
 the second request handling. Another thing that seems strange: why does the 
 UnicodeNormalizerRequestWrapper has it's own field for the wrapped request 
 and parameters, as it already extends HttpServletRequestWrapper. It seems to 
 me that the only method that actually adds someting is getHeader(String name).
 And thus: when i switch of the UnicodeNormalization filter: it works!

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





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

[magnolia-dev] [JIRA] Commented: (MGNLFORM-26) Add delete button for the form paragraph

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLFORM-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30594#action_30594
 ] 

Hudson CI server commented on MGNLFORM-26:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-module-form 
#1178|http://hudson.magnolia-cms.com/job/magnolia-module-form/1178/]
 MGNLFORM-26 - add delete button to the form paragraph bar


 Add delete button for the form paragraph
 

 Key: MGNLFORM-26
 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-26
 Project: Magnolia Form Module
  Issue Type: Improvement
Reporter: Teresa Miyar
Assignee: Zdenek Skodik
 Fix For: 1.2




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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3336) Multipart and Unicode filters do not release requests properly in case of errors

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30599#action_30599
 ] 

Hudson CI server commented on MAGNOLIA-3336:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.4-branch 
#52|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/52/]
 MAGNOLIA-3336 Make sure the stack is released properly even on errors.


 Multipart and Unicode filters do not release requests properly in case of 
 errors
 

 Key: MAGNOLIA-3336
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3336
 Project: Magnolia
  Issue Type: Bug
Affects Versions: 4.3.7
Reporter: Jan Haderka
Assignee: Jan Haderka
Priority: Critical
 Fix For: 4.4.x


 {{CosMultipartFilter}},{{MultipartFilter}} and {{UnicodeNormalization 
 filter}} manage stack of request/response wrappers on their own and do not 
 release those objects from the stack properly in case of errors the same way 
 {{ContextFilter}} does.
 They need to wrap chain execution in try block and make sure stack is updated 
 after execution even in case of errors.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2251) Deletion should not de-activate immediately

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30553#action_30553
 ] 

Hudson CI server commented on MAGNOLIA-2251:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.4-branch 
#49|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/49/]
 MAGNOLIA-2251 - Added missing bootstrap file for template.


 Deletion should not de-activate immediately
 ---

 Key: MAGNOLIA-2251
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2251
 Project: Magnolia
  Issue Type: Task
  Components: activation
Reporter: Grégory Joseph
Assignee: Jan Haderka
 Fix For: Green


 Possible paths:
 - trash
 - metadata
 This change should then possibly be applied to moving as well, consolidating 
 the way (de)activation works.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3334) FckEditor images not handled correctly without context path in URL

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30581#action_30581
 ] 

Hudson CI server commented on MAGNOLIA-3334:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.3-branch 
#107|http://hudson.magnolia-cms.com/job/magnolia_main-4.3-branch/107/]
 MAGNOLIA-3334
Links generated with context path.
Test cases updated.


 FckEditor images not handled correctly without context path in URL
 --

 Key: MAGNOLIA-3334
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3334
 Project: Magnolia
  Issue Type: Bug
  Components: core, fckeditor
Affects Versions: 4.3.7
Reporter: Ondřej Chytil
Assignee: Ondřej Chytil
 Fix For: 4.3.x


 When inserting images in fckEditor from DMS without context path in URL image 
 is rendered on page after saving but not in edit mode of fckEditor or in 
 preview window.

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





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

[magnolia-dev] [JIRA] Commented: (MGNLFORM-58) Add support for multi step forms

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLFORM-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30584#action_30584
 ] 

Hudson CI server commented on MGNLFORM-58:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-module-form 
#1174|http://hudson.magnolia-cms.com/job/magnolia-module-form/1174/]
 MGNLFORM-58 standard form model is now capable of multi step by default, 
extracted form processing to a parallel class heirarchy and simplified the 
implemenation


 Add support for multi step forms
 

 Key: MGNLFORM-58
 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-58
 Project: Magnolia Form Module
  Issue Type: New Feature
Reporter: Tobias Mattsson
Assignee: Tobias Mattsson

 Add support for multi step forms. Relies in the addition of preexecution in 
 magnolia-core.
 * Each step will be configured on a page of its own so that different steps 
 can be on a page with content specific to that step.
 * The back button must work as expected.
 * Must be able to use the same form in multiple tabs. Tabs should not use 
 each others values.

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





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

[magnolia-dev] [JIRA] Commented: (MGNLFORM-58) Add support for multi step forms

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLFORM-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30585#action_30585
 ] 

Hudson CI server commented on MGNLFORM-58:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-module-form 
#1175|http://hudson.magnolia-cms.com/job/magnolia-module-form/1175/]
 MGNLFORM-58 updated the description the file upload field to inform that 
file upload only works on the last step


 Add support for multi step forms
 

 Key: MGNLFORM-58
 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-58
 Project: Magnolia Form Module
  Issue Type: New Feature
Reporter: Tobias Mattsson
Assignee: Tobias Mattsson

 Add support for multi step forms. Relies in the addition of preexecution in 
 magnolia-core.
 * Each step will be configured on a page of its own so that different steps 
 can be on a page with content specific to that step.
 * The back button must work as expected.
 * Must be able to use the same form in multiple tabs. Tabs should not use 
 each others values.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3335) Mixin information is not persisted during versioning

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30586#action_30586
 ] 

Hudson CI server commented on MAGNOLIA-3335:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.4-branch 
#50|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/50/]
 MAGNOLIA-3335 Trasnfer node types when versioning and report them from the 
version rather then from frozen node in ContentVersion


 Mixin information is not persisted during versioning
 

 Key: MAGNOLIA-3335
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3335
 Project: Magnolia
  Issue Type: Bug
  Components: core
Affects Versions: 4.3.7
Reporter: Jan Haderka
Assignee: Jan Haderka
 Fix For: 4.4.x


 Mixin info is not transferred while copying content to the {{mgnlVersion}} 
 space and as such doesn't become part of the version and is not restored when 
 restoring the content.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3311) nodebuilder: add an exception handler which logs but proceeds with the processing

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30518#action_30518
 ] 

Hudson CI server commented on MAGNOLIA-3311:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.3-branch 
#106|http://hudson.magnolia-cms.com/job/magnolia_main-4.3-branch/106/]
 MAGNOLIA-3311 Rollback changes.


 nodebuilder: add an exception handler which logs but proceeds with the 
 processing
 -

 Key: MAGNOLIA-3311
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3311
 Project: Magnolia
  Issue Type: Improvement
  Components: core
Reporter: Ondřej Chytil
Assignee: Ondřej Chytil
Priority: Minor
 Fix For: 4.3.x


 Error handler which simply logs warnings messages into stacktrace.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3311) nodebuilder: add an exception handler which logs but proceeds with the processing

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30519#action_30519
 ] 

Hudson CI server commented on MAGNOLIA-3311:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.4-branch 
#46|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/46/]
 MAGNOLIA-3311 Rollback changes


 nodebuilder: add an exception handler which logs but proceeds with the 
 processing
 -

 Key: MAGNOLIA-3311
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3311
 Project: Magnolia
  Issue Type: Improvement
  Components: core
Reporter: Ondřej Chytil
Assignee: Ondřej Chytil
Priority: Minor
 Fix For: 4.3.x


 Error handler which simply logs warnings messages into stacktrace.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3311) nodebuilder: add an exception handler which logs but proceeds with the processing

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30520#action_30520
 ] 

Hudson CI server commented on MAGNOLIA-3311:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-trunk 
#2064|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/2064/]
 MAGNOLIA-3311 Rollback changes.


 nodebuilder: add an exception handler which logs but proceeds with the 
 processing
 -

 Key: MAGNOLIA-3311
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3311
 Project: Magnolia
  Issue Type: Improvement
  Components: core
Reporter: Ondřej Chytil
Assignee: Ondřej Chytil
Priority: Minor
 Fix For: 4.3.x


 Error handler which simply logs warnings messages into stacktrace.

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





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

[magnolia-dev] [JIRA] Commented: (MGNLFORM-58) Add support for multi step forms

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLFORM-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30537#action_30537
 ] 

Hudson CI server commented on MGNLFORM-58:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-module-form 
#1171|http://hudson.magnolia-cms.com/job/magnolia-module-form/1171/]
 MGNLFORM-58 missing license header for AbstractFormProcessor


 Add support for multi step forms
 

 Key: MGNLFORM-58
 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-58
 Project: Magnolia Form Module
  Issue Type: New Feature
Reporter: Tobias Mattsson
Assignee: Tobias Mattsson

 Add support for multi step forms. Relies in the addition of preexecution in 
 magnolia-core.
 * Each step will be configured on a page of its own so that different steps 
 can be on a page with content specific to that step.
 * The back button must work as expected.
 * Must be able to use the same form in multiple tabs. Tabs should not use 
 each others values.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30545#action_30545
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[ee_magnolia-module-enterprise_4.4-branch 
#57|http://hudson.magnolia-cms.com/job/ee_magnolia-module-enterprise_4.4-branch/57/]
 MAGNOLIA-88: refactoring: soft locking becomes a separate module. Removed 
all code and deps related to that.


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30547#action_30547
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[ee_magnolia-module-enterprise_4.4-branch 
#58|http://hudson.magnolia-cms.com/job/ee_magnolia-module-enterprise_4.4-branch/58/]
 MAGNOLIA-88: refactoring: removed old package.


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30546#action_30546
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.4-branch 
#47|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/47/]
 MAGNOLIA-88: refactoring: soft locking becomes a separate module and no 
longer depends on templating


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2251) Deletion should not de-activate immediately

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30550#action_30550
 ] 

Hudson CI server commented on MAGNOLIA-2251:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/yellow.gif! 
[magnolia_main-4.4-branch 
#48|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/48/]
 MAGNOLIA-2251 - Special deleted page template with functionality to 
preview or restore deleted page.


 Deletion should not de-activate immediately
 ---

 Key: MAGNOLIA-2251
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2251
 Project: Magnolia
  Issue Type: Task
  Components: activation
Reporter: Grégory Joseph
Assignee: Jan Haderka
 Fix For: Green


 Possible paths:
 - trash
 - metadata
 This change should then possibly be applied to moving as well, consolidating 
 the way (de)activation works.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3310) UnicodeNormalizationFilter seems to be messing up the virtualUriMappings

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30499#action_30499
 ] 

Hudson CI server commented on MAGNOLIA-3310:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/yellow.gif! 
[magnolia_main-4.4-branch 
#41|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/41/]
 MAGNOLIA-3310
Request unwrapped before forwarding.


 UnicodeNormalizationFilter seems to be messing up the virtualUriMappings
 

 Key: MAGNOLIA-3310
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3310
 Project: Magnolia
  Issue Type: Bug
  Components: core
Affects Versions: 4.3.6
Reporter: Ernst Bunders
Assignee: Ondřej Chytil
Priority: Critical
 Fix For: 4.3.x


 Hello
 I discovered a problem with a virtual uri mapping (of type forward)and the 
 UnicodeNormalizationFilter. What i try to do is the following:
 I have a processed css file that creates the css for a configurable theme. 
 The theme also has a dialog that lets you do all kinds of theme settings.
 The theme css is called with some parameters: the uuid of the page node (to 
 resolve the theme config), and a version parameter (to create uniuque urls 
 for each 'version' of the theme).
 What i want is a virtalUriMapping for this css request, so i can call it 
 without request parameters, making it more cachable. Here is the 
 virtualUriMapping config:
 class: info.magnolia.cms.beans.config.RegexpVirtualURIMapping
 fromURI:  ^/themes/([^/]+)/([0-9]+)/theme\.css$
 toURI:  
 forward:/resources/vpro/themes/pip/css/theme.css?uuid=$1lastmodified=$2
 this way i can call my css from the template like: 
 http://localhost:8080/pip/themes/1fb8d8e1-d625-4c24-95a3-904e0102eddd/1286288160080/theme.css
 And the request is forwarded to: 
 /resources/vpro/themes/pip/css/theme.css?uuid=1fb8d8e1-d625-4c24-95a3-904e0102edddlastmodified=1286288160080
 So that works but oh lala: when the css model class kicks into action: no 
 more request parameters.
 I put some breakpoints here and there and this is what i see:
 - Every request object is wrapped with a 
 info.magnolia.cms.filters.UnicodeNormalizationFilter.UnicodeNormalizerRequestWrapper
  by the UnicodeNormalizationFilter filter.
 - this method has a method getParameterMap(), that will look into the wrapped 
 request and fetch the parameters only once.
 - so the first time the VirtualUriFilter is hit, the request wrapper is 
 wrapping a request with no parameters. So the 
 UnicodeNormalizerRequestWrapper.parameters map is empty.
 - The virtualUriMapping is found, the 'forward:' prefix is found, and a 
 request dispatcher is created (with proper requestUri and queryString values).
 - the request is forwarded.
 - At this point i would expect a new request to be created and reinserted 
 into the whole requests handling pipeline. So the next time 
 UnicodeNormalizationFilter is hit, i expect the request to be unwrapped. To 
 my surprise this is not the case. the request is wrapped already, and the 
 wrapper still has the parameters map (with zero entries)  from the first 
 request.
 The wrapper now wraps two requests! In it's field 'original' there is the 
 request with url:  
 http://localhost:8080/pip/themes/1fb8d8e1-d625-4c24-95a3-904e0102eddd/1286288160080/theme.css
  (the first request), and in it's field 'request' (inherited from 
 HttpServletRequestWrapper) a request with url: 
 /resources/vpro/themes/pip/css/theme.css and queryString: 
 uuid=1fb8d8e1-d625-4c24-95a3-904e0102edddlastmodified=1286288160080 ( the 
 new request)
 All a bit surprising, and It seems to me that the wrapper is still around at 
 the second request handling. Another thing that seems strange: why does the 
 UnicodeNormalizerRequestWrapper has it's own field for the wrapped request 
 and parameters, as it already extends HttpServletRequestWrapper. It seems to 
 me that the only method that actually adds someting is getHeader(String name).
 And thus: when i switch of the UnicodeNormalization filter: it works!

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30505#action_30505
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[ee_magnolia-module-enterprise_4.4-branch 
#49|http://hudson.magnolia-cms.com/job/ee_magnolia-module-enterprise_4.4-branch/49/]
 

 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30504#action_30504
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/yellow.gif! 
[magnolia_main-4.4-branch 
#42|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/42/]
 MAGNOLIA-88: added isTimeout method to interface


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30506#action_30506
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/yellow.gif! 
[magnolia_main-4.4-branch 
#43|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/43/]
 MAGNOLIA-88: refactoring: changed return type of method lockedBy(..) from 
List to Set both because user names should actually be unique and to avoid 
silly, useless conversion in implementations


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30507#action_30507
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[ee_magnolia-module-enterprise_4.4-branch 
#50|http://hudson.magnolia-cms.com/job/ee_magnolia-module-enterprise_4.4-branch/50/]
 MAGNOLIA-88: refactoring: no need to convert from set to list


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30508#action_30508
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[ee_magnolia-module-enterprise_4.4-branch 
#51|http://hudson.magnolia-cms.com/job/ee_magnolia-module-enterprise_4.4-branch/51/]
 MAGNOLIA-88: return else filter is not skipped.


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MGNLSTK-671) Singleton Template Definitiona (feature pages): Contain relative include of mainArea.ftl which doesn't work if using a custom main.ftl

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLSTK-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30509#action_30509
 ] 

Hudson CI server commented on MGNLSTK-671:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[standard-templating-kit 
#2709|http://hudson.magnolia-cms.com/job/standard-templating-kit/2709/]
 MGNLSTK-671
Update task modified.


 Singleton Template Definitiona (feature pages): Contain relative include of 
 mainArea.ftl which doesn't work if using a custom main.ftl
 --

 Key: MGNLSTK-671
 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-671
 Project: Magnolia Standard Templating Kit
  Issue Type: Bug
  Components: templates
Affects Versions: 1.3.4
Reporter: Christian Ringele
Assignee: Ondřej Chytil
 Fix For: 1.3.x

 Attachments: Screen shot 2010-08-02 at 12.18.48 PM.png


 Relative includes of sub templates/sub snippets don't work, if you use a 
 main.ftl located in a different location/module.
 The relative include is the executed on the new location (relative to the new 
 main.ftl).
 We had the same problem with all Section templates and removed the relative 
 pathes from the Section templates.
 The the singleton paragraph templates still contain these relative includes, 
 see print screen.
 Best would be to check all template definitions (and all ftl's for include of 
 macros) if there are still any relative includes left.
 All includes, no matter where, should be absolute paths.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3310) UnicodeNormalizationFilter seems to be messing up the virtualUriMappings

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30510#action_30510
 ] 

Hudson CI server commented on MAGNOLIA-3310:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/yellow.gif! 
[magnolia_main-4.4-branch 
#44|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/44/]
 MAGNOLIA-3310 added comment noting what issue this is a fix for


 UnicodeNormalizationFilter seems to be messing up the virtualUriMappings
 

 Key: MAGNOLIA-3310
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3310
 Project: Magnolia
  Issue Type: Bug
  Components: core
Affects Versions: 4.3.6
Reporter: Ernst Bunders
Assignee: Ondřej Chytil
Priority: Critical
 Fix For: 4.3.x


 Hello
 I discovered a problem with a virtual uri mapping (of type forward)and the 
 UnicodeNormalizationFilter. What i try to do is the following:
 I have a processed css file that creates the css for a configurable theme. 
 The theme also has a dialog that lets you do all kinds of theme settings.
 The theme css is called with some parameters: the uuid of the page node (to 
 resolve the theme config), and a version parameter (to create uniuque urls 
 for each 'version' of the theme).
 What i want is a virtalUriMapping for this css request, so i can call it 
 without request parameters, making it more cachable. Here is the 
 virtualUriMapping config:
 class: info.magnolia.cms.beans.config.RegexpVirtualURIMapping
 fromURI:  ^/themes/([^/]+)/([0-9]+)/theme\.css$
 toURI:  
 forward:/resources/vpro/themes/pip/css/theme.css?uuid=$1lastmodified=$2
 this way i can call my css from the template like: 
 http://localhost:8080/pip/themes/1fb8d8e1-d625-4c24-95a3-904e0102eddd/1286288160080/theme.css
 And the request is forwarded to: 
 /resources/vpro/themes/pip/css/theme.css?uuid=1fb8d8e1-d625-4c24-95a3-904e0102edddlastmodified=1286288160080
 So that works but oh lala: when the css model class kicks into action: no 
 more request parameters.
 I put some breakpoints here and there and this is what i see:
 - Every request object is wrapped with a 
 info.magnolia.cms.filters.UnicodeNormalizationFilter.UnicodeNormalizerRequestWrapper
  by the UnicodeNormalizationFilter filter.
 - this method has a method getParameterMap(), that will look into the wrapped 
 request and fetch the parameters only once.
 - so the first time the VirtualUriFilter is hit, the request wrapper is 
 wrapping a request with no parameters. So the 
 UnicodeNormalizerRequestWrapper.parameters map is empty.
 - The virtualUriMapping is found, the 'forward:' prefix is found, and a 
 request dispatcher is created (with proper requestUri and queryString values).
 - the request is forwarded.
 - At this point i would expect a new request to be created and reinserted 
 into the whole requests handling pipeline. So the next time 
 UnicodeNormalizationFilter is hit, i expect the request to be unwrapped. To 
 my surprise this is not the case. the request is wrapped already, and the 
 wrapper still has the parameters map (with zero entries)  from the first 
 request.
 The wrapper now wraps two requests! In it's field 'original' there is the 
 request with url:  
 http://localhost:8080/pip/themes/1fb8d8e1-d625-4c24-95a3-904e0102eddd/1286288160080/theme.css
  (the first request), and in it's field 'request' (inherited from 
 HttpServletRequestWrapper) a request with url: 
 /resources/vpro/themes/pip/css/theme.css and queryString: 
 uuid=1fb8d8e1-d625-4c24-95a3-904e0102edddlastmodified=1286288160080 ( the 
 new request)
 All a bit surprising, and It seems to me that the wrapper is still around at 
 the second request handling. Another thing that seems strange: why does the 
 UnicodeNormalizerRequestWrapper has it's own field for the wrapped request 
 and parameters, as it already extends HttpServletRequestWrapper. It seems to 
 me that the only method that actually adds someting is getHeader(String name).
 And thus: when i switch of the UnicodeNormalization filter: it works!

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





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

[magnolia-dev] [JIRA] Commented: (MGNLFORM-58) Add support for multi step forms

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLFORM-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30511#action_30511
 ] 

Hudson CI server commented on MGNLFORM-58:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-module-form 
#1166|http://hudson.magnolia-cms.com/job/magnolia-module-form/1166/]
 MGNLFORM-58 multi step support, now depends on magnolia 4.4


 Add support for multi step forms
 

 Key: MGNLFORM-58
 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-58
 Project: Magnolia Form Module
  Issue Type: New Feature
Reporter: Tobias Mattsson
Assignee: Tobias Mattsson

 Add support for multi step forms. Relies in the addition of preexecution in 
 magnolia-core.
 * Each step will be configured on a page of its own so that different steps 
 can be on a page with content specific to that step.
 * The back button must work as expected.
 * Must be able to use the same form in multiple tabs. Tabs should not use 
 each others values.

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





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

[magnolia-dev] [JIRA] Commented: (MGNLFORM-62) BaseFormProcessorImpl.enabled should be true by default

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLFORM-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30512#action_30512
 ] 

Hudson CI server commented on MGNLFORM-62:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-module-form 
#1167|http://hudson.magnolia-cms.com/job/magnolia-module-form/1167/]
 MGNLFORM-62
Variable enabled set to true.


 BaseFormProcessorImpl.enabled should be true by default
 ---

 Key: MGNLFORM-62
 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-62
 Project: Magnolia Form Module
  Issue Type: Improvement
Affects Versions: 1.1.2
Reporter: Ondřej Chytil
Assignee: Ondřej Chytil
Priority: Trivial
 Fix For: 1.1.4




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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2251) Deletion should not de-activate immediately

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30513#action_30513
 ] 

Hudson CI server commented on MAGNOLIA-2251:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.4-branch 
#45|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/45/]
 MAGNOLIA-2251 -fixed path for the bootstrap file.


 Deletion should not de-activate immediately
 ---

 Key: MAGNOLIA-2251
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2251
 Project: Magnolia
  Issue Type: Task
  Components: activation
Reporter: Grégory Joseph
Assignee: Jan Haderka
 Fix For: Green


 Possible paths:
 - trash
 - metadata
 This change should then possibly be applied to moving as well, consolidating 
 the way (de)activation works.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30515#action_30515
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[ee_magnolia-module-enterprise_4.4-branch 
#54|http://hudson.magnolia-cms.com/job/ee_magnolia-module-enterprise_4.4-branch/54/]
 MAGNOLIA-88: removed work-in-progress code slipped in when committing 
javadoc


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3326) Fail on attempt to register catalog with existing name

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30459#action_30459
 ] 

Hudson CI server commented on MAGNOLIA-3326:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.4-branch 
#36|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/36/]
 MAGNOLIA-3326 Print out ugly stacktrace on duplicated catalog name and 
advice user on how to solve the problem.


 Fail on attempt to register catalog with existing name
 --

 Key: MAGNOLIA-3326
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3326
 Project: Magnolia
  Issue Type: Bug
  Components: core
Affects Versions: 4.3.7
Reporter: Jan Haderka
Assignee: Jan Haderka
 Fix For: 4.4.x


 Command catalogs names need to be unique, however {{CommandManager}} silently 
 re-registers catalogs in case of duplicate names. This often results in 
 issues that are difficult to track. Manager should instead refuse to register 
 duplicated catalog and print out the warning.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-2251) Deletion should not de-activate immediately

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30463#action_30463
 ] 

Hudson CI server commented on MAGNOLIA-2251:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/yellow.gif! 
[magnolia_main-4.4-branch 
#37|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/37/]
 MAGNOLIA-2251 - first step for multistage deletion - version, strip off 
content and mark with mixing on attempt to delete


 Deletion should not de-activate immediately
 ---

 Key: MAGNOLIA-2251
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2251
 Project: Magnolia
  Issue Type: Task
  Components: activation
Reporter: Grégory Joseph
Assignee: Jan Haderka
 Fix For: Green


 Possible paths:
 - trash
 - metadata
 This change should then possibly be applied to moving as well, consolidating 
 the way (de)activation works.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3310) UnicodeNormalizationFilter seems to be messing up the virtualUriMappings

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30464#action_30464
 ] 

Hudson CI server commented on MAGNOLIA-3310:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.3-branch 
#105|http://hudson.magnolia-cms.com/job/magnolia_main-4.3-branch/105/]
 MAGNOLIA-3310
Request unwrapped before forwarding.


 UnicodeNormalizationFilter seems to be messing up the virtualUriMappings
 

 Key: MAGNOLIA-3310
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3310
 Project: Magnolia
  Issue Type: Bug
  Components: core
Affects Versions: 4.3.6
Reporter: Ernst Bunders
Assignee: Ondřej Chytil
Priority: Critical
 Fix For: 4.3.x


 Hello
 I discovered a problem with a virtual uri mapping (of type forward)and the 
 UnicodeNormalizationFilter. What i try to do is the following:
 I have a processed css file that creates the css for a configurable theme. 
 The theme also has a dialog that lets you do all kinds of theme settings.
 The theme css is called with some parameters: the uuid of the page node (to 
 resolve the theme config), and a version parameter (to create uniuque urls 
 for each 'version' of the theme).
 What i want is a virtalUriMapping for this css request, so i can call it 
 without request parameters, making it more cachable. Here is the 
 virtualUriMapping config:
 class: info.magnolia.cms.beans.config.RegexpVirtualURIMapping
 fromURI:  ^/themes/([^/]+)/([0-9]+)/theme\.css$
 toURI:  
 forward:/resources/vpro/themes/pip/css/theme.css?uuid=$1lastmodified=$2
 this way i can call my css from the template like: 
 http://localhost:8080/pip/themes/1fb8d8e1-d625-4c24-95a3-904e0102eddd/1286288160080/theme.css
 And the request is forwarded to: 
 /resources/vpro/themes/pip/css/theme.css?uuid=1fb8d8e1-d625-4c24-95a3-904e0102edddlastmodified=1286288160080
 So that works but oh lala: when the css model class kicks into action: no 
 more request parameters.
 I put some breakpoints here and there and this is what i see:
 - Every request object is wrapped with a 
 info.magnolia.cms.filters.UnicodeNormalizationFilter.UnicodeNormalizerRequestWrapper
  by the UnicodeNormalizationFilter filter.
 - this method has a method getParameterMap(), that will look into the wrapped 
 request and fetch the parameters only once.
 - so the first time the VirtualUriFilter is hit, the request wrapper is 
 wrapping a request with no parameters. So the 
 UnicodeNormalizerRequestWrapper.parameters map is empty.
 - The virtualUriMapping is found, the 'forward:' prefix is found, and a 
 request dispatcher is created (with proper requestUri and queryString values).
 - the request is forwarded.
 - At this point i would expect a new request to be created and reinserted 
 into the whole requests handling pipeline. So the next time 
 UnicodeNormalizationFilter is hit, i expect the request to be unwrapped. To 
 my surprise this is not the case. the request is wrapped already, and the 
 wrapper still has the parameters map (with zero entries)  from the first 
 request.
 The wrapper now wraps two requests! In it's field 'original' there is the 
 request with url:  
 http://localhost:8080/pip/themes/1fb8d8e1-d625-4c24-95a3-904e0102eddd/1286288160080/theme.css
  (the first request), and in it's field 'request' (inherited from 
 HttpServletRequestWrapper) a request with url: 
 /resources/vpro/themes/pip/css/theme.css and queryString: 
 uuid=1fb8d8e1-d625-4c24-95a3-904e0102edddlastmodified=1286288160080 ( the 
 new request)
 All a bit surprising, and It seems to me that the wrapper is still around at 
 the second request handling. Another thing that seems strange: why does the 
 UnicodeNormalizerRequestWrapper has it's own field for the wrapped request 
 and parameters, as it already extends HttpServletRequestWrapper. It seems to 
 me that the only method that actually adds someting is getHeader(String name).
 And thus: when i switch of the UnicodeNormalization filter: it works!

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3316) Support execution of paragraph models before rendering starts

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30465#action_30465
 ] 

Hudson CI server commented on MAGNOLIA-3316:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/yellow.gif! 
[magnolia_main-4.4-branch 
#38|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/38/]
 MAGNOLIA-3316 set currentContent in AggregationState while creating and 
executing the model
MAGNOLIA-3316 model execution filter is now placed before 
backwardsCompatibilityFilter when installing


 Support execution of paragraph models before rendering starts
 -

 Key: MAGNOLIA-3316
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3316
 Project: Magnolia
  Issue Type: Improvement
  Components: templating
Reporter: Tobias Mattsson
Assignee: Tobias Mattsson
Priority: Minor
 Fix For: 4.4.x


 Using a special request parameter containing the uuid of a paragraph a filter 
 is triggered that performs execution of the paragraphs model before rendering 
 starts. The model can then decide if it wants to output something else or 
 continue with rendering. If it decides to continue it will be used when the 
 paragraph is rendered (the model is not executed again).

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30469#action_30469
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/yellow.gif! 
[magnolia_main-4.4-branch 
#39|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/39/]
 MAGNOLIA-88: added constant to interface


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30491#action_30491
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[ee_magnolia-module-enterprise_4.4-branch 
#47|http://hudson.magnolia-cms.com/job/ee_magnolia-module-enterprise_4.4-branch/47/]
 

 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30449#action_30449
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[ee_magnolia-module-enterprise_4.4-branch 
#43|http://hudson.magnolia-cms.com/job/ee_magnolia-module-enterprise_4.4-branch/43/]
 MAGNOLIA-88: use filter instead of servlet so to get the current main 
content path from the aggregation state instead of calculating it client-side 
using unreliable URI (too many manipulations intervene on it: i18n, short url, 
etc.). Cleaner layout for css and js resources. Update task for registering cms 
filter.


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30450#action_30450
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[ee_magnolia-module-enterprise_4.4-branch 
#44|http://hudson.magnolia-cms.com/job/ee_magnolia-module-enterprise_4.4-branch/44/]
 MAGNOLIA-88: debug log


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3324) Provide release method for LifeTimeSession utilities

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30417#action_30417
 ] 

Hudson CI server commented on MAGNOLIA-3324:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.4-branch 
#32|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/32/]
 MAGNOLIA-3324 release method for life time sessions


 Provide release method for LifeTimeSession utilities
 

 Key: MAGNOLIA-3324
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3324
 Project: Magnolia
  Issue Type: New Feature
Affects Versions: 4.3.7
Reporter: Jan Haderka
Assignee: Boris Kraft
 Fix For: 4.4.x




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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLI A-2526) Update json dependencies ?

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30420#action_30420
 ] 

Hudson CI server commented on MAGNOLIA-2526:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.3-branch 
#101|http://hudson.magnolia-cms.com/job/magnolia_main-4.3-branch/101/]
 MAGNOLIA-2526
JSON updated to version 2.3.


 Update json dependencies ?
 --

 Key: MAGNOLIA-2526
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2526
 Project: Magnolia
  Issue Type: Task
  Components: build
Reporter: Grégory Joseph
Assignee: Ondřej Chytil
 Fix For: 4.2.x


 We have a couple of dependencies to json, in the main project and in modules 
 (dms, data, ...) - maybe its time for an update - along with refreshing the 
 exclusions that go with the current version.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLI A-2526) Update json dependencies ?

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30429#action_30429
 ] 

Hudson CI server commented on MAGNOLIA-2526:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.3-branch 
#102|http://hudson.magnolia-cms.com/job/magnolia_main-4.3-branch/102/]
 MAGNOLIA-2526
Rollback changes.


 Update json dependencies ?
 --

 Key: MAGNOLIA-2526
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2526
 Project: Magnolia
  Issue Type: Task
  Components: build
Reporter: Grégory Joseph
Assignee: Ondřej Chytil
 Fix For: 4.2.x


 We have a couple of dependencies to json, in the main project and in modules 
 (dms, data, ...) - maybe its time for an update - along with refreshing the 
 exclusions that go with the current version.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3185) Upgrade FCKEditor in next major version release

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30389#action_30389
 ] 

Hudson CI server commented on MAGNOLIA-3185:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.4-branch 
#25|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/25/]
 MAGNOLIA-3185: upgraded to fckeditor 2.6.6
Links to other Magnolia pages
Links to documents in the DMS
Links to uploaded Documents
Tables (new features such as table header)
Inserting Uploaded images
Spellchecker (enabled by default)


 Upgrade FCKEditor in next major version release
 ---

 Key: MAGNOLIA-3185
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3185
 Project: Magnolia
  Issue Type: Task
  Components: fckeditor
Affects Versions: 4.3.1
Reporter: Jan Haderka
Assignee: Federico Grilli
 Fix For: 5.0

 Attachments: fck-2.6.6.patch


 2.6.6 is out ... we should consider upgrade.
 http://sourceforge.net/projects/fckeditor/files/FCKeditor/2.6.6/FCKeditor_2.6.6.tar.gz/download

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3185) Upgrade FCKEditor in next major version release

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30397#action_30397
 ] 

Hudson CI server commented on MAGNOLIA-3185:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.4-branch 
#28|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/28/]
 MAGNOLIA-3185: updated javadoc


 Upgrade FCKEditor in next major version release
 ---

 Key: MAGNOLIA-3185
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3185
 Project: Magnolia
  Issue Type: Task
  Components: fckeditor
Affects Versions: 4.3.1
Reporter: Jan Haderka
Assignee: Federico Grilli
 Fix For: 5.0

 Attachments: fck-2.6.6.patch


 2.6.6 is out ... we should consider upgrade.
 http://sourceforge.net/projects/fckeditor/files/FCKeditor/2.6.6/FCKeditor_2.6.6.tar.gz/download

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3316) Support execution of paragraph models before rendering starts

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30396#action_30396
 ] 

Hudson CI server commented on MAGNOLIA-3316:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.4-branch 
#28|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/28/]
 

 Support execution of paragraph models before rendering starts
 -

 Key: MAGNOLIA-3316
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3316
 Project: Magnolia
  Issue Type: Improvement
  Components: templating
Reporter: Tobias Mattsson
Assignee: Tobias Mattsson
Priority: Minor
 Fix For: 4.4.x


 Using a special request parameter containing the uuid of a paragraph a filter 
 is triggered that performs execution of the paragraphs model before rendering 
 starts. The model can then decide if it wants to output something else or 
 continue with rendering. If it decides to continue it will be used when the 
 paragraph is rendered (the model is not executed again).

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3185) Upgrade FCKEditor in next major version release

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30404#action_30404
 ] 

Hudson CI server commented on MAGNOLIA-3185:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.4-branch 
#29|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/29/]
 MAGNOLIA-3185: SCAYT is enabled automatically


 Upgrade FCKEditor in next major version release
 ---

 Key: MAGNOLIA-3185
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3185
 Project: Magnolia
  Issue Type: Task
  Components: fckeditor
Affects Versions: 4.3.1
Reporter: Jan Haderka
Assignee: Federico Grilli
 Fix For: 5.0

 Attachments: fck-2.6.6.patch


 2.6.6 is out ... we should consider upgrade.
 http://sourceforge.net/projects/fckeditor/files/FCKeditor/2.6.6/FCKeditor_2.6.6.tar.gz/download

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





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

[magnolia-dev] [JIRA] Commented: (BUILD-45) Fix version of maven-remote-resources-plugin

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/BUILD-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30412#action_30412
 ] 

Hudson CI server commented on BUILD-45:
---

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-build-tools_trunk 
#25|http://hudson.magnolia-cms.com/job/magnolia-build-tools_trunk/25/]
 BUILD-45 fixing maven-remote-resources-plugin version to 1.1


 Fix version of maven-remote-resources-plugin
 

 Key: BUILD-45
 URL: http://jira.magnolia-cms.com/browse/BUILD-45
 Project: Build
  Issue Type: Task
  Components: build-tools, poms
Reporter: Grégory Joseph
Assignee: Grégory Joseph
 Fix For: POMs 18, Build Tools 1.5.6


 to 1.1 for now - just to avoid the 1.2-snapshot being downloaded everywhere.

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





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

[magnolia-dev] [JIRA] Commented: (BUILD-45) Fix version of maven-remote-resources-plugin

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/BUILD-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30413#action_30413
 ] 

Hudson CI server commented on BUILD-45:
---

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-parent-pom 
#58|http://hudson.magnolia-cms.com/job/magnolia-parent-pom/58/]
 BUILD-45 fixing maven-remote-resources-plugin version to 1.1


 Fix version of maven-remote-resources-plugin
 

 Key: BUILD-45
 URL: http://jira.magnolia-cms.com/browse/BUILD-45
 Project: Build
  Issue Type: Task
  Components: build-tools, poms
Reporter: Grégory Joseph
Assignee: Grégory Joseph
 Fix For: POMs 18, Build Tools 1.5.6


 to 1.1 for now - just to avoid the 1.2-snapshot being downloaded everywhere.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3316) Support execution of paragraph models before rendering starts

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30414#action_30414
 ] 

Hudson CI server commented on MAGNOLIA-3316:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.4-branch 
#31|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/31/]
 

 Support execution of paragraph models before rendering starts
 -

 Key: MAGNOLIA-3316
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3316
 Project: Magnolia
  Issue Type: Improvement
  Components: templating
Reporter: Tobias Mattsson
Assignee: Tobias Mattsson
Priority: Minor
 Fix For: 4.4.x


 Using a special request parameter containing the uuid of a paragraph a filter 
 is triggered that performs execution of the paragraphs model before rendering 
 starts. The model can then decide if it wants to output something else or 
 continue with rendering. If it decides to continue it will be used when the 
 paragraph is rendered (the model is not executed again).

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30346#action_30346
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[ee_magnolia-module-enterprise_4.4-branch 
#29|http://hudson.magnolia-cms.com/job/ee_magnolia-module-enterprise_4.4-branch/29/]
 MAGNOLIA-88: made method private instead of protected


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30347#action_30347
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[ee_magnolia-module-enterprise_4.4-branch 
#30|http://hudson.magnolia-cms.com/job/ee_magnolia-module-enterprise_4.4-branch/30/]
 MAGNOLIA-88: error notification not sticky (fades away after 5 secs)


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30355#action_30355
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.4-branch 
#24|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/24/]
 MAGNOLIA-88: renamed class


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MGNLFORM-61) Show a clearer error message for failed noHTML validation

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLFORM-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30356#action_30356
 ] 

Hudson CI server commented on MGNLFORM-61:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-module-form 
#1164|http://hudson.magnolia-cms.com/job/magnolia-module-form/1164/]
 MGNLFORM-61 Add message for noHTML validation


 Show a clearer error message for failed noHTML validation
 ---

 Key: MGNLFORM-61
 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-61
 Project: Magnolia Form Module
  Issue Type: Improvement
Affects Versions: 1.1.4
Reporter: Felix Rabe
Assignee: Teresa Miyar

 The file 
 {{/magnolia-module-form/src/main/resources/info/magnolia/module/form/messages_en.properties}}
  contains no line for the noHTML error message, showing a potentially 
 confusing invalid input instead.  Proposed change:
 {noformat}
  form.user.errorMessage.number = must be a number
 +form.user.errorMessage.noHTML = characters  are not allowed
  form.user.errorMessage.generic= Internal error, form could not be sent
 {noformat}
 I have applied this change locally and it works for me.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30359#action_30359
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[ee_magnolia-module-enterprise_4.4-branch 
#32|http://hudson.magnolia-cms.com/job/ee_magnolia-module-enterprise_4.4-branch/32/]
 MAGNOLIA-88: fixed wrong url
MAGNOLIA-88: check for null modificationDate


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MGNLFORM-61) Show a clearer error message for failed noHTML validation

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLFORM-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30361#action_30361
 ] 

Hudson CI server commented on MGNLFORM-61:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-module-form 
#1165|http://hudson.magnolia-cms.com/job/magnolia-module-form/1165/]
 Add some translations for form validation failure messages (touches 
MGNLFORM-61)

- German validation failure messages, including noHTML
- Czech translation of noHTML failure message


 Show a clearer error message for failed noHTML validation
 ---

 Key: MGNLFORM-61
 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-61
 Project: Magnolia Form Module
  Issue Type: Improvement
Affects Versions: 1.1.4
Reporter: Felix Rabe
Assignee: Teresa Miyar

 The file 
 {{/magnolia-module-form/src/main/resources/info/magnolia/module/form/messages_en.properties}}
  contains no line for the noHTML error message, showing a potentially 
 confusing invalid input instead.  Proposed change:
 {noformat}
  form.user.errorMessage.number = must be a number
 +form.user.errorMessage.noHTML = characters  are not allowed
  form.user.errorMessage.generic= Internal error, form could not be sent
 {noformat}
 I have applied this change locally and it works for me.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30365#action_30365
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[ee_magnolia-module-enterprise_4.4-branch 
#33|http://hudson.magnolia-cms.com/job/ee_magnolia-module-enterprise_4.4-branch/33/]
 MAGNOLIA-88: show a more meaningful error message


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30325#action_30325
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[ee_magnolia-module-enterprise_4.4-branch 
#25|http://hudson.magnolia-cms.com/job/ee_magnolia-module-enterprise_4.4-branch/25/]
 MAGNOLIA-88: use window.onbeforeunload event, window.unload seems not to 
trigger the call to the server in order to unlock the content. Works on FF 3.6 
and Safari 5.0.2. Added comment.


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30339#action_30339
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[ee_magnolia-module-enterprise_4.4-branch 
#27|http://hudson.magnolia-cms.com/job/ee_magnolia-module-enterprise_4.4-branch/27/]
 MAGNOLIA-88: improved error handling: now setting proper status code in 
the http response. Do manipulation on the users array on client side instead of 
server-side.


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3316) Support execution of paragraph models before rendering starts

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30315#action_30315
 ] 

Hudson CI server commented on MAGNOLIA-3316:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-module-form 
#1163|http://hudson.magnolia-cms.com/job/magnolia-module-form/1163/]
 MAGNOLIA-3316 unused imports


 Support execution of paragraph models before rendering starts
 -

 Key: MAGNOLIA-3316
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3316
 Project: Magnolia
  Issue Type: Improvement
  Components: templating
Reporter: Tobias Mattsson
Assignee: Tobias Mattsson
Priority: Minor
 Fix For: 4.4.x


 Using a special request parameter containing the uuid of a paragraph a filter 
 is triggered that performs execution of the paragraphs model before rendering 
 starts. The model can then decide if it wants to output something else or 
 continue with rendering. If it decides to continue it will be used when the 
 paragraph is rendered (the model is not executed again).

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





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

[magnolia-dev] [JIRA] Commented: (MGNLFORM-58) Add support for multi step forms

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLFORM-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30314#action_30314
 ] 

Hudson CI server commented on MGNLFORM-58:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-module-form 
#1163|http://hudson.magnolia-cms.com/job/magnolia-module-form/1163/]
 

 Add support for multi step forms
 

 Key: MGNLFORM-58
 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-58
 Project: Magnolia Form Module
  Issue Type: New Feature
Reporter: Tobias Mattsson
Assignee: Tobias Mattsson

 Add support for multi step forms. Relies in the addition of preexecution in 
 magnolia-core.
 * Each step will be configured on a page of its own so that different steps 
 can be on a page with content specific to that step.
 * The back button must work as expected.
 * Must be able to use the same form in multiple tabs. Tabs should not use 
 each others values.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30318#action_30318
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[ee_magnolia-module-enterprise_4.4-branch 
#21|http://hudson.magnolia-cms.com/job/ee_magnolia-module-enterprise_4.4-branch/21/]
 MAGNOLIA-88: some minor fixes. Also show when another user saves the same 
page. Use jnotify instead of plain js alert.


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30320#action_30320
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.4-branch 
#21|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/21/]
 MAGNOLIA-88: javadoc


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30321#action_30321
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[ee_magnolia-module-enterprise_4.4-branch 
#23|http://hudson.magnolia-cms.com/job/ee_magnolia-module-enterprise_4.4-branch/23/]
 MAGNOLIA-88: javadoc for servlet + fix when calculating path to content in 
js


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30322#action_30322
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[ee_magnolia-module-enterprise_4.4-branch 
#24|http://hudson.magnolia-cms.com/job/ee_magnolia-module-enterprise_4.4-branch/24/]
 MAGNOLIA-88: try to fix failure in 
info.magnolia.eeintegrationtests.EEBasicTest.loginOnAuthorInstanceWithSuperuser 
due to jQuery undefined


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3318) Provide hook for extending functionality of VersionsList

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30264#action_30264
 ] 

Hudson CI server commented on MAGNOLIA-3318:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.4-branch 
#18|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/18/]
 MAGNOLIA-3318 Provide hook for adding diff/compare functionality


 Provide hook for extending functionality of VersionsList
 

 Key: MAGNOLIA-3318
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3318
 Project: Magnolia
  Issue Type: Improvement
  Components: admininterface
Reporter: Jan Haderka
Assignee: Jan Haderka
 Fix For: 4.4.x




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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3261) Concurrent session changes are not visible when repository uses copy-on-read strategy

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30266#action_30266
 ] 

Hudson CI server commented on MAGNOLIA-3261:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.4-branch 
#20|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/20/]
 MAGNOLIA-3261 removed unused imports


 Concurrent session changes are not visible when repository uses copy-on-read 
 strategy
 -

 Key: MAGNOLIA-3261
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3261
 Project: Magnolia
  Issue Type: Bug
  Components: core
Affects Versions: 4.3.5
Reporter: Jan Haderka
Assignee: Jan Haderka
 Fix For: 4.4.x


 There are 2 ways how repo can deal with the sessions.
 * copy-on-read (eg. ModeShape) copies persisted state to transient and 
 further changes will not be visible until refresh.
 * copy-on-write (eg. JackRabbit) copies data from persistent state only when 
 they are to be changed and all other changes are visible without the refresh.
 more on 
 http://www.day.com/specs/jcr/1.0/7.1.3.4_Seeing_Changes_Made_by_Other_Sessions.html
 One possible way to deal with the issue is to force refresh using observer in 
 the repository strategy.

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





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

[magnolia-dev] [JIRA] Commented: (MGNLSCH-17) Update translations

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLSCH-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30269#action_30269
 ] 

Hudson CI server commented on MGNLSCH-17:
-

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-module-scheduler 
#158|http://hudson.magnolia-cms.com/job/magnolia-module-scheduler/158/]
 MGNLSCH-17 i18n - translations updated and synced, integrated 
community-provided changes


 Update translations
 ---

 Key: MGNLSCH-17
 URL: http://jira.magnolia-cms.com/browse/MGNLSCH-17
 Project: Magnolia Scheduler Module
  Issue Type: Task
Reporter: Grégory Joseph
Assignee: Grégory Joseph
 Fix For: 1.4.1


 Our translations are outdated. We started a translation effort - see 
 http://documentation.magnolia-cms.com/contribute/i18n.html - this issue will 
 track effort and updates to translations files!

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





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

[magnolia-dev] [JIRA] Commented: (MGNLRES-26) Update translations

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLRES-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30271#action_30271
 ] 

Hudson CI server commented on MGNLRES-26:
-

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-module-resources 
#859|http://hudson.magnolia-cms.com/job/magnolia-module-resources/859/]
 MGNLRES-26 i18n - translations updated and synced, integrated 
community-provided changes


 Update translations
 ---

 Key: MGNLRES-26
 URL: http://jira.magnolia-cms.com/browse/MGNLRES-26
 Project: Magnolia Resources Module
  Issue Type: Task
Reporter: Grégory Joseph
Assignee: Grégory Joseph
 Fix For: 1.x


 Our translations are outdated. We started a translation effort - see 
 http://documentation.magnolia-cms.com/contribute/i18n.html - this issue will 
 track effort and updates to translations files!

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





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

[magnolia-dev] [JIRA] Commented: (MGNLRSSAGG-37) Update translations

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLRSSAGG-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30272#action_30272
 ] 

Hudson CI server commented on MGNLRSSAGG-37:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-module-rssaggregator 
#118|http://hudson.magnolia-cms.com/job/magnolia-module-rssaggregator/118/]
 MGNLRSSAGG-37 i18n - translations updated and synced, integrated 
community-provided changes


 Update translations
 ---

 Key: MGNLRSSAGG-37
 URL: http://jira.magnolia-cms.com/browse/MGNLRSSAGG-37
 Project: Magnolia RSS Aggregator Module
  Issue Type: Task
Reporter: Grégory Joseph
Assignee: Grégory Joseph
 Fix For: 1.1.3


 Our translations are outdated. We started a translation effort - see 
 http://documentation.magnolia-cms.com/contribute/i18n.html - this issue will 
 track effort and updates to translations files!

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





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

[magnolia-dev] [JIRA] Commented: (MGNLPUR-45) Update translations

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLPUR-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30273#action_30273
 ] 

Hudson CI server commented on MGNLPUR-45:
-

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-module-public-user-registration 
#64|http://hudson.magnolia-cms.com/job/magnolia-module-public-user-registration/64/]
 MGNLPUR-45 i18n - translations updated and synced, integrated 
community-provided changes


 Update translations
 ---

 Key: MGNLPUR-45
 URL: http://jira.magnolia-cms.com/browse/MGNLPUR-45
 Project: Magnolia Public User Registration
  Issue Type: Task
Reporter: Grégory Joseph
Assignee: Grégory Joseph
 Fix For: 1.1.4


 Our translations are outdated. We started a translation effort - see 
 http://documentation.magnolia-cms.com/contribute/i18n.html - this issue will 
 track effort and updates to translations files!

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30280#action_30280
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[ee_magnolia-module-enterprise_4.4-branch 
#19|http://hudson.magnolia-cms.com/job/ee_magnolia-module-enterprise_4.4-branch/19/]
 MAGNOLIA-88: lets save a call to the Set object


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MGNLSTK-642) Update translations

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLSTK-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30294#action_30294
 ] 

Hudson CI server commented on MGNLSTK-642:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[standard-templating-kit 
#2699|http://hudson.magnolia-cms.com/job/standard-templating-kit/2699/]
 MGNLSTK-642 fixed french accents and synch'd empty properties


 Update translations
 ---

 Key: MGNLSTK-642
 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-642
 Project: Magnolia Standard Templating Kit
  Issue Type: Task
Reporter: Grégory Joseph
Assignee: Grégory Joseph
Priority: Blocker
 Fix For: 1.3.x


 Our translations are outdated. We started a translation effort - see 
 http://documentation.magnolia-cms.com/contribute/i18n.html - this issue will 
 track effort and updates to translations files!

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





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

[magnolia-dev] [JIRA] Commented: (MGNLSTK-642) Update translations

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLSTK-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30295#action_30295
 ] 

Hudson CI server commented on MGNLSTK-642:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[standard-templating-kit 
#2700|http://hudson.magnolia-cms.com/job/standard-templating-kit/2700/]
 MGNLSTK-642 german translations for stk


 Update translations
 ---

 Key: MGNLSTK-642
 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-642
 Project: Magnolia Standard Templating Kit
  Issue Type: Task
Reporter: Grégory Joseph
Assignee: Grégory Joseph
Priority: Blocker
 Fix For: 1.3.x


 Our translations are outdated. We started a translation effort - see 
 http://documentation.magnolia-cms.com/contribute/i18n.html - this issue will 
 track effort and updates to translations files!

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30296#action_30296
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[ee_magnolia-module-enterprise_4.4-branch 
#20|http://hudson.magnolia-cms.com/job/ee_magnolia-module-enterprise_4.4-branch/20/]
 MAGNOLIA-88: renamed operation release as unlock for consistency reasons. 
Introduced jquery periodical updater + our own client side logic.


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (BLOSSOM-18) BlossomMultipartRequestWrapper doesn't work with Spring 3.

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/BLOSSOM-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30220#action_30220
 ] 

Hudson CI server commented on BLOSSOM-18:
-

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! [blossom 
#34|http://hudson.magnolia-cms.com/job/blossom/34/]
 BLOSSOM-18 multipart support for spring 3+


 BlossomMultipartRequestWrapper doesn't work with Spring 3.
 --

 Key: BLOSSOM-18
 URL: http://jira.magnolia-cms.com/browse/BLOSSOM-18
 Project: Magnolia Blossom Module
  Issue Type: Bug
Affects Versions: 1.1.1
Reporter: Danilo Ghirardelli
Assignee: Tobias Mattsson
 Fix For: 1.1.2

 Attachments: reflectionPatch.patch


 BlossomMultipartRequestWrapper estends AbstractMultipartHttpServletRequest. 
 In Spring 2.5.x, AbstractMultipartHttpServletRequest.setMultipartFiles has a 
 parameter of type Map, but in Sping 3.0.x the parameter has been narrowed to 
 type MultiValueMap, which is an extension of Map included in spring-core 3 
 (and unfortunately not included in spring 2.5).
 Current BlossomMultipartRequestWrapper is passing a Map to the 
 setMultipartFiles, and using Spring 3 this will cause an exception.
 Before writing a reflection nightmare to populate the right parameter, is 
 there any other way to get around this? Maybe two different 
 BlossomMultipartRequestWrapper compiled for specific spring versions?
 I honestly can't see a simple solution to overcome the problem, even 
 upgrading the dependency to spring version would make it incompatible with 
 older spring, unless MultiValueMap is copied and included in blossom release 
 (which doesn't seem a good idea).

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





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

[magnolia-dev] [JIRA] Commented: (MGNLDMS-187) Update translations

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLDMS-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30221#action_30221
 ] 

Hudson CI server commented on MGNLDMS-187:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-module-dms 
#495|http://hudson.magnolia-cms.com/job/magnolia-module-dms/495/]
 

 Update translations
 ---

 Key: MGNLDMS-187
 URL: http://jira.magnolia-cms.com/browse/MGNLDMS-187
 Project: Magnolia DMS Module
  Issue Type: Task
Reporter: Grégory Joseph
Assignee: Grégory Joseph
 Fix For: 1.x


 Our translations are outdated. We started a translation effort - see 
 http://documentation.magnolia-cms.com/contribute/i18n.html - this issue will 
 track effort and updates to translations files!

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





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

[magnolia-dev] [JIRA] Commented: (MGNLDMS-192) javadoc: satisfy new checkstyle rules: class level comment, ..

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLDMS-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30222#action_30222
 ] 

Hudson CI server commented on MGNLDMS-192:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-module-dms 
#495|http://hudson.magnolia-cms.com/job/magnolia-module-dms/495/]
 * update to parent pom 17
* MGNLDMS-192 javadoc


 javadoc: satisfy new checkstyle rules: class level comment, ..
 --

 Key: MGNLDMS-192
 URL: http://jira.magnolia-cms.com/browse/MGNLDMS-192
 Project: Magnolia DMS Module
  Issue Type: Task
Reporter: Philipp Bärfuss
Assignee: Boris Kraft
 Fix For: 1.x


 Since BUILD-34 we have new checkstyle rules to satisfy. Once done we can 
 remove:
 {code}
   plugin
 !-- TODO this is temporary ! Don't loaf around and go fix some 
 Javadoc !! --
 artifactIdmaven-checkstyle-plugin/artifactId
 configuration
   failOnViolationfalse/failOnViolation
 /configuration
   /plugin
 {code}
 in the main pom.

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





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

[magnolia-dev] [JIRA] Commented: (MGNLSTK-684) NullPointerException from CategoryOverviewModel.getPager() when category does not exist

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLSTK-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30226#action_30226
 ] 

Hudson CI server commented on MGNLSTK-684:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[ee_magnolia-module-categorization 
#466|http://hudson.magnolia-cms.com/job/ee_magnolia-module-categorization/466/]
 

 NullPointerException from CategoryOverviewModel.getPager() when category does 
 not exist
 ---

 Key: MGNLSTK-684
 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-684
 Project: Magnolia Standard Templating Kit
  Issue Type: Bug
  Components: base system
Affects Versions: 1.3.4
Reporter: Bert Leunis
Assignee: Ondřej Chytil
 Fix For: 1.3.x

 Attachments: magnolia-module-categorization.patch


 When a category does not exist, a NullPointerException is thrown. See for 
 example: 
 http://demoauthor.magnolia-cms.com/demo-project/service/category.Family-blabla.html.
 The CategoryOverviewModel.getPager() uses 
 info.magnolia.module.categorization.util.CategoryUtil.getContentByCategory(CategoryUtil.java:73),
  where the null pointer happens.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30225#action_30225
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.4-branch 
#11|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/11/]
 MAGNOLIA-88: added soft locking support. As this is an EE feature only, 
the implementation for CE is just an empty one. The RenderingFilter now checks 
whether we're in preview mode or not. In the latter case, the content is 
locked, whereas in preview mode it is unlocked.


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MGNLSTK-671) Singleton Template Definitiona (feature pages): Contain relative include of mainArea.ftl which doesn't work if using a custom main.ftl

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLSTK-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30227#action_30227
 ] 

Hudson CI server commented on MGNLSTK-671:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[ee_magnolia-module-categorization 
#466|http://hudson.magnolia-cms.com/job/ee_magnolia-module-categorization/466/]
 

 Singleton Template Definitiona (feature pages): Contain relative include of 
 mainArea.ftl which doesn't work if using a custom main.ftl
 --

 Key: MGNLSTK-671
 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-671
 Project: Magnolia Standard Templating Kit
  Issue Type: Bug
  Components: templates
Affects Versions: 1.3.4
Reporter: Christian Ringele
Assignee: Ondřej Chytil
 Fix For: 1.3.x

 Attachments: Screen shot 2010-08-02 at 12.18.48 PM.png


 Relative includes of sub templates/sub snippets don't work, if you use a 
 main.ftl located in a different location/module.
 The relative include is the executed on the new location (relative to the new 
 main.ftl).
 We had the same problem with all Section templates and removed the relative 
 pathes from the Section templates.
 The the singleton paragraph templates still contain these relative includes, 
 see print screen.
 Best would be to check all template definitions (and all ftl's for include of 
 macros) if there are still any relative includes left.
 All includes, no matter where, should be absolute paths.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30228#action_30228
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[ee_magnolia-module-enterprise_4.4-branch 
#10|http://hudson.magnolia-cms.com/job/ee_magnolia-module-enterprise_4.4-branch/10/]
 MAGNOLIA-88: added soft locking support. The RenderingFilter now checks 
whether we're in preview mode or not. In the latter case, the content is 
locked, whereas in preview mode it is unlocked. Added dep on templating 
module and set javaVersion prop in pom.xml as 1.5.


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3278) javadoc: satisfy new checkstyle rules: class level comment, ..

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30235#action_30235
 ] 

Hudson CI server commented on MAGNOLIA-3278:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-trunk 
#2057|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/2057/]
 MAGNOLIA-3278: backport and some additional fixes like unused imports
- r36503
- r36506
- r36511
- r36512
- r36513
- r36516
- r36517
- r36518
- r36519
- r36522
- r36535
- r36547
- r36881
- r36882
- r36890
- r36896
- r36903
- r36919
- r36935
- r36936
- r36937
- r36939
- r36942
- r36944
- r37516
- r37520
- r37524
- r37526
- r37527
- r37528
- r37529
- r37530
- r37531
- r37622
- r37623


 javadoc: satisfy new checkstyle rules: class level comment, ..
 --

 Key: MAGNOLIA-3278
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3278
 Project: Magnolia
  Issue Type: Task
Reporter: Philipp Bärfuss
Assignee: Boris Kraft
 Fix For: 4.3.x, 4.4.x, 5.0


 Since BUILD-34 we have new checkstyle rules to satisfy. Once done we can 
 remove:
 {code}
   plugin
 !-- TODO this is temporary ! Don't loaf around and go fix some 
 Javadoc !! --
 artifactIdmaven-checkstyle-plugin/artifactId
 configuration
   failOnViolationfalse/failOnViolation
 /configuration
   /plugin
 {code}
 in the main pom.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3278) javadoc: satisfy new checkstyle rules: class level comment, ..

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30236#action_30236
 ] 

Hudson CI server commented on MAGNOLIA-3278:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.4-branch 
#13|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/13/]
 MAGNOLIA-3278: remove the merge script itself


 javadoc: satisfy new checkstyle rules: class level comment, ..
 --

 Key: MAGNOLIA-3278
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3278
 Project: Magnolia
  Issue Type: Task
Reporter: Philipp Bärfuss
Assignee: Boris Kraft
 Fix For: 4.3.x, 4.4.x, 5.0


 Since BUILD-34 we have new checkstyle rules to satisfy. Once done we can 
 remove:
 {code}
   plugin
 !-- TODO this is temporary ! Don't loaf around and go fix some 
 Javadoc !! --
 artifactIdmaven-checkstyle-plugin/artifactId
 configuration
   failOnViolationfalse/failOnViolation
 /configuration
   /plugin
 {code}
 in the main pom.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3294) Dialogs: labels missing

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30237#action_30237
 ] 

Hudson CI server commented on MAGNOLIA-3294:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.4-branch 
#14|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/14/]
 MAGNOLIA-3294: merged r37539


 Dialogs: labels missing
 ---

 Key: MAGNOLIA-3294
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3294
 Project: Magnolia
  Issue Type: Improvement
  Components: gui
Reporter: Ondřej Chytil
Assignee: Ondřej Chytil
Priority: Minor
 Fix For: 4.3.7, 5.0




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





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

[magnolia-dev] [JIRA] Commented: (BUILD-35) Switch to Nexus

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/BUILD-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30244#action_30244
 ] 

Hudson CI server commented on BUILD-35:
---

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-trunk 
#2059|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/2059/]
 merge with 4.4:

r37626 | gjoseph | 2010-10-01 19:45:32 +0200 (Fr, 01 Okt 2010) | 1 line

added missing newline

r37646 | gjoseph | 2010-10-04 14:04:31 +0200 (Mo, 04 Okt 2010) | 2 lines

BUILD-35 not deploying site in /${artifactId}/ subdirectory for main project


r37685 | dlipp | 2010-10-05 14:20:34 +0200 (Di, 05 Okt 2010) | 1 line

fixed typos

r37697 | dlipp | 2010-10-06 11:05:23 +0200 (Mi, 06 Okt 2010) | 1 line

completed javadoc

r37731 | fgrilli | 2010-10-07 12:41:19 +0200 (Do, 07 Okt 2010) | 1 line

MAGNOLIA-3313: added methods for setting and getting multivalue properties. 
Added 'multiple' properties to MetaData nodetype definition

r37736 | fgrilli | 2010-10-07 12:57:49 +0200 (Do, 07 Okt 2010) | 1 line

MAGNOLIA-88: added soft locking support. As this is an EE feature only, the 
implementation for CE is just an empty one. The RenderingFilter now checks 
whether we're in preview mode or not. In the latter case, the content is 
locked, whereas in preview mode it is unlocked. 

r37746 | fgrilli | 2010-10-07 14:58:08 +0200 (Do, 07 Okt 2010) | 1 line

added missing javadoc

r37747 | fgrilli | 2010-10-07 14:58:39 +0200 (Do, 07 Okt 2010) | 1 line

typo


 Switch to Nexus
 ---

 Key: BUILD-35
 URL: http://jira.magnolia-cms.com/browse/BUILD-35
 Project: Build
  Issue Type: Task
  Components: poms
Reporter: Grégory Joseph
Assignee: Grégory Joseph
 Fix For: POMs 16


 We will
 * provide a nexus instance, mirroring external repositories as well as our own
 * remove repository references from the parent pom, instead relying on maven 
 settings.
 * provide user instructions, based on different profiles (Magnolia Intl 
 developer, Community user/developer, Enterprise user/developer)

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30246#action_30246
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-trunk 
#2059|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/2059/]
 merge with 4.4:

r37626 | gjoseph | 2010-10-01 19:45:32 +0200 (Fr, 01 Okt 2010) | 1 line

added missing newline

r37646 | gjoseph | 2010-10-04 14:04:31 +0200 (Mo, 04 Okt 2010) | 2 lines

BUILD-35 not deploying site in /${artifactId}/ subdirectory for main project


r37685 | dlipp | 2010-10-05 14:20:34 +0200 (Di, 05 Okt 2010) | 1 line

fixed typos

r37697 | dlipp | 2010-10-06 11:05:23 +0200 (Mi, 06 Okt 2010) | 1 line

completed javadoc

r37731 | fgrilli | 2010-10-07 12:41:19 +0200 (Do, 07 Okt 2010) | 1 line

MAGNOLIA-3313: added methods for setting and getting multivalue properties. 
Added 'multiple' properties to MetaData nodetype definition

r37736 | fgrilli | 2010-10-07 12:57:49 +0200 (Do, 07 Okt 2010) | 1 line

MAGNOLIA-88: added soft locking support. As this is an EE feature only, the 
implementation for CE is just an empty one. The RenderingFilter now checks 
whether we're in preview mode or not. In the latter case, the content is 
locked, whereas in preview mode it is unlocked. 

r37746 | fgrilli | 2010-10-07 14:58:08 +0200 (Do, 07 Okt 2010) | 1 line

added missing javadoc

r37747 | fgrilli | 2010-10-07 14:58:39 +0200 (Do, 07 Okt 2010) | 1 line

typo


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3313) Add multivalue property support to metadata

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30245#action_30245
 ] 

Hudson CI server commented on MAGNOLIA-3313:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-trunk 
#2059|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/2059/]
 merge with 4.4:

r37626 | gjoseph | 2010-10-01 19:45:32 +0200 (Fr, 01 Okt 2010) | 1 line

added missing newline

r37646 | gjoseph | 2010-10-04 14:04:31 +0200 (Mo, 04 Okt 2010) | 2 lines

BUILD-35 not deploying site in /${artifactId}/ subdirectory for main project


r37685 | dlipp | 2010-10-05 14:20:34 +0200 (Di, 05 Okt 2010) | 1 line

fixed typos

r37697 | dlipp | 2010-10-06 11:05:23 +0200 (Mi, 06 Okt 2010) | 1 line

completed javadoc

r37731 | fgrilli | 2010-10-07 12:41:19 +0200 (Do, 07 Okt 2010) | 1 line

MAGNOLIA-3313: added methods for setting and getting multivalue properties. 
Added 'multiple' properties to MetaData nodetype definition

r37736 | fgrilli | 2010-10-07 12:57:49 +0200 (Do, 07 Okt 2010) | 1 line

MAGNOLIA-88: added soft locking support. As this is an EE feature only, the 
implementation for CE is just an empty one. The RenderingFilter now checks 
whether we're in preview mode or not. In the latter case, the content is 
locked, whereas in preview mode it is unlocked. 

r37746 | fgrilli | 2010-10-07 14:58:08 +0200 (Do, 07 Okt 2010) | 1 line

added missing javadoc

r37747 | fgrilli | 2010-10-07 14:58:39 +0200 (Do, 07 Okt 2010) | 1 line

typo


 Add multivalue property support to metadata
 ---

 Key: MAGNOLIA-3313
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3313
 Project: Magnolia
  Issue Type: Task
  Components: core
Reporter: Federico Grilli
Assignee: Federico Grilli
 Fix For: 4.4.x


 The need for adding multivalue properties to metadata arose as we want to 
 store a list of users concurrently editing a certain content. This involves 
 changing the node type defintion for MetaData and allow for {{multiple}} 
 properties.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3229) Use new office address in Magnolia Login Form

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30248#action_30248
 ] 

Hudson CI server commented on MAGNOLIA-3229:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.3-branch 
#99|http://hudson.magnolia-cms.com/job/magnolia_main-4.3-branch/99/]
 MAGNOLIA-3229: backport of r35111


 Use new office address in Magnolia Login Form
 -

 Key: MAGNOLIA-3229
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3229
 Project: Magnolia
  Issue Type: Bug
Affects Versions: 4.3.2
Reporter: Zdenek Skodik
Assignee: Zdenek Skodik
 Fix For: 4.2.x, 4.1.x, 4.3.3, 5.0, 4.0.x


 [here|http://svn.magnolia-cms.com/svn/community/magnolia/trunk/magnolia-module-admininterface/src/main/resources/mgnl-resources/loginForm/login.html].
  Current year would be also taken into account for the copyright years.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3229) Use new office address in Magnolia Login Form

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30249#action_30249
 ] 

Hudson CI server commented on MAGNOLIA-3229:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.4-branch 
#16|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/16/]
 MAGNOLIA-3229: backport of r35111


 Use new office address in Magnolia Login Form
 -

 Key: MAGNOLIA-3229
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3229
 Project: Magnolia
  Issue Type: Bug
Affects Versions: 4.3.2
Reporter: Zdenek Skodik
Assignee: Zdenek Skodik
 Fix For: 4.2.x, 4.1.x, 4.3.3, 5.0, 4.0.x


 [here|http://svn.magnolia-cms.com/svn/community/magnolia/trunk/magnolia-module-admininterface/src/main/resources/mgnl-resources/loginForm/login.html].
  Current year would be also taken into account for the copyright years.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30250#action_30250
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.4-branch 
#17|http://hudson.magnolia-cms.com/job/magnolia_main-4.4-branch/17/]
 MAGNOLIA-88: removed dummy code leftover


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-88) locking of Pages while editing from one page

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30252#action_30252
 ] 

Hudson CI server commented on MAGNOLIA-88:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[ee_magnolia-module-enterprise_4.4-branch 
#15|http://hudson.magnolia-cms.com/job/ee_magnolia-module-enterprise_4.4-branch/15/]
 MAGNOLIA-88: add author who last modified page and last mod date.


 locking of Pages while editing from one page
 

 Key: MAGNOLIA-88
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-88
 Project: Magnolia
  Issue Type: New Feature
  Components: admininterface, core, templating
Reporter: Boris Kraft
Assignee: Federico Grilli
 Fix For: 4.4.x


 the system should provide the feature that if one person edits a page he or 
 she can see a warning about other users concurrently editing the same page, 
 the so-called soft locking as opposed to hard-locking where two users are 
 not allowed to edit the same page at the same time.

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





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

[magnolia-dev] [JIRA] Commented: (MGNLXLS-17) Update translations

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLXLS-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30251#action_30251
 ] 

Hudson CI server commented on MGNLXLS-17:
-

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-module-excelrenderer 
#5|http://hudson.magnolia-cms.com/job/magnolia-module-excelrenderer/5/]
 MGNLXLS-17 i18n - translations updated and synced, integrated 
community-provided changes\!


 Update translations
 ---

 Key: MGNLXLS-17
 URL: http://jira.magnolia-cms.com/browse/MGNLXLS-17
 Project: Magnolia Excel Renderer Module
  Issue Type: Task
Reporter: Grégory Joseph
Assignee: Grégory Joseph
 Fix For: 1.0


 Our translations are outdated. We started a translation effort - see 
 http://documentation.magnolia-cms.com/contribute/i18n.html - this issue will 
 track effort and updates to translations files!

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





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

[magnolia-dev] [JIRA] Commented: (MGNLDATA-101) Update translations

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLDATA-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30253#action_30253
 ] 

Hudson CI server commented on MGNLDATA-101:
---

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-module-data 
#523|http://hudson.magnolia-cms.com/job/magnolia-module-data/523/]
 MGNLDATA-101 i18n - translations updated and synced, integrated 
community-provided changes\!


 Update translations
 ---

 Key: MGNLDATA-101
 URL: http://jira.magnolia-cms.com/browse/MGNLDATA-101
 Project: Magnolia Data Module
  Issue Type: Task
Reporter: Grégory Joseph
Assignee: Grégory Joseph
Priority: Blocker
 Fix For: 1.5.1


 Our translations are outdated. We started a translation effort - see 
 http://documentation.magnolia-cms.com/contribute/i18n.html - this issue will 
 track effort and updates to translations files!

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





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

[magnolia-dev] [JIRA] Commented: (MGNLSTK-642) Update translations

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLSTK-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30254#action_30254
 ] 

Hudson CI server commented on MGNLSTK-642:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[standard-templating-kit 
#2698|http://hudson.magnolia-cms.com/job/standard-templating-kit/2698/]
 MGNLSTK-642 i18n - translations updated and synced, integrated 
community-provided changes


 Update translations
 ---

 Key: MGNLSTK-642
 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-642
 Project: Magnolia Standard Templating Kit
  Issue Type: Task
Reporter: Grégory Joseph
Assignee: Grégory Joseph
Priority: Blocker
 Fix For: 1.3.x


 Our translations are outdated. We started a translation effort - see 
 http://documentation.magnolia-cms.com/contribute/i18n.html - this issue will 
 track effort and updates to translations files!

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





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

[magnolia-dev] [JIRA] Commented: (MGNLINTEMPL-16) Update translations

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLINTEMPL-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30256#action_30256
 ] 

Hudson CI server commented on MGNLINTEMPL-16:
-

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-module-inplace-templating 
#825|http://hudson.magnolia-cms.com/job/magnolia-module-inplace-templating/825/]
 MGNLINTEMPL-16 i18n - translations updated and synced, integrated 
community-provided changes


 Update translations
 ---

 Key: MGNLINTEMPL-16
 URL: http://jira.magnolia-cms.com/browse/MGNLINTEMPL-16
 Project: Magnolia In-place templating Module
  Issue Type: Task
Reporter: Grégory Joseph
Assignee: Grégory Joseph
 Fix For: 1.2.x


 Our translations are outdated. We started a translation effort - see 
 http://documentation.magnolia-cms.com/contribute/i18n.html - this issue will 
 track effort and updates to translations files!

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





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

[magnolia-dev] [JIRA] Commented: (MGNLFORM-60) Update translations

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLFORM-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30257#action_30257
 ] 

Hudson CI server commented on MGNLFORM-60:
--

Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-module-form 
#1161|http://hudson.magnolia-cms.com/job/magnolia-module-form/1161/]
 MGNLFORM-60 i18n - translations updated and synced, integrated 
community-provided changes


 Update translations
 ---

 Key: MGNLFORM-60
 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-60
 Project: Magnolia Form Module
  Issue Type: Task
Reporter: Grégory Joseph
Assignee: Grégory Joseph
 Fix For: 1.1.4


 Our translations are outdated. We started a translation effort - see 
 http://documentation.magnolia-cms.com/contribute/i18n.html - this issue will 
 track effort and updates to translations files!

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





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

[magnolia-dev] [JIRA] Commented: (MGNLGROOVY-31) Update translations

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MGNLGROOVY-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30258#action_30258
 ] 

Hudson CI server commented on MGNLGROOVY-31:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia-module-groovy 
#371|http://hudson.magnolia-cms.com/job/magnolia-module-groovy/371/]
 MGNLGROOVY-31 i18n - translations updated and synced, integrated 
community-provided changes


 Update translations
 ---

 Key: MGNLGROOVY-31
 URL: http://jira.magnolia-cms.com/browse/MGNLGROOVY-31
 Project: Magnolia Groovy Module
  Issue Type: Task
Reporter: Grégory Joseph
Assignee: Grégory Joseph
 Fix For: 1.1.1


 Our translations are outdated. We started a translation effort - see 
 http://documentation.magnolia-cms.com/contribute/i18n.html - this issue will 
 track effort and updates to translations files!

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





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

[magnolia-dev] [JIRA] Commented: (MAGNOLIA-3311) Create log error handler

[JIRA (on behalf of Hudson CI server)]

[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=30193#action_30193
 ] 

Hudson CI server commented on MAGNOLIA-3311:


Integrated in !http://hudson.magnolia-cms.com/images/16x16/blue.gif! 
[magnolia_main-4.3-branch 
#97|http://hudson.magnolia-cms.com/job/magnolia_main-4.3-branch/97/]
 MAGNOLIA-3311
LogErrorHandler class added.


 Create log error handler
 

 Key: MAGNOLIA-3311
 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3311
 Project: Magnolia
  Issue Type: Improvement
  Components: core
Reporter: Ondřej Chytil
Assignee: Ondřej Chytil
Priority: Minor
 Fix For: 4.3.x


 Error handler which simply logs warnings messages into stacktrace.

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





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