[magnolia-dev] [JIRA] (MGNLMIGRATION-249) Fix integration tests of migration

2013-08-21 Thread on behalf of Robert Šiška














































Robert Šiška
 updated  MGNLMIGRATION-249


Fix integration tests of migration
















Change By:


Robert Šiška
(21/Aug/13 8:49 AM)




Fix Version/s:


1.2.5





Fix Version/s:


1.2.x



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MGNLSTK-1076) The content of Demo-project between a new instance and a migrated instance must be the same

2013-08-21 Thread on behalf of Robert Šiška














































Robert Šiška
 updated  MGNLSTK-1076


The content of Demo-project between a new instance and a migrated instance must be the same
















Change By:


Robert Šiška
(21/Aug/13 8:50 AM)




Fix Version/s:


2.0.12





Fix Version/s:


2.0.x



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MGNLSTK-1225) Prevent NPEs at PageSyndicator

2013-08-21 Thread JIRA (on behalf of Milan Divilek)














































Milan Divilek
 reopened  MGNLSTK-1225


Prevent NPEs at PageSyndicator
















Reopen: Same reason as in MGNLCAT-89 (see http://jira.magnolia-cms.com/browse/MGNLCAT-89?focusedCommentId=68726page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-68726)





Change By:


Milan Divilek
(21/Aug/13 9:05 AM)




Resolution:


Fixed





Status:


Closed
Reopened



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MAGNOLIA-4752) Add support for non referencable subnodes during versioning/activation

2013-08-21 Thread JIRA (on behalf of Jan Haderka)














































Jan Haderka
 updated  MAGNOLIA-4752


Add support for non referencable subnodes during versioning/activation
















Change By:


Jan Haderka
(21/Aug/13 9:03 AM)




Fix Version/s:


4.5.x





Fix Version/s:


4.5.11



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MAGNOLIA-5249) Diabled activation in JCR Browser for website workspace

2013-08-21 Thread JIRA (on behalf of Frank Sommer)














































Frank Sommer
 created  MAGNOLIA-5249


Diabled activation in JCR Browser for website workspace















Issue Type:


Bug



Affects Versions:


4.5.10



Assignee:


Unassigned


Components:


admininterface



Created:


21/Aug/13 9:10 AM



Description:


The change of MAGNOLIA-5057 has impacts at the behaviour of the website jcr browser in the tools menu. An activation on the first two levels is not possible.




Project:


Magnolia



Priority:


Neutral




Reporter:


Frank Sommer



Security Level:


Public 




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MSHOP-83) Sample shop bootstrapped twice on update because of changed uuid

2013-08-21 Thread on behalf of Robert Šiška














































Robert Šiška
 created  MSHOP-83


Sample shop bootstrapped twice on update because of changed uuid















Issue Type:


Bug



Assignee:


Robert Šiška



Created:


21/Aug/13 9:25 AM



Description:


Change uuid of shop page back.




Fix Versions:


1.1.4



Project:


Magnolia Shop



Priority:


Neutral




Reporter:


Robert Šiška




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MGNLIMG-111) Imaging should provide BoundedResizeNoUpscale

2013-08-21 Thread JIRA (on behalf of Jan Haderka)














































Jan Haderka
 updated  MGNLIMG-111


Imaging should provide BoundedResizeNoUpscale
















UI is depending on imaging 3.x





Change By:


Jan Haderka
(21/Aug/13 10:01 AM)




Fix Version/s:


3.0.2





Fix Version/s:


2.2.4



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MGNLBLOG-12) Bootstrap new sample blog on update

2013-08-21 Thread on behalf of Robert Šiška














































Robert Šiška
 created  MGNLBLOG-12


Bootstrap new sample blog on update















Issue Type:


Improvement



Assignee:


Robert Šiška



Created:


21/Aug/13 10:07 AM



Fix Versions:


2.0



Project:


Magnolia Blog Module



Priority:


Neutral




Reporter:


Robert Šiška




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MAGNOLIA-5239) Handling of autogeneratedComponents doesn't depend on order in template definitions

2013-08-21 Thread JIRA (on behalf of Jan Haderka)














































Jan Haderka
 updated  MAGNOLIA-5239


Handling of autogeneratedComponents doesnt depend on order in template definitions
















Change By:


Jan Haderka
(21/Aug/13 10:12 AM)




