[magnolia-dev] [JIRA] (MGNLACTIVATION-99) Unpublishing right after publication can result in exception

2014-12-10 Thread JIRA (on behalf of Evzen Fochr)














































Evzen Fochr
 reopened  MGNLACTIVATION-99


Unpublishing right after publication can result in exception
















Change By:


Evzen Fochr
(10/Dec/14 4:37 PM)




Resolution:


Fixed





Status:


In QA
Reopened



























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








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





[magnolia-dev] [JIRA] (MGNLUI-3294) Links to magnolia pages created from CK editor are rendered wrong on public instances (wrong context-path).

2014-12-10 Thread JIRA (on behalf of Christoph Meier)














































Christoph Meier
 updated  MGNLUI-3294


Links to magnolia pages created from CK editor are rendered wrong on public instances (wrong context-path).
















Change By:


Christoph Meier
(10/Dec/14 2:09 PM)




Labels:


support



























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








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





[magnolia-dev] [JIRA] (MGNLUI-3294) Links to magnolia pages created from CK editor are rendered wrong on public instances (wrong context-path).

2014-12-10 Thread JIRA (on behalf of Christoph Meier)














































Christoph Meier
 created  MGNLUI-3294


Links to magnolia pages created from CK editor are rendered wrong on public instances (wrong context-path).















Issue Type:


Bug



Affects Versions:


5.3.6



Assignee:


Unassigned


Created:


10/Dec/14 2:05 PM



Description:


To reproduce:

Use a dialog with a Richtext-Editor which the property images=true.
=> To keep it easy, just add a text/image component on an article-page.
Before doing: 
Set /modules/standard-templating-kit/dialogs/generic/controls/text@images=true

Add the text/image component. 
Link to a magnolia-page.
Publish all.

=> You will/should notice, that the link made with CK-Editor on the public instance is still linked to a page in author instance.




Fix Versions:


5.3.7



Project:


Magnolia UI



Priority:


Neutral




Reporter:


Christoph Meier



Security Level:


Public 




























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








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





[magnolia-dev] [JIRA] (MGNLRSSAGG-188) Memory leaks and application hangs created by FastRSSFeedFetcher

2014-12-10 Thread JIRA (on behalf of Lars Fischer)














































Lars Fischer
 created  MGNLRSSAGG-188


Memory leaks and application hangs created by FastRSSFeedFetcher















Issue Type:


Bug



Affects Versions:


2.3.1



Assignee:


Aleksandr Pchelintcev



Components:


rss_generator



Created:


10/Dec/14 2:02 PM



Description:


When the webapplication is shut down during RSS aggregator updates, the Thread pool of FastRSSFeedFetcher is not shut down properly and prevents the application from being shut down properly.

To fix this, Namics created a method in the ModuleLifecycle to fix this.



private void shutdownRssFeedFetcher() {
RSSFeedFetcher fetcher = Components.getComponent(RSSAggregator.class).getFetcher();
if (fetcher instanceof FastRSSFeedFetcher) {
FastRSSFeedFetcher fastFetcher = (FastRSSFeedFetcher) fetcher;

try {
Field executorServiceField = FastRSSFeedFetcher.class.getDeclaredField("executorService");
executorServiceField.setAccessible(true);

Object executorServiceObject = executorServiceField.get(fastFetcher);

if (executorServiceObject instanceof ExecutorService) {
ExecutorService executorService = (ExecutorService) executorServiceObject;

log.info("Shutting down feed fetcher executor service: " + executorService);
List terminated = executorService.shutdownNow();
log.info("Cancelled {} Runnable instances.", terminated.size());

log.info("Terminating feed fetcher executor service: " + executorService);
executorService.awaitTermination(5, TimeUnit.MINUTES);
}
} catch (Throwable e) {
log.error("Could not shutdown RSS Feed Fetcher", e);
}

}
}



Of course, it would be nice if the RSSFeedFetcher interface had a stop() method, and the RSSAggregator Module itself would stop it's fetcher. 

To do this, I suggest a method like this:


