[magnolia-dev] [JIRA] (MGNLMAIL-62) Synchronize dependency in pom.xml and in module descriptor

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














































Roman Kovařík
 updated  MGNLMAIL-62


Synchronize dependency in pom.xml and in module descriptor
















Change By:


Roman Kovařík
(01/Sep/14 8:52 AM)




Summary:


mailshouldeitherdependondam-core(
Synchronizedependency
inpom.xml
),orondam-apiinsteadofdam-core(
and
inmodule
-description)
descriptor





Fix Version/s:


5.2.x





Fix Version/s:


5.2.1





Description:


Mailmoduleshouldeitherdependon{{dam-core}}(in{{pom.xml}}),oron{{dam-api}}insteadof{{dam-core}}(inmoduledescriptor).



























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] (MGNLMAIL-46) Sending magnolia pages as html email fails if command used in workflows

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














































Roman Kovařík
 updated  MGNLMAIL-46


Sending magnolia pages as html email fails if command used in workflows
















Change By:


Roman Kovařík
(01/Sep/14 8:57 AM)




Fix Version/s:


5.1.x





Affects Version/s:


Backlog





Description:


AsItriedtosendapageasanhtmlmailuponactivationfromwithingtheworkflowitsfailingwiththeattachederror.


Thecorrespondingpartoftheworkflowdefinitionlookslikethis:

{code}
setfield=fromvalue=ad...@magnolia-cms.com/


setfield=tovalue=olivier.ma...@magnolia-cms.com/


setfield=subjectvalue=Test/


setfield=contentTypevalue=html/


setfield=templateFilevalue=http://localhost:8080/demo-project/news_and_events/events/new-year-s-eve.html/


setfield=typevalue=magnolia/


participantref=command-sendMail/
{code}



























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








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] (MGNLMAIL-47) MailTemplate configured parameters replaced by context parameters

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














































Roman Kovařík
 updated  MGNLMAIL-47


MailTemplate configured parameters replaced by context parameters
















Change By:


Roman Kovařík
(01/Sep/14 8:57 AM)




Fix Version/s:


5.2.x





Fix Version/s:


5.1.x





Affects Version/s:


Backlog



























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] (MGNLPUR-138) TokenPasswordProcessor does not check if the user has an actual token

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














































Roman Kovařík
 updated  MGNLPUR-138


TokenPasswordProcessor does not check if the user has an actual token
















Change By:


Roman Kovařík
(01/Sep/14 12:49 PM)




Fix Version/s:


2.4





Fix Version/s:


2.3.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








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] (BLOSSOM-190) Provide also to blossom the MutliSite features placed in STK (i18n, prototype merging, etc)

2014-09-01 Thread JIRA (on behalf of Christian Ringele)














































Christian Ringele
 created  BLOSSOM-190


Provide also to blossom the MutliSite features placed in STK (i18n, prototype merging, etc)















Issue Type:


Improvement



Affects Versions:


3.0.3



Assignee:


Tobias Mattsson



Created:


01/Sep/14 1:36 PM



Description:


Multi site feature is a base functionality provided by the EE (Pro) usage.

The mutli site configurations used in the MultiSiteModule (modules config node/sites) reflected by "info.magnolia.multisite.MultiSiteModule.sites" use the STK based SiteDefintion bean Site "info.magnolia.module.templatingkit.sites.Site".

But various features of this configuration are based on pure STK implementations:

	i18n (the AbstractRenderer wrapps the nodes, not done by the blossom renderer)
	templates/prototype merging (done by the STK renderer)
	TemplatesAvailability class used for SiteDefition/templates node is pure STK (and not the one form the rendering module).



This limits the use of the blossom module in collaboration of the multi site module.
This functionality provided by the multi-site module should also be useable for the blossom module.

The way to solve this problem by using STK-Pages and adding blossom components is not applicable for all customers, but they still need to use the mutli site capability and its features.




Project:


Magnolia Blossom Module



Labels:


support




Priority:


Neutral




Reporter:


Christian Ringele




























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








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] (MGNLFORM-235) Allow using more than one validator: The relation between a form field and a validator should be 1:n and not 1:1

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














































Roman Kovařík
 reopened  MGNLFORM-235


Allow using more than one validator: The relation between a form field and a validator should be 1:n and not 1:1
















Change By:


Roman Kovařík
(01/Sep/14 2:15 PM)




Resolution:


Fixed





Status:


InQA
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] (MGNLTAGS-46) Make marketing tags manager work with personalization variants

2014-09-01 Thread JIRA (on behalf of Cheng Hu)














































Cheng Hu
 updated  MGNLTAGS-46


Make marketing tags manager work with personalization variants
















Change By:


Cheng Hu
(02/Sep/14 5:44 AM)




Summary:


Makemarketingtagsmanagerworkwith
personalization
variants



























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] (MGNLTAGS-46) Make marketing tags manager work with variants

2014-09-01 Thread JIRA (on behalf of Cheng Hu)














































Cheng Hu
 created  MGNLTAGS-46


Make marketing tags manager work with variants















Issue Type:


Task



Assignee:


Unassigned


Created:


02/Sep/14 5:44 AM



Description:


Currently marketing tags does not take variants in account.


	There should be options and clearly defined behavior about how to apply marketing tags to variants of a page
	Perhaps each variant may even need its own unique marketing tag?






Project:


Marketing Tags Manager



Labels:


next




Priority:


Neutral




Reporter:


Cheng Hu




























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