Description:


Stepstoreproduce:-
LetshavethisstructureofautogeneratedComponents
{noformat}
-autoGeneration--conent---firstcomponent---secondcomponent---thirdcomponent
{noformat}

-
Thenvisitthepagewhereautogeneratedcomponentsarelocated
.Remove
andremove
thefirstcomponent.
The
-Previouslyremoved
componentisautomaticallycreatedandisordered
on
as
last
place
.
Butwhenyouremove
-Remove
secondcomponent
again
thenthecomponentisnotautomaticallycreatedagain.Similarlywhenyouaddnewcomponentintoautogeneratedcomponentsintemplatedefinitions-thenifyouplacethiscomponentonfirstplacethenthiscomponentisgeneratedduringfirstvisitofpage,butwhenyouaddthiscomponentondifferentplacethenthecomponentisnotautomaticallygenerated.Theproblematiccodeisinfo.magnolia.rendering.generator.CopyGenerator.createNode(Node,MapString,Object){code}if(parentNode!=nullparentNode.hasNode(name)){log.debug(path{}wasalreadyfoundinrepository.Noneedtocreateit.,parentNode.getPath()+/+name);break;}{code}itchecksifthecomponentnodeexistsifyesthenitbreakforloopsonoothercomponentsareprocessed.Ifwechangebreaktocontinuethenallcomponentwillbeprocess,butthisbreakthefunctionalityofremovecomponentfromthepage.Differentquestionisifwewantallowremovingautogeneratedcomponents?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MAGNOLIA-5239) Handling of autogeneratedComponents doesn't depend on order in template definitions

2013-08-21 Thread JIRA (on behalf of Jan Haderka)














































Jan Haderka
 updated  MAGNOLIA-5239


Handling of autogeneratedComponents doesnt depend on order in template definitions
















Change By:


Jan Haderka
(21/Aug/13 10:09 AM)




Summary:


Differenthandlingwith
Handlingof
autogeneratedComponents
depending
doesntdepend
onorderintemplatedefinitions



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MGNLSTK-1226) Installation of Demo Project leads to ItemExistsException

2013-08-21 Thread JIRA (on behalf of Jan Haderka)














































Jan Haderka
 updated  MGNLSTK-1226


Installation of Demo Project leads to ItemExistsException
















Change By:


Jan Haderka
(21/Aug/13 10:32 AM)




Fix Version/s:


2.0.12



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MGNLSTK-1226) Installation of Demo Project leads to ItemExistsException

2013-08-21 Thread JIRA (on behalf of Jan Haderka)














































Jan Haderka
 updated  MGNLSTK-1226


Installation of Demo Project leads to ItemExistsException
















Change By:


Jan Haderka
(21/Aug/13 10:33 AM)




Priority:


Major
Critical



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MAGNOLIA-5248) Memory-Leak/Classloader errors because BouncyCastleProvider is registrated for all WARs

2013-08-21 Thread JIRA (on behalf of Jan Haderka)














































Jan Haderka
 updated  MAGNOLIA-5248


Memory-Leak/Classloader errors because BouncyCastleProvider is registrated for all WARs
















Change By:


Jan Haderka
(21/Aug/13 10:35 AM)




Fix Version/s:


5.0.4





Fix Version/s:


5.1



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MGNLCACHE-15) CLONE - GZIP response when threshold for in-memory caching is reached

2013-08-21 Thread JIRA (on behalf of Milan Divilek)














































Milan Divilek
 updated  MGNLCACHE-15


CLONE - GZIP response when threshold for in-memory caching is reached
















Change By:


Milan Divilek
(21/Aug/13 11:17 AM)




Fix Version/s:


5.0.2





Fix Version/s:


5.1



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MAGNOLIA-5247) CommandsManager never resets context after executing commands

2013-08-21 Thread JIRA (on behalf of Espen Jervidalo)














































Espen Jervidalo
 deleted  MAGNOLIA-5247


CommandsManager never resets context after executing commands
























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MAGNOLIA-5239) Handling of autogeneratedComponents doesn't depend on order in template definitions

2013-08-21 Thread JIRA (on behalf of Milan Divilek)














































Milan Divilek
 updated  MAGNOLIA-5239


Handling of autogeneratedComponents doesnt depend on order in template definitions
















Change By:


Milan Divilek
(21/Aug/13 1:31 PM)




Description:


Stepstoreproduce:-LetshavethisstructureofautogeneratedComponents{noformat}-autoGeneration--conent---firstcomponent---secondcomponent---thirdcomponent{noformat}-Thenvisitthepagewhereautogeneratedcomponentsarelocatedandremovethefirstcomponent.-Previouslyremovedcomponentisautomaticallycreatedandisorderedaslast.-Removesecondcomponent
again
thenthecomponentisnotautomaticallycreatedagain.Similarlywhenyouaddnewcomponentintoautogeneratedcomponentsintemplatedefinitions-thenifyouplacethiscomponentonfirstplacethenthiscomponentisgeneratedduringfirstvisitofpage,butwhenyouaddthiscomponentondifferentplacethenthecomponentisnotautomaticallygenerated.Theproblematiccodeisinfo.magnolia.rendering.generator.CopyGenerator.createNode(Node,MapString,Object){code}if(parentNode!=nullparentNode.hasNode(name)){log.debug(path{}wasalreadyfoundinrepository.Noneedtocreateit.,parentNode.getPath()+/+name);break;}{code}itchecksifthecomponentnodeexistsifyesthenitbreakforloopsonoothercomponentsareprocessed.Ifwechangebreaktocontinuethenallcomponentwillbeprocess,butthisbreakthefunctionalityofremovecomponentfromthepage.Differentquestionisifwewantallowremovingautogeneratedcomponents?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MAGNOLIA-5012) Add possibility into AuditLogging to monitor only specific workspace

2013-08-21 Thread JIRA (on behalf of Jan Haderka)














































Jan Haderka
 updated  MAGNOLIA-5012


Add possibility into AuditLogging to monitor only specific workspace
















Change By:


Jan Haderka
(21/Aug/13 2:07 PM)




Fix Version/s:


5.1





Fix Version/s:


4.5.11



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MAGNOLIA-5215) CLONE - URL's with multiple times a parameter with the same name cause cache collisions.

2013-08-21 Thread JIRA (on behalf of Jan Haderka)














































Jan Haderka
 updated  MAGNOLIA-5215


CLONE - URLs with multiple times a parameter with the same name cause cache collisions.
















Change By:


Jan Haderka
(21/Aug/13 2:05 PM)




Priority:


Major
Critical



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MGNLSTK-1227) Drop stkFooter component

2013-08-21 Thread on behalf of Robert Šiška














































Robert Šiška
 created  MGNLSTK-1227


Drop stkFooter component















Issue Type:


Improvement



Assignee:


Robert Šiška



Created:


21/Aug/13 2:07 PM



Description:


The stkFooter component was deprecated in MGNLSTK-918, but its templating definition wasn't removed. The template script was removed though, leaving the component non-functional.

Interestingly, /demo-project/footer and /demo-features/footer were referencing it, but footer area was used for rendering anyway.




Project:


Magnolia Standard Templating Kit



Priority:


Neutral




Reporter:


Robert Šiška



Security Level:


Public 




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MAGNOLIA-5250) fckEditor: make repository browser site aware

2013-08-21 Thread JIRA (on behalf of Jan Haderka)














































Jan Haderka
 updated  MAGNOLIA-5250


fckEditor: make repository browser site aware
















Change By:


Jan Haderka
(21/Aug/13 2:09 PM)




Summary:


fckEditor:makerepositorybrowsersiteaware
again



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MGNLRSSAGG-94) Add default node data in config workspace for backup setting of RSSFeedImportHandler

2013-08-21 Thread JIRA (on behalf of Milan Divilek)














































Milan Divilek
 updated  MGNLRSSAGG-94


Add default node data in config workspace for backup setting of RSSFeedImportHandler
















Change By:


Milan Divilek
(21/Aug/13 2:12 PM)




Fix Version/s:


1.4.3



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MGNLCAT-88) Add an actionbar section that allows more item types

2013-08-21 Thread JIRA (on behalf of Federico Grilli)














































Federico Grilli
 updated  MGNLCAT-88


Add an actionbar section that allows more item types
















Change By:


Federico Grilli
(21/Aug/13 2:09 PM)




Summary:


Addanactionbarsectionthat
alows
allows
moreitemtypes



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MGNLWEBDAV-37) 'document' property only property set when creating file in DMS via Webdav