public void shutdown() {
List runnables = executor.shutdownNow();
log.info("Canceling {} RSS Update Tasks because of shutdown...", runnables.size());

try {
if (executor.awaitTermination(5, TimeUnit.MINUTES)) {
log.info("Termination successful.");
} else {
log.error("Termination timed out.");
}
} catch (InterruptedException e) {
log.error("Termination error.", e);
}
}






Project:


Magnolia RSS Aggregator Module



Labels:


support




Priority:


Major




Reporter:


Lars Fischer




























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








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





[magnolia-dev] [JIRA] (MGNLUI-3293) Basic upload form field does not show preview of the image when preview = true

2014-12-10 Thread JIRA (on behalf of YMC AG)














































YMC AG
 created  MGNLUI-3293


Basic upload form field does not show preview of the image when preview = true















Issue Type:


Bug



Affects Versions:


5.3.4



Assignee:


Unassigned


Attachments:


Screen Shot 2014-12-10 at 13.44.47.png



Components:


dialogs, forms



Created:


10/Dec/14 1:45 PM



Description:


Basic upload form field does not show preview of the image when preview = true.

Basic upload field = info.magnolia.ui.form.field.definition.BasicUploadFieldDefinition





Environment:


OS X Yosemite, JDK 1.7, Tomcat apache-tomcat-7.0.57




Project:


Magnolia UI



Priority:


Neutral




Reporter:


YMC AG



Security Level:


Public 




























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








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





[magnolia-dev] [JIRA] (MGNLUI-3292) readonly form field property should be case insensitive

2014-12-10 Thread JIRA (on behalf of YMC AG)














































YMC AG
 created  MGNLUI-3292


readonly form field property should be case insensitive















Issue Type:


Improvement



Affects Versions:


5.3.4



Assignee:


Unassigned


Attachments:


Screen Shot 2014-12-10 at 13.38.35.png



Components:


dialogs, forms



Created:


10/Dec/14 1:39 PM



Description:


When form fields contain the value "readonly" all in lowercase letters the rendered fields are not displayed as readonly. The user can still enter text inside the field.

When the form fields contain the "readOnly" property then the user can see the field as readonly and cannot enter text which is the correct behavior.

Typing readonly=true or readOnly=true should have the same effect. In both cases the user should not be able to enter text.




Environment:


OS X Yosemite, JDK 1.7, Tomcat apache-tomcat-7.0.57




Project:


Magnolia UI



Labels:


dialog
ux
next




Priority:


Neutral




Reporter:


YMC AG



Security Level:


Public 




























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








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





[magnolia-dev] [JIRA] (MGNLUI-3291) MGNLUI-3290

2014-12-10 Thread JIRA (on behalf of YMC AG)














































YMC AG
 updated  MGNLUI-3291


MGNLUI-3290
















Change By:


YMC AG
(10/Dec/14 1:21 PM)




Description:


The combination of these two properties on a form field does not work:

i18n = truereadOnly = true



























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








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





[magnolia-dev] [JIRA] (MGNLUI-3291) MGNLUI-3290

2014-12-10 Thread JIRA (on behalf of YMC AG)














































YMC AG
 created  MGNLUI-3291


MGNLUI-3290















Issue Type:


Bug



Affects Versions:


5.3.4



Assignee:


Unassigned


Attachments:


Form-readOnly-ContactsApp.png, Form-readOnly-TextImageDialog.png



Components:


dialogs, forms



Created:


10/Dec/14 1:20 PM



Description:


The combination of these two properties on a form field does not work:
i18n = true
readOnly = true




Environment:


OS X 10.10.1, JDK 1.7, Tomcat apache-tomcat-7.0.57




Project:


Magnolia UI



Labels:


support




Priority:


Critical




Reporter:


YMC AG



Security Level:


Public 




























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








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





[magnolia-dev] [JIRA] (MGNLACTIVATION-99) Unpublishing right after publication can result in exception

2014-12-10 Thread JIRA (on behalf of Jan Haderka)














































Jan Haderka
 reopened  MGNLACTIVATION-99


Unpublishing right after publication can result in exception
















