[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4651) Create proper types hosting constants for our jcr nodeTypes and the jcr propertyNames
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Lipp updated MAGNOLIA-4651: -- Summary: Create proper types hosting constants for our jcr nodeTypes and the jcr propertyNames (was: Create proper types interfaces constants for our jcr nodeTypes and the jcr propertyNames we're frequently using) > Create proper types hosting constants for our jcr nodeTypes and the jcr > propertyNames > - > > Key: MAGNOLIA-4651 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4651 > Project: Magnolia > Issue Type: Improvement > Security Level: Public >Affects Versions: 5.0 Alpha1 s008 >Reporter: Daniel Lipp >Assignee: Daniel Lipp > Fix For: 5.0 Alpha1 s009 > > > When implementing MAGNOLIA-4640 we realized we should keep the frequently > used propertyNames as constants. There's already MgnlNodeType but this is > rather confusing because it keeps both nodeTypes and propertyNames. > - nodeTypes go to MgnlNodeTypeNames, propertyNames to MgnlPropertyNames > interface > - MgnlNodeTypeNAmes > - mixin's get a _MIX prefix, nodetypes (default) don't get one > - MgnlPropertyNames > - no prefixes > - camel case names will not be concatenated in the constant name: > - e.g. *_FROZENNODE -> *_FROZEN_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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4671) Bad error handling for method for info.magnolia.templating.functions.TemplatingFunctions#link
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Haderka updated MAGNOLIA-4671:
--
Assignee: Ondřej Chytil
Fix Version/s: 4.5.7
> Bad error handling for method for
> info.magnolia.templating.functions.TemplatingFunctions#link
> -
>
> Key: MAGNOLIA-4671
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4671
> Project: Magnolia
> Issue Type: Improvement
> Security Level: Public
> Components: templating
>Affects Versions: 4.5.4
>Reporter: Per Andersson
>Assignee: Ondřej Chytil
> Fix For: 4.5.7
>
>
> Hi,
> When calling the method
> "info.magnolia.templating.functions.TemplatingFunctions#link" from freemarker
> using:
> {noformat}
> <#assign dmsLink = cmsfn.link("dms", "/demo-docs/children/wizoz10") />
> {noformat}
> The only error visible for me is:
> {noformat}
> Error on line 95, column 11 in path/to/template
> cmsfn.link("dms", "/demo-docs/children/wizoz10") is undefined.
> It cannot be assigned to dmsLink
> The problematic instruction:
> --
> ==> assignment: dmsLink=cmsfn.link("dms", "/demo-docs/children/wizoz10") [on
> line 95, column 11 in path/to/template]
> --
> Java backtrace for programmers:
> --
> freemarker.core.InvalidReferenceException: Error on line 95, column 11 in
> path/to/template
> cmsfn.link("dms", "/demo-docs/children/wizoz10") is undefined.
> It cannot be assigned to dmsLink
> at freemarker.core.Assignment.accept(Assignment.java:111)
> at freemarker.core.Environment.visit(Environment.java:221)
> at freemarker.core.MixedContent.accept(MixedContent.java:92)
> {noformat}
> When downloading the source code I've found:
> {noformat}
> public String link(String workspace, String nodeIdentifier) {
> try {
> return LinkUtil.createLink(workspace, nodeIdentifier);
> } catch (RepositoryException e) {
> return null;
> }
> }
> {noformat}
> The real error "javax.jcr.RepositoryException: invalid identifier:
> /demo-docs/children/wizoz10" was hidden from me because of this. I first
> assumed that the method "link" was missing due to the error visible to me in
> the log.
> Better consistency for the error handling in this file would be appreciated.
> Example:
> {noformat}
> public String link(String workspace, String nodeIdentifier) {
> try {
> return LinkUtil.createLink(workspace, nodeIdentifier);
> } catch (RepositoryException e) {
> log.error(e.getMessage(), e); // Print the real error in the log
> return null;
> }
> }
> {noformat}
> Also I see other methods have the same problem, those should be updated as
> well.
--
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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4633) Allow specifying access credentials to the users workspace via the tree dialog
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka updated MAGNOLIA-4633: -- Assignee: Roman Kovařík Fix Version/s: 4.4.10 > Allow specifying access credentials to the users workspace via the tree dialog > -- > > Key: MAGNOLIA-4633 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4633 > Project: Magnolia > Issue Type: Bug > Security Level: Public > Components: admininterface, gui, security >Affects Versions: 4.4.5, 4.5.6 >Reporter: Zdenek Skodik >Assignee: Roman Kovařík > Fix For: 4.4.10, 4.5.7 > > Attachments: NPE.txt, NPE_userroles.png > > > Changes done to MAGNOLIA-3763 introduces NPE when you're about to click on > the "Choose" button. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLMIGRATION-171) Migration module breaks code which is using <> instead of [] when combined on in a single expression
Migration module breaks code which is using <> instead of [] when combined on
in a single expression
Key: MGNLMIGRATION-171
URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-171
Project: Magnolia Migration
Issue Type: Bug
Affects Versions: 1.1.3
Reporter: Tomas Brimor
Assignee: Jozef Chocholacek
Priority: Major
Pre migration:
{noformat}
<#assign guideProductCategoryUUID =
popularGuidesProductCategories[guide.@uuid]/>
{noformat}
Post migration
{noformat}
<#assign guideProductCategoryUUID = popularGuidesProductCategories[guide.]/>
{noformat}
--
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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLMIGRATION-170) Magnolia migration module does not migrate templates using <> instead of []
Magnolia migration module does not migrate templates using <> instead of [] --- Key: MGNLMIGRATION-170 URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-170 Project: Magnolia Migration Issue Type: Bug Affects Versions: 1.1.3 Reporter: Tomas Brimor Assignee: Jozef Chocholacek Priority: Major -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLUI-184) Implement "edit user" action for the action bar button
Implement "edit user" action for the action bar button -- Key: MGNLUI-184 URL: http://jira.magnolia-cms.com/browse/MGNLUI-184 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Components: security app Reporter: Jozef Chocholacek Assignee: Jozef Chocholacek Populate the fields for group/role management properly, skip the password, ... -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLUI-183) Implement save dialog action for the User form
Implement save dialog action for the User form -- Key: MGNLUI-183 URL: http://jira.magnolia-cms.com/browse/MGNLUI-183 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Components: security app Reporter: Jozef Chocholacek Assignee: Jozef Chocholacek Implement the save action so it will process the groups and roles and save the proper UUIDs to the corresponding subnodes of the user node. Handle password field properly (i.e. encrypt it, do not erase it if the field is left blank, ...) -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLUI-182) Add fields for group/role management to the User form
Add fields for group/role management to the User form - Key: MGNLUI-182 URL: http://jira.magnolia-cms.com/browse/MGNLUI-182 Project: Magnolia UI Issue Type: Task Security Level: Public Components: security app Reporter: Jozef Chocholacek Assignee: Jozef Chocholacek Add TwinColSelect fields for the management of groups/roles. As well as the other missing fields (password, enabled, ...). -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLUI-180) Implement save dialog action for the Group form
Implement save dialog action for the Group form --- Key: MGNLUI-180 URL: http://jira.magnolia-cms.com/browse/MGNLUI-180 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Components: security app Reporter: Jozef Chocholacek Assignee: Jozef Chocholacek Implement save dialog action, which will take the list of group/role UUIDs and save it to the proper subnode of the group 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MPAGEEXPORT-14) Flying-saucer sources jar in bundled-webapp
[ http://jira.magnolia-cms.com/browse/MPAGEEXPORT-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MPAGEEXPORT-14: --- Description: Sources for flying-saucer-core and flying-saucer-pdf jars end up in bundled-webapp. I guess they should be excluded. (was: flying-saucer-core and flying-saucer-pdf jars end up in bundled-webapp. I guess they should be excluded.) > Flying-saucer sources jar in bundled-webapp > --- > > Key: MPAGEEXPORT-14 > URL: http://jira.magnolia-cms.com/browse/MPAGEEXPORT-14 > Project: Magnolia Page Exporting Module > Issue Type: Bug >Affects Versions: 1.0 Alpha1 S7 >Reporter: Federico Grilli >Assignee: Espen Jervidalo >Priority: Blocker > Fix For: 1.0 Alpha1 > > > Sources for flying-saucer-core and flying-saucer-pdf jars end up in > bundled-webapp. I guess they should be excluded. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLUI-181) Implement "edit group" action for action bar button
Implement "edit group" action for action bar button --- Key: MGNLUI-181 URL: http://jira.magnolia-cms.com/browse/MGNLUI-181 Project: Magnolia UI Issue Type: Sub-task Security Level: Public Components: security app Reporter: Jozef Chocholacek Assignee: Jozef Chocholacek Implement the action so it will get the group node and distribute the content of gropus and roles subnodes to the Item for the form. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLUI-179) Add fields for group/role management to the Group form
Add fields for group/role management to the Group form -- Key: MGNLUI-179 URL: http://jira.magnolia-cms.com/browse/MGNLUI-179 Project: Magnolia UI Issue Type: Task Security Level: Public Components: security app Reporter: Jozef Chocholacek Assignee: Jozef Chocholacek Add TwinColSelect fields for managing groups and roles the group belongs to (resp. are assigned to the group). -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLTPLSMPL-3) Downgrade dependency on AdminInterface to 4.5
Downgrade dependency on AdminInterface to 4.5 - Key: MGNLTPLSMPL-3 URL: http://jira.magnolia-cms.com/browse/MGNLTPLSMPL-3 Project: Magnolia Templating Samples Issue Type: Task Affects Versions: 5.0 Alpha1 S7 Reporter: Federico Grilli Assignee: Federico Grilli Priority: Major Fix For: 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLMAIL-2) Downgrade dependency on AdminInterface to 4.5
Downgrade dependency on AdminInterface to 4.5 - Key: MGNLMAIL-2 URL: http://jira.magnolia-cms.com/browse/MGNLMAIL-2 Project: Magnolia Mail Module Issue Type: Task Reporter: Federico Grilli Assignee: Federico Grilli Priority: Major Fix For: 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLIMG-98) make ImagingServlet and caching use new node-api
[ http://jira.magnolia-cms.com/browse/MGNLIMG-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MGNLIMG-98: --- Fix Version/s: 2.3 Alpha1 S9 (was: 2.3) > make ImagingServlet and caching use new node-api > > > Key: MGNLIMG-98 > URL: http://jira.magnolia-cms.com/browse/MGNLIMG-98 > Project: Magnolia Imaging Module > Issue Type: Task >Affects Versions: 2.3 Alpha1 S7 >Reporter: Espen Jervidalo >Assignee: Grégory Joseph > Fix For: 2.3 Alpha1 S9 > > > A log of code is currently deprecated. At least the main classes should be > adapted to the new API. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLIMG-102) Downgrade dependency on AdminInterface to 4.5
Downgrade dependency on AdminInterface to 4.5 - Key: MGNLIMG-102 URL: http://jira.magnolia-cms.com/browse/MGNLIMG-102 Project: Magnolia Imaging Module Issue Type: Task Affects Versions: 2.3 Alpha1 S7 Reporter: Federico Grilli Assignee: Federico Grilli Fix For: 2.3 Alpha1 S9 -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLIMG-99) Add proper setters for node2bean.
[ http://jira.magnolia-cms.com/browse/MGNLIMG-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MGNLIMG-99: --- Fix Version/s: 2.3 Alpha1 S9 (was: 2.3) Affects Version/s: 2.3 Alpha1 S7 > Add proper setters for node2bean. > - > > Key: MGNLIMG-99 > URL: http://jira.magnolia-cms.com/browse/MGNLIMG-99 > Project: Magnolia Imaging Module > Issue Type: Task >Affects Versions: 2.3 Alpha1 S7 >Reporter: Jaroslav Simak >Assignee: Jaroslav Simak > Fix For: 2.3 Alpha1 S9 > > -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MPAGEEXPORT-14) Flying-saucer sources jar in bundled-webapp
Flying-saucer sources jar in bundled-webapp --- Key: MPAGEEXPORT-14 URL: http://jira.magnolia-cms.com/browse/MPAGEEXPORT-14 Project: Magnolia Page Exporting Module Issue Type: Bug Affects Versions: 1.0 Alpha1 S7 Reporter: Federico Grilli Assignee: Espen Jervidalo Priority: Blocker Fix For: 1.0 Alpha1 I guess those should be excluded. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MPAGEEXPORT-14) Flying-saucer sources jar in bundled-webapp
[ http://jira.magnolia-cms.com/browse/MPAGEEXPORT-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Grilli updated MPAGEEXPORT-14: --- Description: flying-saucer-core and flying-saucer-pdf jars end up in bundled-webapp. I guess they should be excluded. (was: I guess those should be excluded.) > Flying-saucer sources jar in bundled-webapp > --- > > Key: MPAGEEXPORT-14 > URL: http://jira.magnolia-cms.com/browse/MPAGEEXPORT-14 > Project: Magnolia Page Exporting Module > Issue Type: Bug >Affects Versions: 1.0 Alpha1 S7 >Reporter: Federico Grilli >Assignee: Espen Jervidalo >Priority: Blocker > Fix For: 1.0 Alpha1 > > > flying-saucer-core and flying-saucer-pdf jars end up in bundled-webapp. I > guess they should be excluded. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLIMG-91) Cannot find symbol during build
[
http://jira.magnolia-cms.com/browse/MGNLIMG-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Haderka updated MGNLIMG-91:
---
Assignee: Jan Haderka
Fix Version/s: 2.1.2
2.2.2
2.3 Alpha1 S8
(was: 2.x)
Affects Version/s: 2.0
> Cannot find symbol during build
> ---
>
> Key: MGNLIMG-91
> URL: http://jira.magnolia-cms.com/browse/MGNLIMG-91
> Project: Magnolia Imaging Module
> Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Ondřej Chytil
>Assignee: Jan Haderka
> Fix For: 2.1.2, 2.2.2, 2.3 Alpha1 S8
>
>
> Imaging module build seems to randomly produce errors during build phase:
> {noformat}
> [INFO]
> /home/chytilo/help/imaging-2.2/target/checkout/magnolia-module-imaging/src/main/java/info/magnolia/imaging/operations/text/BasicTextRenderer.java:[75,43]
> cannot find symbol
> [INFO] symbol : method getPositionFor(float,int,int)
> [INFO] location: class
> info.magnolia.imaging.operations.text.HorizontalAlignment
> [INFO]
> [INFO]
> /home/chytilo/help/imaging-2.2/target/checkout/magnolia-module-imaging/src/main/java/info/magnolia/imaging/operations/text/BasicTextRenderer.java:[76,41]
> cannot find symbol
> [INFO] symbol : method getPositionFor(float,int,int)
> [INFO] location: class info.magnolia.imaging.operations.text.VerticalAlignment
> {noformat}
--
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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLSTK-1028) Implement stkfn.getAsset(contentMap, nodeDataPrefix, variationName)
Implement stkfn.getAsset(contentMap, nodeDataPrefix, variationName)
---
Key: MGNLSTK-1028
URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1028
Project: Magnolia Standard Templating Kit
Issue Type: Improvement
Affects Versions: 2.0.6
Reporter: Cesar Desales
Assignee: Eric Hechinger
Implement getAsset with a ContentMap object as first argument:
{code}
getAsset(ContentMap content, String nodeDataPrefix, String variationName)
{code}
The current version of STK already includes similar methods.
{code}
getAsset(ContentMap content, String nodeDataPrefix)
getAsset(Node content, String nodeDataPrefix, String variationName)
{code}
--
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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MAGNOLIA-4671) Bad error handling for method for info.magnolia.templating.functions.TemplatingFunctions#link
Bad error handling for method for
info.magnolia.templating.functions.TemplatingFunctions#link
-
Key: MAGNOLIA-4671
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4671
Project: Magnolia
Issue Type: Improvement
Security Level: Public
Components: templating
Affects Versions: 4.5.4
Reporter: Per Andersson
Hi,
When calling the method
"info.magnolia.templating.functions.TemplatingFunctions#link" from freemarker
using:
{noformat}
<#assign dmsLink = cmsfn.link("dms", "/demo-docs/children/wizoz10") />
{noformat}
The only error visible for me is:
{noformat}
Error on line 95, column 11 in path/to/template
cmsfn.link("dms", "/demo-docs/children/wizoz10") is undefined.
It cannot be assigned to dmsLink
The problematic instruction:
--
==> assignment: dmsLink=cmsfn.link("dms", "/demo-docs/children/wizoz10") [on
line 95, column 11 in path/to/template]
--
Java backtrace for programmers:
--
freemarker.core.InvalidReferenceException: Error on line 95, column 11 in
path/to/template
cmsfn.link("dms", "/demo-docs/children/wizoz10") is undefined.
It cannot be assigned to dmsLink
at freemarker.core.Assignment.accept(Assignment.java:111)
at freemarker.core.Environment.visit(Environment.java:221)
at freemarker.core.MixedContent.accept(MixedContent.java:92)
{noformat}
When downloading the source code I've found:
{noformat}
public String link(String workspace, String nodeIdentifier) {
try {
return LinkUtil.createLink(workspace, nodeIdentifier);
} catch (RepositoryException e) {
return null;
}
}
{noformat}
The real error "javax.jcr.RepositoryException: invalid identifier:
/demo-docs/children/wizoz10" was hidden from me because of this. I first
assumed that the method "link" was missing due to the error visible to me in
the log.
Better consistency for the error handling in this file would be appreciated.
Example:
{noformat}
public String link(String workspace, String nodeIdentifier) {
try {
return LinkUtil.createLink(workspace, nodeIdentifier);
} catch (RepositoryException e) {
log.error(e.getMessage(), e); // Print the real error in the log
return null;
}
}
{noformat}
Also I see other methods have the same problem, those should be updated as well.
--
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/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MAGNOLIA-4670) STK Templates making use of the PUR Form components cause spurious characters to be displayed on pages based upon those templates
STK Templates making use of the PUR Form components cause spurious characters to be displayed on pages based upon those templates -- Key: MAGNOLIA-4670 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4670 Project: Magnolia Issue Type: Bug Security Level: Public Components: templating, templating components Affects Versions: 4.5.3 Environment: Windows and *nix 4.5.3 community and enterprise Combination of STK and PUR form components apperars on a variety of versions of chrome - but tested on Version 23.0.1271.64 m Reporter: Jon Holmes Attachments: spurious characters.png When displaying a page that has been created using a combination of STK module, PUR module and Form module components, spurious characters are displayed on the page (typically after the tag has closed) If the page has a request parameter attached then the spurious characters are not displayed -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4669) Rendering any kind of image fails in the bundle
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Lipp updated MAGNOLIA-4669: -- Priority: Major (was: Neutral) > Rendering any kind of image fails in the bundle > --- > > Key: MAGNOLIA-4669 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4669 > Project: Magnolia > Issue Type: Bug > Security Level: Public >Affects Versions: 5.0 Alpha1 s008 >Reporter: Jan Haderka >Priority: Major > Fix For: 5.0 Alpha1 s009 > > Attachments: stacktrace.txt > > > See attached stacktrace for details. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLSTK-1025) Error when installing 2.0.6
[ http://jira.magnolia-cms.com/browse/MGNLSTK-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka updated MGNLSTK-1025: - Fix Version/s: 2.0.7 > Error when installing 2.0.6 > --- > > Key: MGNLSTK-1025 > URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1025 > Project: Magnolia Standard Templating Kit > Issue Type: Bug >Affects Versions: 2.0.6 >Reporter: Will Scheidegger > Fix For: 2.0.7 > > > When installing STK 2.0.6 on a fresh Magnolia 4.5.6 (no STK installed yet) I > get the following error message: > Could not install or update standard-templating-kit module. Task 'Move menu > Item' failed. (PathNotFoundException: > modules/adminInterface/config/menu/templates) > Without looking too closely at the code I would assume the problem occurs on > line 192 of STKModuleVersionHandler. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MAGNOLIA-4669) Rendering any kind of image fails in the bundle
Rendering any kind of image fails in the bundle --- Key: MAGNOLIA-4669 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4669 Project: Magnolia Issue Type: Bug Security Level: Public Affects Versions: 5.0 Alpha1 s008 Reporter: Jan Haderka Fix For: 5.0 Alpha1 s009 Attachments: stacktrace.txt See attached stacktrace for details. -- 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/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