2013-08-21 Thread JIRA (on behalf of Robert Deckel)














































Robert Deckel
 created  MGNLWEBDAV-37


document property only property set when creating file in DMS via Webdav















Issue Type:


New Feature



Assignee:


Unassigned


Attachments:


webdav-file-properties.png



Created:


21/Aug/13 2:48 PM



Description:


When creating a file in the DMS of Author via copying a file using Webdav, the only property that is created is the "document" property. 
When manually creating a file in the DMS of Author via the browser interface using AdminCentral, the following properties are created: 
description_files 
creationDate 
creator 
document 
language 
modificationDate 
modifier 
name 
title 
type 

Because the files created via Webdav are missing the "creationDate", these documents will not be found during document searches using the publication date fields. 

See attached screen shot for more information.




Project:


Magnolia WebDAV Module



Priority:


Neutral




Reporter:


Robert Deckel



Security Level:


Public 




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MGNLMIGRATION-249) Fix integration tests of migration

2013-08-21 Thread on behalf of Robert Šiška














































Robert Šiška
 updated  MGNLMIGRATION-249


Fix integration tests of migration
















Change By:


Robert Šiška
(21/Aug/13 4:14 PM)




Description:


Theconfigurationsaftermigrationandafterfreshlyinstalledmoduleswhichusemigrationmodulehavetobeidentical.Modules:MGNLSTK,MGNLFORM,MGNLPUR,MGNLCMNT,MGNLCAT,MSHOP,MGNLRSSAGG,MGNLDMS,MGNLFORUM,MGNLBLOG.
Also/demo-projectand/demo-featuresaretested,sincetheyreknowmigratedaswell(



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MGNLMIGRATION-249) Fix integration tests of migration

2013-08-21 Thread on behalf of Robert Šiška














































Robert Šiška
 updated  MGNLMIGRATION-249


Fix integration tests of migration
















Change By:


Robert Šiška
(21/Aug/13 4:15 PM)




Description:


Theconfigurationsaftermigrationandafterfreshlyinstalledmoduleswhichusemigrationmodulehavetobeidentical.Modules:MGNLSTK,MGNLFORM,MGNLPUR,MGNLCMNT,MGNLCAT,MSHOP,MGNLRSSAGG,MGNLDMS,MGNLFORUM,MGNLBLOG.Also/demo-projectand/demo-featuresaretested,sincetheyreknowmigratedaswell(
MGNLSTK-1076).



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MGNLUI-1934) Clicking [MORE] in an Error or Warning banner does not open the message details in pulse.

2013-08-21 Thread JIRA (on behalf of Christopher Zimmermann)














































Christopher Zimmermann
 created  MGNLUI-1934


Clicking [MORE] in an Error or Warning banner does not open the message details in pulse.















Issue Type:


Bug



Affects Versions:


5.0.2



Assignee:


Unassigned


Components:


pulse



Created:


21/Aug/13 4:37 PM



Description:


The Pulse is successfully opened. But the pulse retains whatever state it had previously.
The Pulse should open and should display the message detail of the message which causes the Error or Warning banner to open.




Fix Versions:


5.0.x, 5.1



Project:


Magnolia UI



Priority:


Neutral




Reporter:


Christopher Zimmermann



Security Level:


Public 




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MGNLUI-1934) Clicking [MORE] in an Error or Warning banner does not open the message details in pulse.

2013-08-21 Thread JIRA (on behalf of Christopher Zimmermann)














































Christopher Zimmermann
 updated  MGNLUI-1934


Clicking [MORE] in an Error or Warning banner does not open the message details in pulse.
















Change By:


Christopher Zimmermann
(21/Aug/13 4:37 PM)




Priority:


Neutral
Major



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MGNLUI-1934) Clicking [MORE] in an Error or Warning banner does not open the message details in pulse.

2013-08-21 Thread JIRA (on behalf of Christopher Zimmermann)














































Christopher Zimmermann
 updated  MGNLUI-1934


Clicking [MORE] in an Error or Warning banner does not open the message details in pulse.
















Change By:


Christopher Zimmermann
(21/Aug/13 4:37 PM)




Assignee:


FedericoGrilli



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MGNLUI-1932) Single, unread message in Pulse causes scrollbar