Make sure any changes you do are maximally localised - do not change what this class is passing onto the syndicator.





Change By:


Jan Haderka
(10/Dec/14 1:03 PM)




Resolution:


Fixed





Status:


Resolved
Reopened



























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








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





[magnolia-dev] [JIRA] (MGNLUI-3282) About app crashes in IE8

2014-12-10 Thread JIRA (on behalf of Christopher Zimmermann)














































Christopher Zimmermann
 updated  MGNLUI-3282


About app crashes in IE8
















Change By:


Christopher Zimmermann
(10/Dec/14 11:59 AM)




Fix Version/s:


5.3.7





Fix Version/s:


5.3.6



























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








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





[magnolia-dev] [JIRA] (MGNLUI-3281) IE8 date chooser not displayed in forms

2014-12-10 Thread JIRA (on behalf of Christopher Zimmermann)














































Christopher Zimmermann
 updated  MGNLUI-3281


IE8 date chooser not displayed in forms
















Change By:


Christopher Zimmermann
(10/Dec/14 11:59 AM)




Fix Version/s:


5.3.7





Fix Version/s:


5.3.6



























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








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





[magnolia-dev] Template file not found

2014-12-10 Thread Nattarat Champreeda (via Magnolia Forums)
I follow this tutorial vdo. 
[url]https://www.youtube.com/watch?v=aU7q3daQ8S0#t=170[/url]
However when I try to edit my page this error occurs.
[quote]Template Error!

Error while rendering [/MyFirstPage] with template 
[myTemplateModule:pages/myPageTemplate]: RenderException: 
java.io.FileNotFoundException: Template 
/myTemplateModule/pages/myPageTemplate.ftl not found.[/quote]

My project structure is same as the project in vdo. Does anyone know the 
problem?

Thank 
ning

-- 
Context is everything: 
http://forum.magnolia-cms.com/forum/thread.html?threadId=5e67b029-8a7c-4daf-9560-e614c276afbd



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




[magnolia-dev] [JIRA] (MGNLUI-3280) IE8 checkboxes displayed improperly

2014-12-10 Thread JIRA (on behalf of Christopher Zimmermann)














































Christopher Zimmermann
 updated  MGNLUI-3280


IE8 checkboxes displayed improperly
















Change By:


Christopher Zimmermann
(10/Dec/14 11:59 AM)




Fix Version/s:


5.3.7





Fix Version/s:


5.3.6



























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








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





[magnolia-dev] [JIRA] (MGNLUI-3227) Improve validation capabilities of the multi fields

2014-12-10 Thread JIRA (on behalf of Christopher Zimmermann)














































Christopher Zimmermann
 updated  MGNLUI-3227


Improve validation capabilities of the multi fields
















Change By:


Christopher Zimmermann
(10/Dec/14 11:53 AM)




Fix Version/s:


5.3.6



























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








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





[magnolia-dev] [JIRA] (MGNLREST-60) RESTEasy dependency should be upgraded to 3.0.10.Final

2014-12-10 Thread JIRA (on behalf of Philip Mundt)














































Philip Mundt
 updated  MGNLREST-60


RESTEasy dependency should be upgraded to 3.0.10.Final 
















Change By:


Philip Mundt
(10/Dec/14 11:41 AM)




Summary:


RESTEasy
 client
 dependency should be upgraded to 3.0.10.Final 



























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








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





[magnolia-dev] [JIRA] (MGNLREST-60) RESTEasy client dependency should be upgraded to 3.0.10.Final

2014-12-10 Thread JIRA (on behalf of Philip Mundt)














































Philip Mundt
 updated  MGNLREST-60


RESTEasy client dependency should be upgraded to 3.0.10.Final 
















Change By:


Philip Mundt
(10/Dec/14 11:40 AM)




Description:


From MGNLRESTCL-5:{quote}I think the RESTEasy client dependency should be upgraded from 3.0.4.Final to the latest stable one which at the moment is 3.0.10.Final? There have been a large number of bug fixes in between so I think it is good to stay up-to-date.We use the RESTEasy client in Magnolia for consuming an external REST API so it is important for us to use the latest version. We have upgraded to 3.0.10.Final manually and everything seems to work just fine.{quote}



























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








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





[magnolia-dev] [JIRA] (MGNLREST-60) RESTEasy client dependency should be upgraded to 3.0.10.Final

2014-12-10 Thread JIRA (on behalf of Philip Mundt)














































Philip Mundt
 created  MGNLREST-60


RESTEasy client dependency should be upgraded to 3.0.10.Final 















Issue Type:


Task



Assignee:


Unassigned


Components:


integration, services



Created:


10/Dec/14 11:39 AM



Fix Versions:


1.0.x



Project:


Magnolia REST Framework



Priority:


Neutral




Reporter:


Philip Mundt



Security Level:


Public 




























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








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





[magnolia-dev] [JIRA] (MGNLUI-3227) Improve validation capabilities of the multi fields

2014-12-10 Thread JIRA (on behalf of Christopher Zimmermann)














































Christopher Zimmermann
 updated  MGNLUI-3227


Improve validation capabilities of the multi fields
















Change By:


Christopher Zimmermann
(10/Dec/14 11:30 AM)




Labels:


support



























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








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





[magnolia-dev] [JIRA] (MGNLPUR-144) Password reminder could be configured to require email (or even telephone number) instead of username.

2014-12-10 Thread JIRA (on behalf of Jaroslav Simak)














































Jaroslav Simak
 updated  MGNLPUR-144


Password reminder could be configured to require email (or even telephone number) instead of username.
















Change By:


Jaroslav Simak
(10/Dec/14 10:29 AM)




Fix Version/s:


2.4.2



























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








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





[magnolia-dev] [JIRA] (MGNLUI-3290) Field properties: Combination of i18n=true & readOnly=true results in Exception & Dialog or subApp does not open.

2014-12-10 Thread JIRA (on behalf of Christian Ringele)














































Christian Ringele
 created  MGNLUI-3290


Field properties: Combination of i18n=true & readOnly=true results in Exception & Dialog or subApp does not open.















Issue Type:


Bug



Affects Versions:


5.3.5



Assignee:


Unassigned


Attachments:


Form-readOnly-ContactsApp.png, Form-readOnly-TextImageDialog.png



Components:


forms



Created:


10/Dec/14 9:51 AM



Description:


The combination of these two properties on a form field does not work:

	i18n = true
	readOnly = true



The the detail subapp of the contacts app does not open and trows:


2014-12-10 09:49:48,033 ERROR agnolia.ui.framework.app.AppInstanceControllerImpl: Sub-app detail failed to start: Invocation of method valueChange in info.magnolia.ui.dialog.formdialog.ItemFormView$2 failed.
com.vaadin.event.ListenerMethod$MethodException: Invocation of method valueChange in info.magnolia.ui.dialog.formdialog.ItemFormView$2 failed.
	at com.vaadin.event.ListenerMethod.receiveEvent(ListenerMethod.java:528)
	at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:167)
	at com.vaadin.server.AbstractClientConnector.fireEvent(AbstractClientConnector.java:969)
	at com.vaadin.ui.AbstractField.fireValueChange(AbstractField.java:1126)
	at com.vaadin.ui.AbstractField.setValue(AbstractField.java:542)
	at com.vaadin.ui.AbstractSelect.setValue(AbstractSelect.java:702)
	at com.vaadin.ui.AbstractSelect.setValue(AbstractSelect.java:671)
	at info.magnolia.ui.dialog.formdialog.ItemFormView.setCurrentLocale(ItemFormView.java:143)
	at info.magnolia.ui.dialog.formdialog.FormBuilder.buildForm(FormBuilder.java:132)
	at info.magnolia.ui.contentapp.detail.DetailPresenter.setItemView(DetailPresenter.java:159)
	at info.magnolia.ui.contentapp.detail.DetailPresenter.start(DetailPresenter.java:138)
	at info.magnolia.ui.contentapp.detail.DetailEditorPresenter.start(DetailEditorPresenter.java:122)
	at info.magnolia.ui.contentapp.detail.DetailEditorPresenter.start(DetailEditorPresenter.java:101)
	at info.magnolia.ui.contentapp.detail.DetailSubApp.start(DetailSubApp.java:118)
	at info.magnolia.ui.contentapp.detail.DetailSubApp.start(DetailSubApp.java:1)