2013-08-21 Thread JIRA (on behalf of Christopher Zimmermann)














































Christopher Zimmermann
 updated  MGNLUI-1932


Single, unread message in Pulse causes scrollbar
















Change By:


Christopher Zimmermann
(21/Aug/13 4:40 PM)




Fix Version/s:


5.0.4





Fix Version/s:


5.0.3



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MGNLUI-1932) Single, unread message in Pulse causes scrollbar

2013-08-21 Thread JIRA (on behalf of Christopher Zimmermann)














































Christopher Zimmermann
 updated  MGNLUI-1932


Single, unread message in Pulse causes scrollbar
















Change By:


Christopher Zimmermann
(21/Aug/13 4:40 PM)




Fix Version/s:


5.0.3





Fix Version/s:


5.0.4



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MGNLUI-1934) Clicking [MORE] in an Error or Warning banner does not open the message details in pulse.

2013-08-21 Thread JIRA (on behalf of Christopher Zimmermann)














































Christopher Zimmermann
 updated  MGNLUI-1934


Clicking [MORE] in an Error or Warning banner does not open the message details in pulse.
















Change By:


Christopher Zimmermann
(21/Aug/13 4:41 PM)




Fix Version/s:


5.0.4





Fix Version/s:


5.0.x



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MGNLUI-1934) Clicking [MORE] in an Error or Warning banner does not open the message details in pulse.

2013-08-21 Thread JIRA (on behalf of Christopher Zimmermann)














































Christopher Zimmermann
 updated  MGNLUI-1934


Clicking [MORE] in an Error or Warning banner does not open the message details in pulse.
















Change By:


Christopher Zimmermann
(21/Aug/13 4:39 PM)




Description:


ThePulseissuccessfullyopened.Butthepulseretainswhateverstateithadpreviously.ThePulseshouldopenandshoulddisplaythemessagedetailofthemessagewhichcausestheErrororWarningbannertoopen.
Notethatthisisespeciallyirritatingiftheuserhadpreviouslyhadamessageopen.ForthentheyclicktheMORElinkonanewmessage-butseeanoldermessage.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MGNLRSSAGG-91) Using a path with a dash (-) or a feed name starting with a digit in a stkSingleFeed paragraph causes an exception in FeedListModel

2013-08-21 Thread JIRA (on behalf of Jan Haderka)














































Jan Haderka
 reopened  MGNLRSSAGG-91


Using a path with a dash (-) or a feed name starting with a digit in a stkSingleFeed paragraph causes an exception in FeedListModel
















AbstractFeedModel.runQuerry() should be AbstractFeedModel.runQuery()





Change By:


Jan Haderka
(22/Aug/13 7:50 AM)




Resolution:


Fixed





Status:


Resolved
Reopened



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MAGNOLIA-5014) Search _still_ returns nothing when searching for Umlaut!

2013-08-21 Thread JIRA (on behalf of Jan Haderka)














































Jan Haderka
 updated  MAGNOLIA-5014


Search _still_ returns nothing when searching for Umlaut!
















Change By:


Jan Haderka
(22/Aug/13 7:56 AM)




Description:


Thishasbeendiscussedmanytimes,andIreallydidnotexpecttoseethatbuganymore,but...Ifyouentertextwithumlautcharacters,FCKEditorwillautomaticallyescapethese.Nowwhenyoutrytosearchforawordwithanumlautyoureoutofluck.Possiblework-arounds:
-
#
TurnofescapingoflatinspecialcharactersinFCKEditor(FCKConfig.IncludeLatinEntities=false;)
-
#
encodeyourqueryterm
-
#
or,asBorisonceproposed:savethecontentonceintheescapedversionandoncewithoutescaping;-)



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com





[magnolia-dev] [JIRA] (MAGNOLIA-5210) Broken div structure breaks page editor

2013-08-21 Thread JIRA (on behalf of Jan Haderka)














































Jan Haderka
 updated  MAGNOLIA-5210


Broken div structure breaks page editor
















Change By:


Jan Haderka
(22/Aug/13 7:55 AM)




Fix Version/s:


4.5.12





Fix Version/s:


4.5.11



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira








Forlistdetails,see:http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively,useourforums:http://forum.magnolia-cms.com/
Tounsubscribe,E-mailto:dev-list-unsubscr...@magnolia-cms.com