In the textImage component the dialog does not open and trwos:


2014-12-10 09:51:04,699 ERROR info.magnolia.pages.app.editor.PageEditorPresenter: An error occurred while executing action [editComponent]
info.magnolia.ui.api.action.ActionExecutionException: Action execution failed for action: editComponent
	at info.magnolia.ui.api.action.AbstractActionExecutor.execute(AbstractActionExecutor.java:64)
	at info.magnolia.pages.app.editor.PageEditorPresenter.onAction(PageEditorPresenter.java:127)
	at info.magnolia.ui.vaadin.editor.PageEditor$1.editComponent(PageEditor.java:93)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at com.vaadin.server.ServerRpcManager.applyInvocation(ServerRpcManager.java:168)
	at com.vaadin.server.ServerRpcManager.applyInvocation(ServerRpcManager.java:118)
	at com.vaadin.server.communication.ServerRpcHandler.handleBurst(ServerRpcHandler.java:214)
	at com.vaadin.server.communication.ServerRpcHandler.handleRpc(ServerRpcHandler.java:111)
	at com.vaadin.server.communication.UidlRequestHandler.synchronizedHandleRequest(UidlRequestHandler.java:91)
	at com.vaadin.server.SynchronizedRequestHandler.handleRequest(SynchronizedRequestHandler.java:37)
	at com.vaadin.server.VaadinService.handleRequest(VaadinService.java:1371)
	at com.vaadin.server.VaadinServlet.service(VaadinServlet.java:238)






Project:


Magnolia UI



Priority:


Neutral




[magnolia-dev] [JIRA] (MGNLCACHE-32) Upgrade Ehcache to 2.8

2014-12-10 Thread JIRA (on behalf of Jan Haderka)














































Jan Haderka
 updated  MGNLCACHE-32


Upgrade Ehcache to 2.8
















Change By:


Jan Haderka
(10/Dec/14 9:31 AM)




Assignee:


Grégory Joseph



























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








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





[magnolia-dev] [JIRA] (MGNLCACHE-46) Magnolia CacheFilter shoudn't write content twice for non-cached pages

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














































Roman Kovařík
 reopened  MGNLCACHE-46


Magnolia CacheFilter shoudn't write content twice for non-cached pages
















Change By:


Roman Kovařík
(10/Dec/14 9:26 AM)




Resolution:


Obsolete





Status:


Closed
Reopened



























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








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





[magnolia-dev] [JIRA] (MGNLCACHE-46) Magnolia CacheFilter shoudn't write content twice for non-cached pages

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














































Roman Kovařík
 updated  MGNLCACHE-46


Magnolia CacheFilter shoudn't write content twice for non-cached pages
















Change By:


Roman Kovařík
(10/Dec/14 9:26 AM)




Comment:


Obsolete



























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








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





[magnolia-dev] [JIRA] (MGNLACTIVATION-99) Unpublishing right after publication can result in exception

2014-12-10 Thread JIRA (on behalf of Jan Haderka)














































Jan Haderka
 reopened  MGNLACTIVATION-99


Unpublishing right after publication can result in exception
















The code:

	When checking skipPath you check simply for startsWith. This is common mistake that will result in path that is superset of skipped path to be skipped as well, e.g. if skipPath=/skip/me it will skip also node at path /skip/meNOT
The test:
	the TestSimpleSydicator is not really generic "testSS". More explicit name would help later to make anyone tempted to reuse it understand what it does. Something like ThrowExceptionWhileActivatingA_B_ANodeSyndicator
	since in your fix you are manipulating parent nodes of activated node, you need extra test to cover also the case when activating node just under the root (since root node that will be obtained as parent tends to behave differently in certain corner cases)
	test for names that are superset of failing name is called for (see above comment regarding code issue)







Change By:


Jan Haderka
(10/Dec/14 9:20 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








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