[magnolia-dev] [JIRA] Created: (MGNLMIGRATION-213) UpdateExtendsMigrationTask fails on relative paths
UpdateExtendsMigrationTask fails on relative paths -- Key: MGNLMIGRATION-213 URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-213 Project: Magnolia Migration Issue Type: Bug Affects Versions: 1.2 Reporter: Ondřej Chytil Fix For: 1.2.1 See linked support ticket 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4495) mainBar is always shown with properties button in author instance
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-4495: Fix Version/s: 4.5.8 (was: 4.5.x) mainBar is always shown with properties button in author instance -- Key: MAGNOLIA-4495 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4495 Project: Magnolia Issue Type: Bug Security Level: Public Components: page editor Affects Versions: 4.5.3 Reporter: Luca Boati Priority: Major Fix For: 4.5.8 In the author instance, if a user has read only access to a page, the green area bars and the green component bars are not displayed but the main bar is always shown with page properties edit option. Even though saving changes is forbidden, this option should be hidden. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-4718) Improve performance for SimpleUrlPattern
Improve performance for SimpleUrlPattern Key: MAGNOLIA-4718 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4718 Project: Magnolia Issue Type: Improvement Security Level: Public Components: security Affects Versions: 4.4.6 Reporter: Ondřej Chytil Assignee: Ondřej Chytil Fix For: 4.4.10 SimpleUrlPattern check takes more time now due to reflection calls made to determine site. This can be improved. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-4705) info.magnolia.cms.util.DelayedExecutorTest fails randomly
info.magnolia.cms.util.DelayedExecutorTest fails randomly - Key: MAGNOLIA-4705 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4705 Project: Magnolia Issue Type: Bug Security Level: Public Reporter: Ondřej Chytil Fix For: Backlog - Soon DelayedExecutorTest fails aparently due to timing of thread sleep (mostly just on hudson). Should be reviewed and fixed. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4639) Link API update
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-4639: Description: There is still some code refactoring needed in Link related classes (Link, LinkUtil...). - Code is not yet 100% converted to use Node/Property API. - Javadoc needs to be updated for deprecated methods. - Tests are still using expectation to old API. - Also few improvements of methods logic while handling with old API cases (NodeData/binary NodeData). was:There is still some code refactoring needed in Link related classes (Link, LinkUtil...). Link API update --- Key: MAGNOLIA-4639 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4639 Project: Magnolia Issue Type: Improvement Security Level: Public Affects Versions: 5.0 Alpha1 s008 Reporter: Ondřej Chytil Assignee: Ondřej Chytil Fix For: 5.0 Alpha1 s009 There is still some code refactoring needed in Link related classes (Link, LinkUtil...). - Code is not yet 100% converted to use Node/Property API. - Javadoc needs to be updated for deprecated methods. - Tests are still using expectation to old API. - Also few improvements of methods logic while handling with old API cases (NodeData/binary NodeData). -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSTK-1034) CLONE -Verify STK with improved links API
[ http://jira.magnolia-cms.com/browse/MGNLSTK-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MGNLSTK-1034: --- Fix Version/s: 2.5 Alpha1 s009 CLONE -Verify STK with improved links API - Key: MGNLSTK-1034 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1034 Project: Magnolia Standard Templating Kit Issue Type: Task Reporter: Ondřej Chytil Assignee: Ondřej Chytil Priority: Major Fix For: 2.5 Alpha1 s009 -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Reopened: (MAGNOLIA-4593) simultaneous activation of 1st and 2nd level page might cause failure to activate due incorrect locking
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil reopened MAGNOLIA-4593: - Bundle build is failing because of attempts of locking the root node. simultaneous activation of 1st and 2nd level page might cause failure to activate due incorrect locking --- Key: MAGNOLIA-4593 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4593 Project: Magnolia Issue Type: Bug Security Level: Public Components: activation Affects Versions: 4.4.8, 4.5.6 Reporter: Jan Haderka Assignee: Ondřej Chytil Priority: Blocker Fix For: 4.4.10, 4.5.7 When activating 1st level pages (home page) the root of the repo can't be locked and no JCR lock is issued for activation. If 2nd level page that exists under same path is activated at the same time, it would issue lock on the parent (1st level page) and thus lock it during the activation causing first activation to fail. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Reopened: (MGNLACTIVATION-3) CLONE -simultaneous activation of 1st and 2nd level page might cause failure to activate due incorrect locking
[ http://jira.magnolia-cms.com/browse/MGNLACTIVATION-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil reopened MGNLACTIVATION-3: Bundle build is failing because of attempts of locking the root node. CLONE -simultaneous activation of 1st and 2nd level page might cause failure to activate due incorrect locking -- Key: MGNLACTIVATION-3 URL: http://jira.magnolia-cms.com/browse/MGNLACTIVATION-3 Project: Magnolia Activation Module Issue Type: Bug Reporter: Jan Haderka Assignee: Ondřej Chytil Priority: Blocker Fix For: 5.0 Alpha1 s009 When activating 1st level pages (home page) the root of the repo can't be locked and no JCR lock is issued for activation. If 2nd level page that exists under same path is activated at the same time, it would issue lock on the parent (1st level page) and thus lock it during the activation causing first activation to fail. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLDMS-251) Update Link related tests
Update Link related tests - Key: MGNLDMS-251 URL: http://jira.magnolia-cms.com/browse/MGNLDMS-251 Project: Magnolia DMS Module Issue Type: Task Reporter: Ondřej Chytil Assignee: Ondřej Chytil Fix For: 1.7 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-4686) CLONE -simultaneous activation of 1st and 2nd level page might cause failure to activate due incorrect locking
CLONE -simultaneous activation of 1st and 2nd level page might cause failure to activate due incorrect locking -- Key: MAGNOLIA-4686 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4686 Project: Magnolia Issue Type: Bug Security Level: Public Components: activation Affects Versions: 4.4.8, 4.5.6 Reporter: Jan Haderka Assignee: Ondřej Chytil Priority: Blocker Fix For: 4.4.10, 4.5.7 When activating 1st level pages (home page) the root of the repo can't be locked and no JCR lock is issued for activation. If 2nd level page that exists under same path is activated at the same time, it would issue lock on the parent (1st level page) and thus lock it during the activation causing first activation to fail. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Reopened: (MAGNOLIA-4000) Update copyright to 2012
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil reopened MAGNOLIA-4000: - Some of classes in main project were not affected by script. Update copyright to 2012 Key: MAGNOLIA-4000 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4000 Project: Magnolia Issue Type: Task Security Level: Public Affects Versions: 3.5, 3.6, 4.0, 4.1, 4.2, 4.3, 4.4, 4.5 Reporter: Jan Haderka Assignee: Jan Haderka Fix For: 4.2.5, 4.1.7, 4.3.9, 4.4.10, 4.5.7 -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-4639) Link API update
Link API update --- Key: MAGNOLIA-4639 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4639 Project: Magnolia Issue Type: Improvement Security Level: Public Affects Versions: 5.0 Alpha1 s008 Reporter: Ondřej Chytil Assignee: Ondřej Chytil Fix For: 5.0 Alpha1 s009 There is still some code refactoring needed in Link related classes (Link, LinkUtil...). -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLIMG-100) Loading image from JCR using AbstractLoader will result in adding the alpha value as a color to generated JPGs
[
http://jira.magnolia-cms.com/browse/MGNLIMG-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondřej Chytil updated MGNLIMG-100:
--
Assignee: (was: Grégory Joseph)
Fix Version/s: 2.2.2
(was: 2.x)
Loading image from JCR using AbstractLoader will result in adding the alpha
value as a color to generated JPGs
--
Key: MGNLIMG-100
URL: http://jira.magnolia-cms.com/browse/MGNLIMG-100
Project: Magnolia Imaging Module
Issue Type: Bug
Components: image operations
Affects Versions: 2.2.1
Reporter: Christian Ringele
Priority: Critical
Fix For: 2.2.2
Attachments: AbstractLoader.java.patch, Generator.png,
OrigImage-PlacedIntoDMS.jpg, out1-works.png, out1-worksNot.jpg
Description:
Calling an image generator which uses a FromContent (extends AbstractLoader)
operation will result in wrong JPGs.
If storing PNGs it works fine. As PNGs have a alpha channel, the alpha value
is correctly applied.
Storing a JPG, it seems as the ImageIO.write() method writes the alpha value
as a color and not ignoring it as it should.
Reproduce:
1. Import the generator attached to this issue. Just containing one
operation, the load operation.
2. Add a test image to DMS.
3. execute this code with correct paths:
{code}
final ImagingModuleConfig config = (ImagingModuleConfig)
ModuleRegistry.Factory.getInstance().getModuleInstance(imaging);
final ImageGenerator generator =
config.getGenerators().get(myOperationChainBResize);
Session dmsSession = MgnlContext.getJCRSession(dms);
Node origImage = dmsSession.getNode(/test/orig);
final Content content =
info.magnolia.cms.util.ContentUtil.asContent(origImage);
final ParameterProviderContent parameterProvider = new
ContentParameterProvider(new SimpleEqualityContentWrapper(content));
final BufferedImage bufferedImage = generator.generate(parameterProvider);
ImageIO.write(bufferedImage, png, new
File(/Users/cringele/Documents/temp_stuff/image-test/create/out1-works.png));
ImageIO.write(bufferedImage, jpg, new
File(/Users/cringele/Documents/temp_stuff/image-test/create/out1-worksNot.jpg));
{code}
You can also write the stream back into JCR, the result is the same. So for
testing much easier into a file.
Source of the problem:
info.magnolia.imaging.operations.load.AbstractLoader.apply(BufferedImage, P)
{code}
if (source != null) {
throw new ImagingException(This operation currently does not support
overlaying images);
}
final BufferedImage loaded = loadSource(filterParams);
if (loaded == null) {
throw new ImagingException(Could not load image for + filterParams);
}
//This line is the source of the problem. Using BufferedImage.TYPE_INT_RGB
would work because it wouldn't contain any alpha channel. Of course just for
testing applicable.
final BufferedImage img = new BufferedImage(loaded.getWidth(),
loaded.getHeight(), BufferedImage.TYPE_INT_ARGB_PRE);
final Graphics2D g = img.createGraphics();
if (backgroundColor != null) {
g.setColor(backgroundColor);
g.fill(new Rectangle(0, 0, img.getWidth(), img.getHeight()));
}
g.drawImage(loaded, null, 0, 0);
// TODO would this make any difference ? g.drawRenderedImage(loaded, null);
g.dispose();
return img;
{code}
Proof of the problem source:
First possibility: Execute this code just passing back the loaded
BufferedImage
{code}
if (source != null) {
throw new ImagingException(This operation currently does not support
overlaying images);
}
final BufferedImage loaded = loadSource(filterParams);
if (loaded == null) {
throw new ImagingException(Could not load image for + filterParams);
}
return loaded;
{code}
Second possibility: Pass back the created BufferedImage (img) withour loagin
the orig image on top.
Like this you can compare alpha value in PNG to color in JPG.
{code}
if (source != null) {
throw new ImagingException(This operation currently does not support
overlaying images);
}
final BufferedImage loaded = loadSource(filterParams);
if (loaded == null) {
throw new ImagingException(Could not load image for + filterParams);
}
final BufferedImage img = new BufferedImage(loaded.getWidth(),
loaded.getHeight(), BufferedImage.TYPE_INT_ARGB_PRE);
final Graphics2D g = img.createGraphics();
if (backgroundColor != null) {
g.setColor(backgroundColor);
g.fill(new Rectangle(0, 0, img.getWidth(), img.getHeight()));
}
//Image not loaded on top of it
//g.drawImage(loaded, null, 0, 0);
// TODO would this make any difference ? g.drawRenderedImage(loaded, null);
g.dispose();
return img;
{code}
It seems to be a known problem:
[magnolia-dev] [JIRA] Reopened: (MAGNOLIA-4555) Skip site-aware check on author instance
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil reopened MAGNOLIA-4555: - Skip site-aware check on author instance Key: MAGNOLIA-4555 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4555 Project: Magnolia Issue Type: Improvement Security Level: Public Components: security Reporter: Ondřej Chytil Assignee: Ondřej Chytil Site-aware check on author instance makes unnecessary calls and should be skipped. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4589) Improve security API to allow testing arbitrary user's permissions
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondřej Chytil updated MAGNOLIA-4589:
Fix Version/s: 5.0
Hi Thomas,
thanks for handy idea. Should be implemented as part of Magnolia 5.0.
Improve security API to allow testing arbitrary user's permissions
--
Key: MAGNOLIA-4589
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4589
Project: Magnolia
Issue Type: Improvement
Security Level: Public
Components: security
Affects Versions: 4.5.3
Reporter: Tomas Brimor
Priority: Major
Fix For: 5.0
The security API should allow you to test an arbitrary user's permissons
against a specific Magnolia resource. As it is now only the logged in user as
found in the context is accessible for permission testing.
Example of pseudo usage:
{code}
workspace = someworkspace
path = /path/to/a/node
node = NodeUtil.getNode(workspace, path)
userName = myuser
userObj = Security.getUser(userName)
hasPermission = Security.isGranted(userObj, node, Permission.READ)
{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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4386) FCKeditor doesn't work correctly in IE9
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondřej Chytil updated MAGNOLIA-4386:
Fix Version/s: 4.5.7
(was: 4.5.x)
FCKeditor doesn't work correctly in IE9
---
Key: MAGNOLIA-4386
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4386
Project: Magnolia
Issue Type: Bug
Security Level: Public
Environment: Internet explorer 9
Reporter: Roman Milos
Fix For: 4.5.7
Attachments: fckdialog.diff
We currently using FCKeditor 2.6.6. However this version doesn't work well
with internet explorer 9. Most of buttons which creates pop-up windows
doesn't work in ie9 (paste, flash, image, etc.) and no pop-up window is
showed or only empty pop-up is showed and fckeditor freeze.
According CKeditor official pages this version of FCKeditor isn't supported
and to fix problem is suggested update to new version CKeditor 3.x (atleast
3.5.2 which added ie9 support). So we should update to later version where
this problem are fixed.
As workaround in ie9 is possible add to head of pages:
{{meta http-equiv=X-UA-Compatible content=IE=EmulateIE8 /}}
this cause changing of rendering engine in ie9 to ie8 where FCKeditor work
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4481) Core: LinkUtil should be refactored for use with Node type
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-4481: Assignee: Ondřej Chytil Fix Version/s: 5.0 (was: 4.5.x) Core: LinkUtil should be refactored for use with Node type -- Key: MAGNOLIA-4481 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4481 Project: Magnolia Issue Type: Bug Security Level: Public Components: core Reporter: Christian Ringele Assignee: Ondřej Chytil Fix For: 5.0 Attachments: nodeBasedLink-patch-2.txt -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3395) MgnlMailFactory NPE when passing an erroneous template name
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-3395: Fix Version/s: 4.3.9 (was: 4.3.x) MgnlMailFactory NPE when passing an erroneous template name --- Key: MAGNOLIA-3395 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3395 Project: Magnolia Issue Type: Bug Security Level: Public Components: mail Reporter: Grégory Joseph Assignee: Ondřej Chytil Priority: Major Fix For: 4.3.9, 4.4 Attachments: MAGNOLIA-3395.txt When a command attempts to send an email with an erroneous template name, a NullPointerException is thrown, with no indication of the actual problem. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3479) ContentUtil: orderAfter does not work propertly
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-3479: Fix Version/s: 4.3.9 (was: 4.3.x) ContentUtil: orderAfter does not work propertly --- Key: MAGNOLIA-3479 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3479 Project: Magnolia Issue Type: Bug Security Level: Public Components: core Affects Versions: 4.3.8, 4.4.1 Reporter: Christian Ringele Assignee: Ondřej Chytil Priority: Major Fix For: 4.3.9, 4.4.2, 4.5 Attachments: ContentUtilTest.java.patch, ContentUtilTest.java.patch2 The algorithm can't work, it just orders all nodes in front of the 'nodeToMove' until the 'targetNodeName' is in front. But that can't work in most cases (at least when there is more than three nodes as in the existing textcase). I created a patch with test cases, all these should work properly (ContentUtilTest.java.patch). While testing the orderAfter i tested the orderBefore too. The orderBefore works fine, still adding a patch here, so the test cases (no cases there yet) can be addedtested at the same time (ContentUtilTest.java.patch2). -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3458) Dialog checkboxSwitch not saved (i18n enabled)
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-3458: Fix Version/s: 4.3.9 (was: 4.3.x) Dialog checkboxSwitch not saved (i18n enabled) -- Key: MAGNOLIA-3458 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3458 Project: Magnolia Issue Type: Bug Security Level: Public Components: admininterface Affects Versions: 4.4.1 Environment: http://demoauthor.magnolia-cms.com/demo-project/de/about/subsection-articles/ncaTest.html?mgnlCK=1291995819484 Local (Tomcat 6, Eclipse WTP, magnolia-empty-webapp) Reporter: Marco Glur Assignee: Ondřej Chytil Fix For: 4.3.9, 4.4.2, 4.5 Attachments: config.modules.standard-templating-kit.dialogs.paragraphs.content.ncaDialog.xml When I add a new Paragraph (ncaTest) having a Dialog with two i18n-enabled checkboxSwitch controls, they just are set initially (on first save of the dialog) for each language and need to be set using the JCR browser afterwards. So, unchecking/checking the checkbox does not impact the JCR content AND the opening of the Dialog at a later time. Problem was encountered in my local setup (Eclipse IDE) and could be reproduced on demoauthor: http://demoauthor.magnolia-cms.com/demo-project/de/about/subsection-articles/ 1. add new dialog (attachment ncaDialog.xml) 2. copy a paragraph and set its dialog to the new created from xml. 3. add paragraph to an area and edit, change values, save and check. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3347) Security Improvement: User accounts are testable
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-3347: Fix Version/s: 4.3.9 (was: 4.3.x) Security Improvement: User accounts are testable Key: MAGNOLIA-3347 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3347 Project: Magnolia Issue Type: Improvement Security Level: Public Components: admininterface Reporter: Martin Ruf Assignee: Ondřej Chytil Priority: Major Fix For: 4.3.9, 4.4 Original Estimate: 1h Remaining Estimate: 1h User accounts can be tested very easily, there are three (or more) different error messages when login fails: - user deactivated - wrong password - user does not exist Knowing valid user accounts can be used as a basis for brute force attacks, a generic error message should be shown (login failed or something like that). -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-2820) Backend with HTTPS - warning in IE7
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-2820: Fix Version/s: 4.3.9 4.4 (was: 4.3.x) Backend with HTTPS - warning in IE7 --- Key: MAGNOLIA-2820 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2820 Project: Magnolia Issue Type: Bug Security Level: Public Components: admininterface Affects Versions: 3.6.3 Reporter: Rainer Blumenthal Assignee: Ondřej Chytil Priority: Major Fix For: 4.3.9, 4.4 Attachments: IE6-patch.patch, Navigation.java, Navigation.js, Navigation.patch If you access the Magnolia Backend with HTTPS using an IE Browser: u get this warning: This page containsd secure and non-secure items... http://farm3.static.flickr.com/2263/2330340408_63a47989da.jpg?v=0 If you look here: http://weblogs.asp.net/rchartier/archive/2008/03/12/ie7-this-page-contains-both-secure-and-nonsecure-items.aspx somebody seems to have found the cause. The Magnolia Backend seems to use an iframe without src attribute - the src attribute is then set by JS. But on page-load the IE interpretes this as unsecure. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3146) Update to log4j 1.2.16 asap
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondřej Chytil updated MAGNOLIA-3146:
Fix Version/s: 4.3.9
(was: 4.3.x)
Update to log4j 1.2.16 asap
---
Key: MAGNOLIA-3146
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3146
Project: Magnolia
Issue Type: Task
Security Level: Public
Components: build, core
Reporter: Grégory Joseph
Assignee: Ondřej Chytil
Priority: Major
Fix For: 4.3.9, 4.4
Everynow and then, we get these in logs:
{noformat}java.lang.NullPointerException
at java.io.Writer.write(Writer.java:126)
at org.apache.log4j.helpers.QuietWriter.write(QuietWriter.java:48)
at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:309)
at org.apache.log4j.WriterAppender.append(WriterAppender.java:160)
at
org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:251)
at
org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:66)
at org.apache.log4j.Category.callAppenders(Category.java:206)
at org.apache.log4j.Category.forcedLog(Category.java:391)
at org.apache.log4j.Category.log(Category.java:856)
at
org.slf4j.impl.Log4jLoggerAdapter.error(Log4jLoggerAdapter.java:571)
{noformat}
This is this issue: https://issues.apache.org/bugzilla/show_bug.cgi?id=44032
It's apparently been fixed for a while, but 1.2.16 was never released;
however, there seems to be a fairly recent (1 month old) [RC1
tag|http://svn.apache.org/viewvc/logging/log4j/tags/v1_2_16_rc1] so all hope
is not lost !
Another, slightly longer-term, option would be to switch to
[logback|http://logback.qos.ch].
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3013) Moving paragraphs using edit bars not working properly in Internet Explorer (IE7 / IE8)
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-3013: Fix Version/s: 4.2.5 (was: 4.2.x) Moving paragraphs using edit bars not working properly in Internet Explorer (IE7 / IE8) --- Key: MAGNOLIA-3013 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3013 Project: Magnolia Issue Type: Bug Security Level: Public Components: gui Affects Versions: 4.2.3 Environment: Internet Explorer 7.0 and 8.0 under Windows. Reporter: Hay Kranen Assignee: Ondřej Chytil Priority: Critical Fix For: 4.2.5, 4.3.3 Attachments: general.patch, general2.patch When moving paragraphs using the 'move' button a bug occurs in both IE7 and IE8. The green bar is floating approximately 150 pixels higher than were the mouse cursor is, in some cases it's completely invisible. In Firefox / Safari the bar is located where you expect it to be, right next to the mouse cursor. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4560) Use system context also for destination node during restore
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-4560: Fix Version/s: 4.5.7 (was: 4.5.6) Use system context also for destination node during restore --- Key: MAGNOLIA-4560 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4560 Project: Magnolia Issue Type: Bug Security Level: Public Components: core Affects Versions: 4.5 Reporter: Jan Haderka Assignee: Philipp Bärfuss Fix For: 4.5.7 JR 2.4.x will use session context of the destination to also check for read permission from the source during cloning. Ordinary user is never allowed read from version store directly hence the check fails. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSTK-1008) Area of type single allows a list of components to be added actually
[ http://jira.magnolia-cms.com/browse/MGNLSTK-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MGNLSTK-1008: --- Fix Version/s: 2.0.7 (was: 2.0.6) Area of type single allows a list of components to be added actually Key: MGNLSTK-1008 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1008 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: paragraphs, templates Affects Versions: 2.0.4 Reporter: Zdenek Skodik Assignee: Roman Kovařík Priority: Major Fix For: 2.0.7 -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4568) Cache temp files are not cleared out in case of failure while rendering the content
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-4568: Fix Version/s: 4.5.7 (was: 4.5.6) Cache temp files are not cleared out in case of failure while rendering the content --- Key: MAGNOLIA-4568 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4568 Project: Magnolia Issue Type: Bug Security Level: Public Components: cache Affects Versions: 4.4.6 Reporter: Jan Haderka Fix For: 4.4.10, 4.5.7 -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3821) magnolia gzip compressed cache sometimes produces hieroglyphics on user browser
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-3821: Fix Version/s: 4.5.7 (was: 4.5.6) magnolia gzip compressed cache sometimes produces hieroglyphics on user browser --- Key: MAGNOLIA-3821 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3821 Project: Magnolia Issue Type: Bug Security Level: Public Components: cache Affects Versions: 4.4.4 Environment: Linux RH 5.7 + Tomcat 6.0.32 + Apache 2.2.19 (ajp) Reporter: Damiano Bianchi Priority: Critical Fix For: 4.4.x, 4.5.7 Attachments: Screen shot 2012-05-15 at 11.52.17.png After upgrading magnolia 4.3.8 to magnolia 4.4.4 we noticed that if a user refresh a page on the browser sometimes she receives a malformed page or hieroglyphics. After a long analysis we discovered that: - the malformed page is caused by a css that is transmitted to the browsers compressed with gzip instead of plain text. Using a sniffer we notices that the server, when send the compressed content to the browser, don't set a content encoding header. - the hieroglyphics are a the html page compressed sent to the browser as plain text All works fine if the user browse the page bypassing apache, directly to tomcat on port 8080. To solve this issue we deleted all nodes under: modules/cache/config/compression/voters/content type/allowed Best regards, Damiano -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4566) Moving of components in extras column does not work - write selenium test
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondřej Chytil updated MAGNOLIA-4566:
Fix Version/s: 4.5.7
(was: 4.5.6)
Moving of components in extras column does not work - write selenium test
-
Key: MAGNOLIA-4566
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4566
Project: Magnolia
Issue Type: Bug
Security Level: Public
Components: page editor
Affects Versions: 4.5.5
Reporter: Frank Sommer
Assignee: Milan Divilek
Priority: Major
Fix For: 4.5.7
If I have a inherit component in the extras column, the movement of
components in the extras column does not work. But without an inherit
component it works. I could reproduce this on your demoauthor instance.
Following java script error occures, if I want to move a component:
{{uncaught exception: com.google.gwt.event.shared.UmbrellaException: One or
more exceptions caught, see full set in UmbrellaException#getCauses}}
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSTK-1009) Extends:override doesn't work as expected
[ http://jira.magnolia-cms.com/browse/MGNLSTK-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MGNLSTK-1009: --- Fix Version/s: 2.0.7 (was: 2.0.6) Extends:override doesn't work as expected - Key: MGNLSTK-1009 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1009 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: paragraphs, templates Affects Versions: 2.0.4 Reporter: Zdenek Skodik Fix For: 2.0.7 The use case is quite simple: * child site definition extends a parent, and overrides parts of areas, i.e. availableComponents * child page template definition extends a parent, and overrides parts of areas, i.e. availableComponents * these child definitions get merged and you end up with both lists of components to choose from, however one would expect to end up just with those defined on the page template definition level like usually -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4562) Write integration test for workflow activate versioned state not current state
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-4562: Fix Version/s: 4.5.7 (was: 4.5.6) Write integration test for workflow activate versioned state not current state -- Key: MAGNOLIA-4562 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4562 Project: Magnolia Issue Type: Task Security Level: Public Affects Versions: 4.5.5 Reporter: Milan Divilek Assignee: Milan Divilek Priority: Major Fix For: 4.5.7 -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLFORM-133) formGroupEdit component: allow horizontal nesting of inner input fields again
[ http://jira.magnolia-cms.com/browse/MGNLFORM-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MGNLFORM-133: --- Fix Version/s: 1.4.4 formGroupEdit component: allow horizontal nesting of inner input fields again - Key: MGNLFORM-133 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-133 Project: Magnolia Form Module Issue Type: Bug Affects Versions: 1.4 Reporter: Zdenek Skodik Fix For: 1.4.4 We say that the component groups text fields on the same line. That's right, at least up until Magnolia CMS 4.5 where the divIDs assigned (form-item-s/m/l) don't support that anymore. Similarly it doesn't matter whether you define the input fields to be small/medium/long, they're always rendered with identical length. The css should be updated accordingly. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSTK-1008) Area of type single allows a list of components to be added actually
[ http://jira.magnolia-cms.com/browse/MGNLSTK-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MGNLSTK-1008: --- Fix Version/s: 2.0.6 (was: 2.0.x) Area of type single allows a list of components to be added actually Key: MGNLSTK-1008 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1008 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: paragraphs, templates Affects Versions: 2.0.4 Reporter: Zdenek Skodik Priority: Major Fix For: 2.0.6 -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSTK-1009) Extends:override doesn't work as expected
[ http://jira.magnolia-cms.com/browse/MGNLSTK-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MGNLSTK-1009: --- Fix Version/s: 2.0.6 Extends:override doesn't work as expected - Key: MGNLSTK-1009 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1009 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: paragraphs, templates Affects Versions: 2.0.4 Reporter: Zdenek Skodik Fix For: 2.0.6 The use case is quite simple: * child site definition extends a parent, and overrides parts of areas, i.e. availableComponents * child page template definition extends a parent, and overrides parts of areas, i.e. availableComponents * these child definitions get merged and you end up with both lists of components to choose from, however one would expect to end up just with those defined on the page template definition level like usually -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-4555) Skip site-aware check on author instance
Skip site-aware check on author instance Key: MAGNOLIA-4555 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4555 Project: Magnolia Issue Type: Improvement Security Level: Public Components: security Reporter: Ondřej Chytil Assignee: Ondřej Chytil Fix For: 4.4.10 Site-aware check on author instance makes unnecessary calls and should be skipped. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-4534) CLONE -When navigations are moved in an area their links are no more clickable in edit mode, we must switch to the preview mode if we want to navigate.
CLONE -When navigations are moved in an area their links are no more clickable
in edit mode, we must switch to the preview mode if we want to navigate.
---
Key: MAGNOLIA-4534
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4534
Project: Magnolia
Issue Type: Improvement
Security Level: Public
Components: page editor
Affects Versions: 4.5
Reporter: Samuel Schmitt
Assignee: Ondřej Chytil
Fix For: 4.5.5
Attachments: pageeditor.patch
It's a pain to always switch to the preview mode when we want to click on a
navigation item.
It be great if all the links wrapped in an element with an attribute
{{role=navigation}} stay clickable in the edit mode.
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-4535) CLONE -When navigations are moved in an area their links are no more clickable in edit mode, we must switch to the preview mode if we want to navigate.
CLONE -When navigations are moved in an area their links are no more clickable
in edit mode, we must switch to the preview mode if we want to navigate.
---
Key: MAGNOLIA-4535
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4535
Project: Magnolia
Issue Type: Improvement
Security Level: Public
Components: page editor
Affects Versions: 4.5
Reporter: Samuel Schmitt
Assignee: Ondřej Chytil
Fix For: 4.5.5
Attachments: pageeditor.patch
It's a pain to always switch to the preview mode when we want to click on a
navigation item.
It be great if all the links wrapped in an element with an attribute
{{role=navigation}} stay clickable in the edit mode.
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLUI-9) CLONE -When navigations are moved in an area their links are no more clickable in edit mode, we must switch to the preview mode if we want to navigate.
[
http://jira.magnolia-cms.com/browse/MGNLUI-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondřej Chytil updated MGNLUI-9:
---
Fix Version/s: 5.0
Affects Version/s: (was: 5.0)
CLONE -When navigations are moved in an area their links are no more
clickable in edit mode, we must switch to the preview mode if we want to
navigate.
---
Key: MGNLUI-9
URL: http://jira.magnolia-cms.com/browse/MGNLUI-9
Project: Magnolia UI
Issue Type: Improvement
Security Level: Public
Components: editor
Reporter: Samuel Schmitt
Assignee: Ondřej Chytil
Fix For: 5.0
Attachments: pageeditor.patch
It's a pain to always switch to the preview mode when we want to click on a
navigation item.
It be great if all the links wrapped in an element with an attribute
{{role=navigation}} stay clickable in the edit mode.
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLTPLSMPL-2) CLONE -When navigations are moved in an area their links are no more clickable in edit mode, we must switch to the preview mode if we want to navigate.
[
http://jira.magnolia-cms.com/browse/MGNLTPLSMPL-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondřej Chytil updated MGNLTPLSMPL-2:
Summary: CLONE -When navigations are moved in an area their links are no
more clickable in edit mode, we must switch to the preview mode if we want to
navigate. Port to 5.0 (was: CLONE -When navigations are moved in an area their
links are no more clickable in edit mode, we must switch to the preview mode if
we want to navigate.)
Assignee: (was: Ondřej Chytil)
CLONE -When navigations are moved in an area their links are no more
clickable in edit mode, we must switch to the preview mode if we want to
navigate. Port to 5.0
---
Key: MGNLTPLSMPL-2
URL: http://jira.magnolia-cms.com/browse/MGNLTPLSMPL-2
Project: Magnolia Templating Samples
Issue Type: Improvement
Reporter: Samuel Schmitt
Fix For: 5.0
Attachments: pageeditor.patch
It's a pain to always switch to the preview mode when we want to click on a
navigation item.
It be great if all the links wrapped in an element with an attribute
{{role=navigation}} stay clickable in the edit mode.
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLUI-9) CLONE -When navigations are moved in an area their links are no more clickable in edit mode, we must switch to the preview mode if we want to navigate. Port
[
http://jira.magnolia-cms.com/browse/MGNLUI-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondřej Chytil updated MGNLUI-9:
---
Summary: CLONE -When navigations are moved in an area their links are no
more clickable in edit mode, we must switch to the preview mode if we want to
navigate. Port to 5.0 (was: CLONE -When navigations are moved in an area their
links are no more clickable in edit mode, we must switch to the preview mode if
we want to navigate.)
Assignee: (was: Ondřej Chytil)
CLONE -When navigations are moved in an area their links are no more
clickable in edit mode, we must switch to the preview mode if we want to
navigate. Port to 5.0
---
Key: MGNLUI-9
URL: http://jira.magnolia-cms.com/browse/MGNLUI-9
Project: Magnolia UI
Issue Type: Improvement
Security Level: Public
Components: editor
Reporter: Samuel Schmitt
Fix For: 5.0
Attachments: pageeditor.patch
It's a pain to always switch to the preview mode when we want to click on a
navigation item.
It be great if all the links wrapped in an element with an attribute
{{role=navigation}} stay clickable in the edit mode.
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3821) magnolia gzip compressed cache sometimes produces hieroglyphics on user browser
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-3821: Fix Version/s: 4.5.5 (was: 4.5.x) magnolia gzip compressed cache sometimes produces hieroglyphics on user browser --- Key: MAGNOLIA-3821 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3821 Project: Magnolia Issue Type: Bug Security Level: Public Components: cache Affects Versions: 4.4.4 Environment: Linux RH 5.7 + Tomcat 6.0.32 + Apache 2.2.19 (ajp) Reporter: Damiano Bianchi Priority: Critical Fix For: 4.4.x, 4.5.5 Attachments: Screen shot 2012-05-15 at 11.52.17.png After upgrading magnolia 4.3.8 to magnolia 4.4.4 we noticed that if a user refresh a page on the browser sometimes she receives a malformed page or hieroglyphics. After a long analysis we discovered that: - the malformed page is caused by a css that is transmitted to the browsers compressed with gzip instead of plain text. Using a sniffer we notices that the server, when send the compressed content to the browser, don't set a content encoding header. - the hieroglyphics are a the html page compressed sent to the browser as plain text All works fine if the user browse the page bypassing apache, directly to tomcat on port 8080. To solve this issue we deleted all nodes under: modules/cache/config/compression/voters/content type/allowed Best regards, Damiano -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-4526) Disable site-aware ACL check for author instance
Disable site-aware ACL check for author instance Key: MAGNOLIA-4526 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4526 Project: Magnolia Issue Type: Improvement Security Level: Public Components: security Affects Versions: 4.4.9 Reporter: Ondřej Chytil Fix For: 4.4.10 Site-aware ACL check has no use on author instance and is slowing performance thus should be allowed only on public. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4511) MultiSelect does not keep the order of its value items (NodeDatas)
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondřej Chytil updated MAGNOLIA-4511:
Assignee: (was: Philipp Bärfuss)
Fix Version/s: 4.5.5
That helped, thanks Will. Added for current changelog.
MultiSelect does not keep the order of its value items (NodeDatas)
--
Key: MAGNOLIA-4511
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4511
Project: Magnolia
Issue Type: Bug
Security Level: Public
Components: admininterface
Affects Versions: 4.4.6
Reporter: Will Scheidegger
Fix For: 4.5.5
Attachments: multiSelect.patch, Screen Shot 2012-08-27 at
12.16.34.png, Screen Shot 2012-08-27 at 12.16.49.png, Screen Shot 2012-08-27
at 12.17.02.png
Original Estimate: 1h
Remaining Estimate: 1h
If you use the multiSelect control in a dialog to select three nodes A, B and
C, Magnolia will correctly save something like
- myMultiValueNode
-- 0: A
-- 1: B
-- 2: C
But when you open the dialog the next time, chances are that the order will
not be correct anymore. You save again and the order will now also be messed
up in the repository. I don't know exactly why this is happening, but it
boils down to Content.getNodeDataCollection() not returning the nodes in the
proper order.
However this is easily fixed: Simply sort the NodeDatas by name when
retrieved from the Content object:
ArrayListNodeData nodeDatas = new
ArrayListNodeData(this.getStorageNode().getContent(this.getName()).getNodeDataCollection());
Collections.sort(nodeDatas, new Comparator() {
@Override
public int compare(Object arg0, Object arg1) {
return ((NodeData) arg0).getName().compareTo(((NodeData)
arg1).getName());
}
});
Iterator it = nodeDatas.iterator();
...
The attached patch does exactly this.
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Reopened: (MAGNOLIA-4514) Workflow doesn't release session correctly after manipulation expressions
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil reopened MAGNOLIA-4514: - Port to 5.0 is remaining. Workflow doesn't release session correctly after manipulation expressions - Key: MAGNOLIA-4514 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4514 Project: Magnolia Issue Type: Bug Security Level: Public Components: workflow Affects Versions: 4.5 Reporter: Jan Haderka Assignee: Ondřej Chytil Fix For: 4.5.5 Since 4.5 some ops are executed in SystemContext, so it is necessary for workflow to take care of the fact and make sure that in threads it creates for execution all context is released properly. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-4517) Search results not i18n wrapped
Search results not i18n wrapped --- Key: MAGNOLIA-4517 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4517 Project: Magnolia Issue Type: Bug Security Level: Public Components: i18n Reporter: Ondřej Chytil Fix For: 4.5.5 Results provided by search are presented in default locale. To reproduce: - Switch to german - Add a german title and abstract for Home/About/Articles/Standard Article - Search for a german word -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4508) User manager is not handling removing (roles, groups) correctly
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondřej Chytil updated MAGNOLIA-4508:
Fix Version/s: (was: 5.0)
User manager is not handling removing (roles, groups) correctly
---
Key: MAGNOLIA-4508
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4508
Project: Magnolia
Issue Type: Bug
Security Level: Public
Components: security
Reporter: Ondřej Chytil
Assignee: Ondřej Chytil
Priority: Major
Fix For: 4.5.5
Delegating user manager is calling remove methods in
{{delegateUntilSupported}} which will call the method on first UM regardless
if the user exists under it.
Another issue - base {{RepositoryBackedSecurityManager.remove}} method is
called in SystemContext. Current context should be used instead to respect
permissions.
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSTK-998) Sub components of inherited components should not have a component bar.
[ http://jira.magnolia-cms.com/browse/MGNLSTK-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MGNLSTK-998: -- Fix Version/s: 2.0.5 Thanks for reporting the issue Diana, added to current changelog. Sub components of inherited components should not have a component bar. --- Key: MGNLSTK-998 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-998 Project: Magnolia Standard Templating Kit Issue Type: Bug Components: templates Affects Versions: 2.0.2 Reporter: Diana Racho Fix For: 2.0.5 Also the sub area of inherited components should not have an area bar. Reproduce - Go on demo instance - Add a link list to extras area and choose Show in subpage - Add same links to this list - Go to sub page and click on one of the links = the component bar of this link and the area bar of the link list will be shown -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLSTK-991) Site security handling
Site security handling -- Key: MGNLSTK-991 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-991 Project: Magnolia Standard Templating Kit Issue Type: Improvement Reporter: Ondřej Chytil Assignee: Ondřej Chytil Priority: Major Fix For: 2.0.5 [Concept page|http://wiki.magnolia-cms.com/display/DEV/Site+security+handling] is suggesting URISecurityFilter should be extended to respect site security and prevent cross-site access. This filter should replace URISecurityFilter when STK is installed and is part of port/improve site-aware ACL - MAGNOLIA-3914. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-4508) User manager is not handling removing (roles, groups) correctly
User manager is not handling removing (roles, groups) correctly
---
Key: MAGNOLIA-4508
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4508
Project: Magnolia
Issue Type: Bug
Security Level: Public
Components: security
Reporter: Ondřej Chytil
Assignee: Ondřej Chytil
Priority: Major
Fix For: 4.5.5
Delegating user manager is calling remove methods in {{delegateUntilSupported}}
which will call the method on first UM regardless if the user exists under it.
Another issue - base {{RepositoryBackedSecurityManager.remove}} method is
called in SystemContext. Current context should be used instead to respect
permissions.
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4386) FCKeditor doesn't work correctly in IE9
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondřej Chytil updated MAGNOLIA-4386:
Fix Version/s: 4.5.5
FCKeditor doesn't work correctly in IE9
---
Key: MAGNOLIA-4386
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4386
Project: Magnolia
Issue Type: Bug
Security Level: Public
Environment: Internet explorer 9
Reporter: Roman Milos
Fix For: 4.5.5
Attachments: fckdialog.diff
We currently using FCKeditor 2.6.6. However this version doesn't work well
with internet explorer 9. Most of buttons which creates pop-up windows
doesn't work in ie9 (paste, flash, image, etc.) and no pop-up window is
showed or only empty pop-up is showed and fckeditor freeze.
According CKeditor official pages this version of FCKeditor isn't supported
and to fix problem is suggested update to new version CKeditor 3.x (atleast
3.5.2 which added ie9 support). So we should update to later version where
this problem are fixed.
As workaround in ie9 is possible add to head of pages:
{{meta http-equiv=X-UA-Compatible content=IE=EmulateIE8 /}}
this cause changing of rendering engine in ie9 to ie8 where FCKeditor work
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4495) mainBar is always shown with properties button in author instance
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-4495: Summary: mainBar is always shown with properties button in author instance (was: mainBar is always shown in author instance ) Description: In the author instance, if a user has read only access to a page, the green area bars and the green component bars are not displayed but the main bar is always shown with page properties edit option. Even though saving changes is forbidden, this option should be hidden. (was: In the author instance, if a user has read only access to a page, the green area bars and the green component bars are not displayed but the main bar is always shown.) mainBar is always shown with properties button in author instance -- Key: MAGNOLIA-4495 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4495 Project: Magnolia Issue Type: Bug Security Level: Public Components: page editor Affects Versions: 4.5.3 Reporter: Luca Boati Priority: Major Fix For: 4.5.5 In the author instance, if a user has read only access to a page, the green area bars and the green component bars are not displayed but the main bar is always shown with page properties edit option. Even though saving changes is forbidden, this option should be hidden. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLPUR-69) Provide a way to change password without sending it as plain text
Provide a way to change password without sending it as plain text - Key: MGNLPUR-69 URL: http://jira.magnolia-cms.com/browse/MGNLPUR-69 Project: Magnolia Public User Registration Issue Type: Improvement Reporter: Ondřej Chytil Fix For: 1.4.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLPUR-69) Provide a way to change password without sending it as plain text
[ http://jira.magnolia-cms.com/browse/MGNLPUR-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MGNLPUR-69: - Priority: Major (was: Neutral) Provide a way to change password without sending it as plain text - Key: MGNLPUR-69 URL: http://jira.magnolia-cms.com/browse/MGNLPUR-69 Project: Magnolia Public User Registration Issue Type: Improvement Reporter: Ondřej Chytil Priority: Major Fix For: 1.4.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4495) mainBar is always shown in author instance
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-4495: Fix Version/s: 4.5.5 Thanks for reporting the issue Luca. Confirmed and added to current changelog. mainBar is always shown in author instance --- Key: MAGNOLIA-4495 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4495 Project: Magnolia Issue Type: Bug Security Level: Public Components: page editor Affects Versions: 4.5.3 Reporter: Luca Boati Priority: Major Fix For: 4.5.5 In the author instance, if a user has read only access to a page, the green area bars and the green component bars are not displayed but the main bar is always shown. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4496) Nodes marked deleted have no icons in templates workspace
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondřej Chytil updated MAGNOLIA-4496:
Assignee: (was: Philipp Bärfuss)
Fix Version/s: 4.5.5
Priority: Trivial (was: Minor)
Description:
If you configure the MarkNodeAsDeletedCommand for the templates workspace,
things generally work as expected, but the marked deleted nodes are displayed
without an icon.
It seems to me that this problem could be solved generally by adding an icon
for the node-type mgnl:deleted in the constructor for
info.magnolia.cms.gui.control.Tree
was:
If you configure the MarkNodeAsDeletedCommand for the templates workspace,
things generally work as expected, but the marked deleted nodes are displayed
without an icon.
It seems to me that this problem could be solved generally by adding an icon
for the node-type mgnl:deleted in the constructor for
info.magnolia.cms.gui.control.Tree
Added to changelog.
As workaround
{noformat}
tree.addIcon(ItemType.DELETED_NODE_MIXIN, /path/to/document_deleted.gif);
{noformat}
can be added to
{{info.magnolia.module.inplacetemplating.InplaceTemplatingAdminTreeConfig.prepareTree()}}
or any other {{AbstractTreeConfiguration}} based class.
Nodes marked deleted have no icons in templates workspace
---
Key: MAGNOLIA-4496
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4496
Project: Magnolia
Issue Type: Bug
Security Level: Public
Components: admininterface
Affects Versions: 4.4.8
Environment: 4.4.8 EE
Reporter: Richard Unger
Priority: Trivial
Fix For: 4.5.5
If you configure the MarkNodeAsDeletedCommand for the templates workspace,
things generally work as expected, but the marked deleted nodes are displayed
without an icon.
It seems to me that this problem could be solved generally by adding an icon
for the node-type mgnl:deleted in the constructor for
info.magnolia.cms.gui.control.Tree
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4434) Revive taglibs or provide other way to archieve their functionality
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondřej Chytil updated MAGNOLIA-4434:
Summary: Revive taglibs or provide other way to archieve their
functionality (was: Support for (XPath) queries in the taglibs?)
Description:
Since we are dropping support of compatibility modules there have to be
replacement for functions provided by those modules.
[Tag migration
page|http://wiki.magnolia-cms.com/display/DEV/Tags+migration+for+4.5] contains
detailed info for every tag.
was:
As mentioned in SUPPORT-1448:
In our pre 4.5 templates (JSP) we use the old 'cms:query' tag quite a bit to
fire XPath queries on our (data) repository. E.g. like this:
{code}
cms:query query=${query} nodeType=kantoor var=kantorenList
repository=data type=xpath /{code}
Where ${query} is some sort of XPath expression.
Is there a way to do this (using JSPs or FTLs for that matter) in Magnolia 4.5?
I cannot seem to find anything similar. Is it an idea to add this to the taglib
APIs? Or does Magnolia advise to no longer perform such queries in the
templates but rather in a model class?
Revive taglibs or provide other way to archieve their functionality
---
Key: MAGNOLIA-4434
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4434
Project: Magnolia
Issue Type: New Feature
Security Level: Public
Components: taglibs
Affects Versions: 4.5.3
Reporter: Edgar Vonk
Assignee: Ondřej Chytil
Fix For: 4.5.4
Since we are dropping support of compatibility modules there have to be
replacement for functions provided by those modules.
[Tag migration
page|http://wiki.magnolia-cms.com/display/DEV/Tags+migration+for+4.5]
contains detailed info for every tag.
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-4491) Port migrated taglib to 5.0
Port migrated taglib to 5.0 --- Key: MAGNOLIA-4491 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4491 Project: Magnolia Issue Type: Task Security Level: Public Reporter: Ondřej Chytil Assignee: Ondřej Chytil Fix For: 5.0 Port of MAGNOLIA-4434 has to be done to 5.0 branch. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4491) Port migrated taglib to 5.0
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-4491: Fix Version/s: 4.5.5 Port migrated taglib to 5.0 --- Key: MAGNOLIA-4491 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4491 Project: Magnolia Issue Type: Task Security Level: Public Reporter: Ondřej Chytil Assignee: Ondřej Chytil Fix For: 4.5.5, 5.0 Port of MAGNOLIA-4434 has to be done to 5.0 branch. Also tests are now missing and should be added. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4491) Port migrated taglib to 5.0
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-4491: Description: Port of MAGNOLIA-4434 has to be done to 5.0 branch. Also tests are now missing and should be added. was:Port of MAGNOLIA-4434 has to be done to 5.0 branch. Port migrated taglib to 5.0 --- Key: MAGNOLIA-4491 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4491 Project: Magnolia Issue Type: Task Security Level: Public Reporter: Ondřej Chytil Assignee: Ondřej Chytil Fix For: 4.5.5, 5.0 Port of MAGNOLIA-4434 has to be done to 5.0 branch. Also tests are now missing and should be added. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-4492) Exclude compatibility modules from main project build
Exclude compatibility modules from main project build - Key: MAGNOLIA-4492 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4492 Project: Magnolia Issue Type: Task Security Level: Public Components: build Reporter: Ondřej Chytil Assignee: Ondřej Chytil Fix For: 4.5.4 Compatibility modules were excluded from empty webapp but they are still built with magnolia_main. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4480) MgnlContext.getUser().inGroup(xxx) gives NPE
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-4480: Assignee: (was: Philipp Bärfuss) Attachment: stacktrace.txt Fix Version/s: 4.5.4 Description: Calling MgnlContext.getUser().inGroup() produces NPE. You can verify this quickly with the groovy console. Welcome to the Magnolia Groovy Interactive Console! Type 'help' for more info and a list of available commands. [Using Groovy version 1.7.10]. mgnl usr = MgnlContext.getUser(); === MgnlUser - superuser [51ae3379-67cf-4994-9e05-f97cb8bc3e4a] mgnl usr.inGroup(foo); NullPointerException: null mgnl was: Calling MgnlContext.getUser().inGroup() produces NPE. You can verify this quickly with the groovy console. Welcome to the Magnolia Groovy Interactive Console! Type 'help' for more info and a list of available commands. [Using Groovy version 1.7.10]. mgnl usr = MgnlContext.getUser(); === MgnlUser - superuser [51ae3379-67cf-4994-9e05-f97cb8bc3e4a] mgnl usr.inGroup(foo); NullPointerException: null mgnl Thanks for reporting the issue Richard. MgnlContext.getUser().inGroup(xxx) gives NPE -- Key: MAGNOLIA-4480 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4480 Project: Magnolia Issue Type: Bug Security Level: Public Components: security Affects Versions: 4.5.3 Environment: Windows, 4.5.3 EE Bundle Reporter: Richard Unger Priority: Major Fix For: 4.5.4 Attachments: stacktrace.txt Calling MgnlContext.getUser().inGroup() produces NPE. You can verify this quickly with the groovy console. Welcome to the Magnolia Groovy Interactive Console! Type 'help' for more info and a list of available commands. [Using Groovy version 1.7.10]. mgnl usr = MgnlContext.getUser(); === MgnlUser - superuser [51ae3379-67cf-4994-9e05-f97cb8bc3e4a] mgnl usr.inGroup(foo); NullPointerException: null mgnl -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4480) MgnlContext.getUser().inGroup(xxx) gives NPE
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-4480: Comment: was deleted (was: 2012-07-18 12:24:58,810 ERROR info.magnolia.cms.security.JCRSessionOp : Failed to execute info.magnolia.cms.security.MgnlUser$1@31c311ff session operation with Not an absolute path: superuser javax.jcr.RepositoryException: Not an absolute path: superuser at org.apache.jackrabbit.core.session.SessionItemOperation.perform(SessionItemOperation.java:189) at org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216) at org.apache.jackrabbit.core.SessionImpl.perform(SessionImpl.java:361) at org.apache.jackrabbit.core.SessionImpl.getNode(SessionImpl.java:1109) at info.magnolia.jcr.wrapper.DelegateSessionWrapper.getNode(DelegateSessionWrapper.java:179) at info.magnolia.jcr.wrapper.DelegateSessionWrapper.getNode(DelegateSessionWrapper.java:179) at info.magnolia.jcr.wrapper.NodeWrappingDelegateSessionWrapper.getNode(NodeWrappingDelegateSessionWrapper.java:55) at info.magnolia.cms.security.MgnlUser$1.doExec(MgnlUser.java:199) at info.magnolia.cms.security.MgnlUser$1.doExec(MgnlUser.java:195) at info.magnolia.cms.security.SilentSessionOp.exec(SilentSessionOp.java:71) at info.magnolia.context.MgnlContext.doInSystemContext(MgnlContext.java:403) at info.magnolia.context.MgnlContext.doInSystemContext(MgnlContext.java:376) at info.magnolia.cms.security.MgnlUser.hasAny(MgnlUser.java:195) at info.magnolia.cms.security.MgnlUser.inGroup(MgnlUser.java:121) at at.lfrz.magnolia.module.bmlfuw.util.BMLFUWLoginVirtualURIMapping.mapURI(BMLFUWLoginVirtualURIMapping.java:96) at info.magnolia.cms.beans.config.VirtualURIManager.getURIMapping(VirtualURIManager.java:112) at info.magnolia.cms.filters.VirtualUriFilter.getURIMapping(VirtualUriFilter.java:102) at info.magnolia.cms.filters.VirtualUriFilter.doFilter(VirtualUriFilter.java:67) at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:91) at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:83) at info.magnolia.module.cache.executor.Bypass.processCacheRequest(Bypass.java:58) at info.magnolia.module.cache.executor.CompositeExecutor.processCacheRequest(CompositeExecutor.java:66) at info.magnolia.module.cache.filter.CacheFilter.doFilter(CacheFilter.java:153) at info.magnolia.cms.filters.OncePerRequestAbstractMgnlFilter.doFilter(OncePerRequestAbstractMgnlFilter.java:61) at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:83) at info.magnolia.cms.i18n.I18nContentSupportFilter.doFilter(I18nContentSupportFilter.java:76) at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:91) at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:83) at info.magnolia.cms.filters.RangeSupportFilter.doFilter(RangeSupportFilter.java:86) at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:91) at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:83) at info.magnolia.cms.security.BaseSecurityFilter.doFilter(BaseSecurityFilter.java:60) at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:91) at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:83) at info.magnolia.cms.security.SecurityCallbackFilter.doFilter(SecurityCallbackFilter.java:86) at info.magnolia.cms.filters.OncePerRequestAbstractMgnlFilter.doFilter(OncePerRequestAbstractMgnlFilter.java:61) at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:83) at info.magnolia.cms.security.LogoutFilter.doFilter(LogoutFilter.java:93) at info.magnolia.cms.filters.OncePerRequestAbstractMgnlFilter.doFilter(OncePerRequestAbstractMgnlFilter.java:61) at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:83) at info.magnolia.module.templatingkit.filters.SiteMergeFilter.doFilter(SiteMergeFilter.java:99) at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:91) at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:83) at info.magnolia.module.extendedtemplatingkit.filters.MultiSiteFilter.doFilter(MultiSiteFilter.java:100) at info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:91) at info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:83) at info.magnolia.cms.filters.MultiChannelFilter.doFilter(MultiChannelFilter.java:83) at
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3571) AdminCentral button - JS error
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-3571: Fix Version/s: 4.4.9 (was: 4.4.x) AdminCentral button - JS error --- Key: MAGNOLIA-3571 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3571 Project: Magnolia Issue Type: Bug Security Level: Public Components: admininterface, gui Affects Versions: 4.3.8, 4.4.2, 4.5.2 Reporter: Matteo Pelucco Assignee: Milan Divilek Fix For: 4.4.9, 4.5.3 Attachments: screenshot.628.jpg A customer noticed that the AdminCentral button in the Main Bar sometimes stops to work, giving a JS error. These are the steps to reproduce it: 1) Open a IE8/FF browser in a new browser window (A) 2) Clean all browser history / data 3) Point directly to this url: http://demo.magnolia-cms.com 4) Provide username / password 5) Open (double-click) the demo-project page. It opens a new browser window, (B) 6) Now close the (A) window 7) Click on the AdminCentral button. -- JS error (javascript.js) In Firefox, you obtain the same behaviour opening (dragdrop outside browser app) the -B- window in a new browser window. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4434) Support for (XPath) queries in the taglibs?
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondřej Chytil updated MAGNOLIA-4434:
Assignee: (was: Philipp Bärfuss)
Fix Version/s: 4.5.4
Support for (XPath) queries in the taglibs?
---
Key: MAGNOLIA-4434
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4434
Project: Magnolia
Issue Type: New Feature
Security Level: Public
Components: taglibs
Affects Versions: 4.5.3
Reporter: Edgar Vonk
Fix For: 4.5.4
As mentioned in SUPPORT-1448:
In our pre 4.5 templates (JSP) we use the old 'cms:query' tag quite a bit
to fire XPath queries on our (data) repository. E.g. like this:
{code}
cms:query query=${query} nodeType=kantoor var=kantorenList
repository=data type=xpath /{code}
Where ${query} is some sort of XPath expression.
Is there a way to do this (using JSPs or FTLs for that matter) in Magnolia
4.5? I cannot seem to find anything similar. Is it an idea to add this to the
taglib APIs? Or does Magnolia advise to no longer perform such queries in the
templates but rather in a model class?
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4464) Core Tests not running on win system because of ignoring File.separator
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-4464: Fix Version/s: 4.5.4 As MAGNOLIA-4465 added to changelog. Core Tests not running on win system because of ignoring File.separator --- Key: MAGNOLIA-4464 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4464 Project: Magnolia Issue Type: Bug Security Level: Public Components: testing Affects Versions: 4.5.3 Environment: Win7 Reporter: Horst Krause Fix For: 4.5.4 Attachments: mgnl-core-test.zip Checking out the core and trying mvn package will result in some errors because of different file separators on linux and win. I added three changed test classes where I replace some hardcoded / with File.separator -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLMIGRATION-29) Migration module script scripts.migration.from4_4To4_5.general.UpdateMetaDataTemplateId does not handle Blossom templates
[ http://jira.magnolia-cms.com/browse/MGNLMIGRATION-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MGNLMIGRATION-29: --- Assignee: (was: Jan Haderka) Thanks for reporting the issue Tomas, ticket is already in current changelog. Migration module script scripts.migration.from4_4To4_5.general.UpdateMetaDataTemplateId does not handle Blossom templates - Key: MGNLMIGRATION-29 URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-29 Project: Magnolia Migration Issue Type: Bug Affects Versions: 1.1.1 Reporter: Tomas Brimor Priority: Blocker Fix For: 1.1.2 Migration module script scripts.migration.from4_4To4_5.general.UpdateMetaDataTemplateId does not handle Blossom templates. We are using blossom for templates and the migrationscript does not update our metadata for our pages to the new blossom template ids. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4447) DMS folder with special characters (öäü with magnolia.utf8.enabled=true) introduce incomplete linking of fck editor images
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondřej Chytil updated MAGNOLIA-4447:
Fix Version/s: 4.5.x
DMS folder with special characters (öäü with magnolia.utf8.enabled=true)
introduce incomplete linking of fck editor images
--
Key: MAGNOLIA-4447
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4447
Project: Magnolia
Issue Type: Bug
Security Level: Public
Components: fckeditor
Affects Versions: 4.4.8, 4.5.2
Reporter: Stefan Baur
Fix For: 4.5.x
Normally, the fck editor saves images in this format:
src=${link:{uuid:{f466d306-ff0c-4921-a06f-40a27f17e22f},repository:{dms},handle:{/TESTING/images/Satellite_image_of_Iceland_in_September},nodeData:{},extension:{jpg}}}
If the folder name contains a special character like öäü (e.g. Jubiläum), the
image is saved differently:
src=/dms/TESTING/Jubilauml;um/Satellite_image_of_Iceland_in_September.jpg
In the second case, the moving of the image will cause the link to break, as
there is no UUID stored to resolve the new location.
I assume there is a problem in the DMS to resolve folder content with special
characters. So this might sctually be a DMS problem or have to do with such
one.
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4451) Default cache policy doesn't handle correctly URLs with multi value parameters
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-4451: Fix Version/s: 4.5.4 Thanks for reporting the issue Gianluca. For now added to backlog. Default cache policy doesn't handle correctly URLs with multi value parameters -- Key: MAGNOLIA-4451 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4451 Project: Magnolia Issue Type: Bug Security Level: Public Components: cache Affects Versions: 4.4.8, 4.5 Reporter: Gianluca Ortelli Fix For: 4.5.4 If a site uses the Default policy and decides to extends the caching to URLs with query parameters, the cache will behave incorrectly in presence of multi valued parameters. For example, http://host/path?a=1 and http://host/path?a=1a=2 will be stored using equal values of the DefaultCacheKey object. This happens because DefaultCacheKey keeps the parameters in a MapString, String. (I made my test with magnolia on top of Tomcat 6; I guess the way HttpServletRequest#getParameters() compresses multiple values in one is not predictable, so a different example might be necessary to replicate the bug on a different container). I used Magnolia 4.4.6, but the implementation of DefaultCacheKey has not changed in that respect in both 4.4. and 4.5 branches, so I expect the bug to affect all versions. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-4441) Review util classes
Review util classes --- Key: MAGNOLIA-4441 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4441 Project: Magnolia Issue Type: Task Security Level: Public Components: core Reporter: Ondřej Chytil Fix For: 4.5.4 PropertyUtil, NodeDataUtil and DateUtil should be checked for duplicate code, missplace methods etc. For example PropertyUtil.getDateFormat() should be in DateUtil class, also the same code is directly in NodeDataUtil.getValueString(NodeData). -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (THBLUE-2) Theme depends on ETK whereas it doesn't provide such a dependency declaration
[
http://jira.magnolia-cms.com/browse/THBLUE-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondřej Chytil updated THBLUE-2:
---
Fix Version/s: 1.0.0
Theme depends on ETK whereas it doesn't provide such a dependency declaration
-
Key: THBLUE-2
URL: http://jira.magnolia-cms.com/browse/THBLUE-2
Project: Blue theme for Magnolia
Issue Type: Bug
Affects Versions: 1.0.0
Reporter: Daniel Kasmeroglu
Fix For: 1.0.0
I suspect this to be a refactoring relict as the bootstrap for this theme
declares
*info.magnolia.module.extendedtemplatingkit.imaging.ETKImagingSupport* as the
class for the _imaging_ node. I expect
*info.magnolia.module.templatingkit.imaging.STKImagingSupport* to be the
right choice.
As a workaround someone can create a pseudo-implementation like this:
{code:java}
package info.magnolia.module.extendedtemplatingkit.imaging;
import info.magnolia.module.templatingkit.imaging.STKImagingSupport;
public class ETKImagingSupport extends STKImagingSupport {
}
{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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLDMS-234) Links created within the description field's FCKEditor are not resolved correctly
[
http://jira.magnolia-cms.com/browse/MGNLDMS-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondřej Chytil updated MGNLDMS-234:
--
Assignee: (was: Philipp Bärfuss)
Fix Version/s: 1.6.3
Confirmed, thanks for reporting Matt, added to changelog.
Links created within the description field's FCKEditor are not resolved
correctly
-
Key: MGNLDMS-234
URL: http://jira.magnolia-cms.com/browse/MGNLDMS-234
Project: Magnolia DMS Module
Issue Type: Bug
Affects Versions: 1.6.1
Environment: Java 1.6, Tomcat 7, Magnolia 4.5.2
Reporter: Matt Dertinger
Fix For: 1.6.3
Hi,
Currently, links added within a DMS assets {{description}} field are not
resolved correctly.
h2. Steps to reproduce:
# Log into [demoauthor.magnolia-cms.com] as superuser
# Go to {{Documents/img/bk/Opener/}}
# Select {{wooden-table-with-yellow---red-chairs}} then click on {{Edit
document}} to open the Edit dialog
# In the Edit dialog, enter Some text with a link to website content.
within the {{description}} field. Select the text a link to website content
and click the {{link}} icon in the FCKEditor's menu bar.
# In the Link dialog, click the {{Browse server}} button, choose
{{demo-project/about}} from the website tree, then click {{OK}}
# In the Edit dialog window, click {{Save}}
# Open up a new browser tab, and go to
[http://demoauthor.magnolia-cms.com/demo-project/multimedia/image-gallery.html]
# Hit the {{esc}} key to enter preview mode, then click the {{Zoom}} icon
under the first gallery photo to bring up the showbox.
# Mouse over, or click on the link within the images description (i.e. a link
to website content).
# Note that the link is not resolved and instead renders as:
{code:html}
a
href=${link:{uuid:{f312fc16-8f66-451c-bdf0-a72913b74c2d},repository:{website},handle:{/demo-project/about},nodeData:{},extension:{html}}}a
link to website content/a
{code}
Please let me know if you have any questions.
Cheers,
Matt
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSCH-28) NullPointerException by configured jobs without parameters
[ http://jira.magnolia-cms.com/browse/MGNLSCH-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MGNLSCH-28: - Assignee: (was: Philipp Bärfuss) Fix Version/s: 1.5.3 Priority: Trivial (was: Minor) Thanks for reporting Frank, added to changelog but with lower priority since there is easy workaround. NullPointerException by configured jobs without parameters -- Key: MGNLSCH-28 URL: http://jira.magnolia-cms.com/browse/MGNLSCH-28 Project: Magnolia Scheduler Module Issue Type: Bug Affects Versions: 1.4.2, 1.5.1 Reporter: Frank Sommer Priority: Trivial Fix For: 1.5.3 Workaround is to configure a dummy parameter to this job. Then the job will be executed. Error occured on info.magnolia.module.scheduler.CommandJob line 88. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4416) this will lead to error-logs when strarting up your server
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-4416: Assignee: (was: Philipp Bärfuss) Fix Version/s: 4.5.4 Thanks for reporting this Jonathan. this will lead to error-logs when strarting up your server -- Key: MAGNOLIA-4416 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4416 Project: Magnolia Issue Type: Bug Security Level: Public Components: core Affects Versions: 4.5.2 Reporter: Jonathan Molyneux Priority: Trivial Fix For: 4.5.4 Minor spelling mistake referenced in the code this will lead to error-logs when strarting up your server. The word starting has been misspelled. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLFORM-123) Selection Checkbox, select (single/multiple) and radio buttons don't allow multiple selection
[ http://jira.magnolia-cms.com/browse/MGNLFORM-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MGNLFORM-123: --- Fix Version/s: 1.4.3 (was: 1.4.x) Selection Checkbox, select (single/multiple) and radio buttons don't allow multiple selection - Key: MGNLFORM-123 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-123 Project: Magnolia Form Module Issue Type: Bug Affects Versions: 1.4.1 Environment: 4.5.1 EE Reporter: Eric Hechinger Priority: Major Fix For: 1.4.3 Attachments: formSelection.ftl Not able to define multiple select with the recomended syntax: bar:bar baz:baz bat:bat Just display the first entry. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLFORM-123) Selection Checkbox, select (single/multiple) and radio buttons don't allow multiple selection
[ http://jira.magnolia-cms.com/browse/MGNLFORM-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MGNLFORM-123: --- Patch included: [Yes] Selection Checkbox, select (single/multiple) and radio buttons don't allow multiple selection - Key: MGNLFORM-123 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-123 Project: Magnolia Form Module Issue Type: Bug Affects Versions: 1.4.1 Environment: 4.5.1 EE Reporter: Eric Hechinger Priority: Major Fix For: 1.4.3 Attachments: formSelection.ftl Not able to define multiple select with the recomended syntax: bar:bar baz:baz bat:bat Just display the first entry. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4400) templating: introduce a possibility to get node by identifier
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondřej Chytil updated MAGNOLIA-4400:
Assignee: Milan Divilek (was: Philipp Bärfuss)
Fix Version/s: 4.5.4
templating: introduce a possibility to get node by identifier
--
Key: MAGNOLIA-4400
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4400
Project: Magnolia
Issue Type: Improvement
Security Level: Public
Components: templating
Affects Versions: 4.5
Reporter: Zdenek Skodik
Assignee: Milan Divilek
Priority: Major
Fix For: 4.5.4
{{TemplatingFunctions}} lets you retrieve a node by path, similarly you
should have a possibility to do by identifier so that you'll not need to go
via MgnlContext necessarily.
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4431) cmsfn:link methods missing from the JSP tag lib
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-4431: Assignee: Milan Divilek (was: Philipp Bärfuss) Fix Version/s: 4.5.4 cmsfn:link methods missing from the JSP tag lib --- Key: MAGNOLIA-4431 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4431 Project: Magnolia Issue Type: Task Security Level: Public Components: taglibs Affects Versions: 4.5.3 Reporter: Edgar Vonk Assignee: Milan Divilek Fix For: 4.5.4 In the new Magnolia JSP taglib API we are missing the cmsfn:link methods that take a UUID as parameter. The FTL cmsfn function does provide a link(String workspace, String nodeIdentifier) function but the JSP cmsfn function does not. It is possible to add this? We are now forced to keep on using the JSP compatibility taglib. Also reported in [SUPPORT-1448|http://jira.magnolia-cms.com/browse/SUPPORT-1448?focusedCommentId=47583page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_47583]. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4432) Add function to retrieve node based on UUID?
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondřej Chytil updated MAGNOLIA-4432:
Assignee: Milan Divilek (was: Philipp Bärfuss)
Fix Version/s: 4.5.4
Add function to retrieve node based on UUID?
Key: MAGNOLIA-4432
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4432
Project: Magnolia
Issue Type: New Feature
Security Level: Public
Components: taglibs
Affects Versions: 4.5.3
Reporter: Edgar Vonk
Assignee: Milan Divilek
Hi,
It could be that we are overlooking something but we cannot seem to find an
easy way to get to a (page) node from the UUID anymore in the new Magnolia
templating API / taglibs. Neither the FTL nor the JSP version. Can this
functionality be added to the taglibs? cmsfn:link seems to be the only
function that still takes a UUID.
Situation: we store internal links as UUID fields (not paths). In the old
(pre 4.5) API it was easy to retrieve the node that the link points to in
order to get this node's children etc. In the new API (FTL example below) we
now have to get the link and then strip the context path and extension from
it and use the resulting path to get the node. There must be an easier way?
{code}
[#assign contextlink = cmsfn.link('website',content.start?string)]
[#assign serviceMenuParentPath =
(contextlink?replace(.+state.extension,))?replace(ctx.contextPath,)]
[#assign serviceMenuParentNode =
cmsfn.content('website',serviceMenuParentPath)]
[#if serviceMenuParentNode?has_content]
ul class=nav
[#list cmsfn.children(serviceMenuParentNode) as serviceMenuNode]
[#assign serviceMenuPage = cmsfn.asContentMap(serviceMenuNode)]
[#assign serviceMenuPageLink = cmsfn.link(serviceMenuPage)!]
[..]
{code}
Also reported in
[SUPPORT-1448|http://jira.magnolia-cms.com/browse/SUPPORT-1448?focusedCommentId=47583page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_47583].
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLRSSAGG-56) Handle stuck import job
Handle stuck import job --- Key: MGNLRSSAGG-56 URL: http://jira.magnolia-cms.com/browse/MGNLRSSAGG-56 Project: Magnolia RSS Aggregator Module Issue Type: Improvement Affects Versions: 1.2.3 Reporter: Ondřej Chytil Assignee: Milan Divilek While importer is running and gets stuck it's impossible to stop it unless server is restarted. There should be possibility to safely end import job or make sure that the job doesn't get into this state. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSTK-957) Internal link component throws freemarker exception if target is not available
[
http://jira.magnolia-cms.com/browse/MGNLSTK-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondřej Chytil updated MGNLSTK-957:
--
Assignee: (was: Philipp Bärfuss)
Fix Version/s: 2.0.4
Thanks for reporting the issue Frank.
Internal link component throws freemarker exception if target is not available
--
Key: MGNLSTK-957
URL: http://jira.magnolia-cms.com/browse/MGNLSTK-957
Project: Magnolia Standard Templating Kit
Issue Type: Bug
Components: demoproject
Affects Versions: 2.0.2
Reporter: Frank Sommer
Fix For: 2.0.4
Tested on demoauthor instance. Try to reference a not existing page in a
internal link component and a freemarker stack trace will occure.
{{stkFunctions.getReferencedContent(content, link,
RepositoryConstants.WEBSITE)}} throws an uncatched runtime exception.
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3571) AdminCentral button - JS error
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-3571: Fix Version/s: 4.5.3 Affects Version/s: 4.5.2 (was: 4.3.2) Also confirmed on current demo (4.5.2). AdminCentral button - JS error --- Key: MAGNOLIA-3571 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3571 Project: Magnolia Issue Type: Bug Security Level: Public Components: admininterface, gui Affects Versions: 4.3.8, 4.4.2, 4.5.2 Reporter: Matteo Pelucco Fix For: 4.4.x, 4.5.3 Attachments: screenshot.628.jpg A customer noticed that the AdminCentral button in the Main Bar sometimes stops to work, giving a JS error. These are the steps to reproduce it: 1) Open a IE8/FF browser in a new browser window (A) 2) Clean all browser history / data 3) Point directly to this url: http://demo.magnolia-cms.com 4) Provide username / password 5) Open (double-click) the demo-project page. It opens a new browser window, (B) 6) Now close the (A) window 7) Click on the AdminCentral button. -- JS error (javascript.js) In Firefox, you obtain the same behaviour opening (dragdrop outside browser app) the -B- window in a new browser window. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Reopened: (MAGNOLIA-4380) magnolia-empty-webapp should provide dependency on magnolia-templating-jsp
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondřej Chytil reopened MAGNOLIA-4380:
-
Also magnolia-templating-compatibility,
magnolia-templating-compatibility-taglib-cms and
magnolia-templating-compatibility-taglib-utility should be part of bundled
webapp.
magnolia-empty-webapp should provide dependency on magnolia-templating-jsp
--
Key: MAGNOLIA-4380
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4380
Project: Magnolia
Issue Type: Task
Security Level: Public
Components: build
Reporter: Federico Grilli
Assignee: Federico Grilli
Fix For: 4.5.3
As both CE and EE webapps depend on m-empty-webapp and as Magnolia aims at
providing JSP support out of the box, it makes sense to add m-templating-jsp
dependency to the m-empty-webapp module. Furthermore, m-templating-samples
should use scope {{provided}} so that the add-ons folder in the bundles does
not contain a useless duplicate of m-templating-jsp jar
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLFORM-128) Class FormParagraph should be FormComponent
[ http://jira.magnolia-cms.com/browse/MGNLFORM-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MGNLFORM-128: --- Fix Version/s: 1.4.3 (was: 1.4.2) Class FormParagraph should be FormComponent --- Key: MGNLFORM-128 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-128 Project: Magnolia Form Module Issue Type: Improvement Affects Versions: 1.4.1 Reporter: Christian Ringele Assignee: Ondřej Chytil Fix For: 1.4.3 The class info.magnolia.module.form.templates.components.FormParagraph should be renamed to info.magnolia.module.form.templates.components.FormComponent -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSTK-803) Update translations
[ http://jira.magnolia-cms.com/browse/MGNLSTK-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MGNLSTK-803: -- Fix Version/s: 2.0.4 (was: 2.0.3) Update translations --- Key: MGNLSTK-803 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-803 Project: Magnolia Standard Templating Kit Issue Type: Task Reporter: Grégory Joseph Assignee: Grégory Joseph Fix For: 2.0.4 Another round of updates. See http://documentation.magnolia-cms.com/contribute/i18n.html 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLDMS-231) Reactivate tests
[ http://jira.magnolia-cms.com/browse/MGNLDMS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MGNLDMS-231: -- Priority: Major (was: Neutral) Reactivate tests Key: MGNLDMS-231 URL: http://jira.magnolia-cms.com/browse/MGNLDMS-231 Project: Magnolia DMS Module Issue Type: Bug Affects Versions: 1.6.1 Reporter: Milan Divilek Priority: Major Fix For: 1.6.2 The most of test in dms are not launched, because missing @Test tag. Also should be rewritten to mockito. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLDATA-152) ItemTypes Root Path set to root leads to NPE in New Item dialog
[ http://jira.magnolia-cms.com/browse/MGNLDATA-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MGNLDATA-152: --- Fix Version/s: 1.7.3 (was: 1.7.2) ItemTypes Root Path set to root leads to NPE in New Item dialog --- Key: MGNLDATA-152 URL: http://jira.magnolia-cms.com/browse/MGNLDATA-152 Project: Magnolia Data Module Issue Type: Bug Affects Versions: 1.7.1 Reporter: Milan Divilek Assignee: Milan Divilek Fix For: 1.7.3 Attachments: stacktrace.txt When ItemTypes Root Path is root or is blank, then New Item dialog return HTTP Status 500 depending on NPE and you get ItemNotFoundException: Root node doesn't have a parent. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4345) use digester to generate signatures in activation
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-4345: Fix Version/s: 4.5.4 (was: 4.5.3) use digester to generate signatures in activation - Key: MAGNOLIA-4345 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4345 Project: Magnolia Issue Type: Improvement Security Level: Public Components: core Affects Versions: 4.5 Reporter: Jan Haderka Assignee: Jan Haderka Fix For: 4.5.4 info.magnolia.cms.security.Digester -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLSTK-803) Update translations
[ http://jira.magnolia-cms.com/browse/MGNLSTK-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MGNLSTK-803: -- Fix Version/s: 2.0.3 (was: 2.0.4) Update translations --- Key: MGNLSTK-803 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-803 Project: Magnolia Standard Templating Kit Issue Type: Task Reporter: Grégory Joseph Assignee: Grégory Joseph Fix For: 2.0.3 Another round of updates. See http://documentation.magnolia-cms.com/contribute/i18n.html 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4403) Consistent date display for website pages and website page versions
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-4403: Assignee: (was: Philipp Bärfuss) Fix Version/s: 4.5.x Priority: Minor (was: Neutral) Added to backlog for now but the time format should be synchronized. Thanks for reporting this Tomas. Consistent date display for website pages and website page versions --- Key: MAGNOLIA-4403 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4403 Project: Magnolia Issue Type: Improvement Security Level: Public Components: admininterface Affects Versions: 4.4.5 Reporter: Tomas Brimor Priority: Minor Fix For: 4.5.x Attachments: version-date.png, website-date.png The date display for website pages and the date displayed in versions for them are not the same. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4404) External links in menu. Do it standard way
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-4404: Fix Version/s: 4.5.x Adding to backlog for now, let's see if there will be more interest in this improvement. External links in menu. Do it standard way -- Key: MAGNOLIA-4404 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4404 Project: Magnolia Issue Type: New Feature Security Level: Public Reporter: Lauri Fix For: 4.5.x Related forum threads: [Thread 1|http://forum.magnolia-cms.com/forum/thread.html?threadId=35cb7d6f-ed6f-41a1-9f86-a6b98d10b68fpage=1] [Thread 2|http://forum.magnolia-cms.com/forum/thread.html?threadId=ce5775c9-15db-4666-8113-3eaabed48b59page=1] Make it possible to render external links in menu. This probably will require: 1) a special template 2) changes to cmsu taglib (and rest), so it would be template aware on link generation phase -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLDATA-151) ItemTypes cannot be deleted when their rootPath is not on the top level
[
http://jira.magnolia-cms.com/browse/MGNLDATA-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondřej Chytil updated MGNLDATA-151:
---
Assignee: (was: Philipp Bärfuss)
Fix Version/s: 1.6.x
1.7.2
Affects Version/s: 1.7.1
Also issue for trunk version - added to 4.5.3 changelog.
Thanks for reporting Will.
ItemTypes cannot be deleted when their rootPath is not on the top level
-
Key: MGNLDATA-151
URL: http://jira.magnolia-cms.com/browse/MGNLDATA-151
Project: Magnolia Data Module
Issue Type: Bug
Affects Versions: 1.6.4, 1.7.1
Reporter: Will Scheidegger
Fix For: 1.6.x, 1.7.2
Attachments: itemsExist.patch
Original Estimate: 0.5h
Remaining Estimate: 0.5h
If you have defined a data node type which has its root on level 1 you'll
get a NPE when trying to delete the item type.
{{2012-05-05 07:04:18,637 ERROR
fo.magnolia.module.data.commands.TypeDeleteCommand: cannot do delete
java.lang.NullPointerException
at
info.magnolia.module.data.commands.TypeDeleteCommand.itemsExist(TypeDeleteCommand.java:119)}}
This is caused by the use of (deprecated) *.getChildByName()* which of course
does not work for something like /customer/products.
The attached patch uses *ContentUtil.getContent(repository, path)* instead
and therefore also works with nested root nodes.
--
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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MGNLFORM-126) Back button should not be implemented with a Javascript history(-1) link!
[ http://jira.magnolia-cms.com/browse/MGNLFORM-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MGNLFORM-126: --- Fix Version/s: 1.4.2 Thanks for reporting Will, added for next release. Back button should not be implemented with a Javascript history(-1) link! - Key: MGNLFORM-126 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-126 Project: Magnolia Form Module Issue Type: Bug Affects Versions: 1.4.1 Reporter: Will Scheidegger Priority: Major Fix For: 1.4.2 The current implementation of the back button is useless. As soon as a validation error occurs, the user is not taken back to the previous step but rather to the same step before the validation. The form engine should always know all its steps and be able to navigation from one step to the next and back. To cope with the new condition-feature the engine should keep track of the previous steps in its own history-stack. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Reopened: (MAGNOLIA-3972) Image broken links when using both DMS referencing and user upload
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondřej Chytil reopened MAGNOLIA-3972:
-
Image broken links when using both DMS referencing and user upload
--
Key: MAGNOLIA-3972
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3972
Project: Magnolia
Issue Type: Bug
Security Level: Public
Components: fckeditor
Affects Versions: 4.4.6, 4.5.2
Environment: standard magnolia installation on windows/linux
Reporter: Matteo Pelucco
Assignee: Ondřej Chytil
Fix For: 4.4.7, 4.5.3
Attachments: ImageImportInRichTextArea.jpg.rb.jpg
When using FCK editor image button, there are broken links for images.
Reproduce with:
1) Upload an image to DMS
2) Open a page, new paragraph textImage
3) In FCK, upload a new image from your PC. The link is correct (e.g.:
/magnoliaAuthor/tmp/fckeditor/22ba03f1-5b9b-11e1-834c-df984c86872c/banner_FlashSubstitute.jpg)
4) Now save and re-edit
5) In FCK, reference a DMS image (see 1.). The previous correct link now is
broken (e.g.:
/test/test-section/text/mainArea/013/text_files/file/banner_FlashSubstitute.jpg)
but the second (dms) is working.
probably related to: http://jira.magnolia-cms.com/browse/MGNLDATA-143
Update from SUPPORT-1566:
{noformat}
IMPORTANT: use magnolia with site recognition based on domain mapping.
Otherwise the bug is not visible.
{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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MGNLRSSAGG-55) Wrong link to RSS feed icon
Wrong link to RSS feed icon --- Key: MGNLRSSAGG-55 URL: http://jira.magnolia-cms.com/browse/MGNLRSSAGG-55 Project: Magnolia RSS Aggregator Module Issue Type: Bug Affects Versions: 1.3.1, 1.2.2 Reporter: Ondřej Chytil Assignee: Ondřej Chytil Fix For: 1.2.3, 1.3.2 There are incorrect links to RSS feed icon in RSS templates - icon is 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Reopened: (MSHOP-23) Update to Magnolia Version 4.4.6
[ http://jira.magnolia-cms.com/browse/MSHOP-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil reopened MSHOP-23: Needs to be backported to branch. Update to Magnolia Version 4.4.6 Key: MSHOP-23 URL: http://jira.magnolia-cms.com/browse/MSHOP-23 Project: Magnolia Shop Issue Type: Task Affects Versions: 1.0 Reporter: Teresa Miyar Assignee: Teresa Miyar Fix For: 1.0.1, 1.1 Time Spent: 3h Remaining Estimate: 0d -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MSHOP-23) Update to Magnolia Version 4.4.6
[ http://jira.magnolia-cms.com/browse/MSHOP-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MSHOP-23: --- Fix Version/s: 1.1 Update to Magnolia Version 4.4.6 Key: MSHOP-23 URL: http://jira.magnolia-cms.com/browse/MSHOP-23 Project: Magnolia Shop Issue Type: Task Affects Versions: 1.0 Reporter: Teresa Miyar Assignee: Teresa Miyar Fix For: 1.0.1, 1.1 Time Spent: 3h Remaining Estimate: 0d -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MSHOP-22) The demo-project is requested when adding the shop module to my application
[ http://jira.magnolia-cms.com/browse/MSHOP-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MSHOP-22: --- Fix Version/s: 1.1 The demo-project is requested when adding the shop module to my application --- Key: MSHOP-22 URL: http://jira.magnolia-cms.com/browse/MSHOP-22 Project: Magnolia Shop Issue Type: Bug Affects Versions: 1.0 Reporter: Fabrice LAZZARI Assignee: Teresa Miyar Priority: Blocker Fix For: 1.0.1, 1.1 I've downloaded the shop module from the magnolia shop, and installed it in the WEB-INF\lib of my application. When starting the application I get the following error message, saying that I need the demo-project. It's OK for test purpose, but I'd like to be able to install the shop on our productive system without demo-project = blocker issue. Could you remove the dependency ? Thanks ! -- java.lang.Exception: Exception received from deployment driver. See Error Log view for more detail. at oracle.eclipse.tools.weblogic.server.internal.DeploymentProgressListener.watch(DeploymentProgressListener.java:190) at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper.redeploy(WlsJ2EEDeploymentHelper.java:931) at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper.redeploy(WlsJ2EEDeploymentHelper.java:797) at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishWeblogicModules(WeblogicServerBehaviour.java:1471) at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishToServer(WeblogicServerBehaviour.java:896) at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishOnce(WeblogicServerBehaviour.java:677) at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publish(WeblogicServerBehaviour.java:530) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:775) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2893) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:337) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: weblogic.application.ModuleException: :info.magnolia.module.model.reader.ModuleDependencyException:Module Magnolia Simple Shop Module (version 1.0.0) is dependent on demo-project version 1.4.2/*, which was not found. at info.magnolia.module.model.reader.DependencyCheckerImpl.checkSpecificDependency(DependencyCheckerImpl.java:75) at info.magnolia.module.model.reader.DependencyCheckerImpl.checkDependencies(DependencyCheckerImpl.java:57) at info.magnolia.module.ModuleManagerImpl.loadDefinitions(ModuleManagerImpl.java:140) at info.magnolia.cms.beans.config.PropertiesInitializer.loadAllModuleProperties(PropertiesInitializer.java:148) at info.magnolia.cms.beans.config.PropertiesInitializer.loadAllProperties(PropertiesInitializer.java:119) at info.magnolia.cms.servlets.MgnlServletContextListener.contextInitialized(MgnlServletContextListener.java:192) at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1863) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267) at
[magnolia-dev] [JIRA] Reopened: (MSHOP-22) The demo-project is requested when adding the shop module to my application
[ http://jira.magnolia-cms.com/browse/MSHOP-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil reopened MSHOP-22: Needs to be backported to branch. The demo-project is requested when adding the shop module to my application --- Key: MSHOP-22 URL: http://jira.magnolia-cms.com/browse/MSHOP-22 Project: Magnolia Shop Issue Type: Bug Affects Versions: 1.0 Reporter: Fabrice LAZZARI Assignee: Teresa Miyar Priority: Blocker Fix For: 1.0.1, 1.1 I've downloaded the shop module from the magnolia shop, and installed it in the WEB-INF\lib of my application. When starting the application I get the following error message, saying that I need the demo-project. It's OK for test purpose, but I'd like to be able to install the shop on our productive system without demo-project = blocker issue. Could you remove the dependency ? Thanks ! -- java.lang.Exception: Exception received from deployment driver. See Error Log view for more detail. at oracle.eclipse.tools.weblogic.server.internal.DeploymentProgressListener.watch(DeploymentProgressListener.java:190) at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper.redeploy(WlsJ2EEDeploymentHelper.java:931) at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper.redeploy(WlsJ2EEDeploymentHelper.java:797) at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishWeblogicModules(WeblogicServerBehaviour.java:1471) at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishToServer(WeblogicServerBehaviour.java:896) at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishOnce(WeblogicServerBehaviour.java:677) at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publish(WeblogicServerBehaviour.java:530) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:775) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2893) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:337) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: weblogic.application.ModuleException: :info.magnolia.module.model.reader.ModuleDependencyException:Module Magnolia Simple Shop Module (version 1.0.0) is dependent on demo-project version 1.4.2/*, which was not found. at info.magnolia.module.model.reader.DependencyCheckerImpl.checkSpecificDependency(DependencyCheckerImpl.java:75) at info.magnolia.module.model.reader.DependencyCheckerImpl.checkDependencies(DependencyCheckerImpl.java:57) at info.magnolia.module.ModuleManagerImpl.loadDefinitions(ModuleManagerImpl.java:140) at info.magnolia.cms.beans.config.PropertiesInitializer.loadAllModuleProperties(PropertiesInitializer.java:148) at info.magnolia.cms.beans.config.PropertiesInitializer.loadAllProperties(PropertiesInitializer.java:119) at info.magnolia.cms.servlets.MgnlServletContextListener.contextInitialized(MgnlServletContextListener.java:192) at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1863) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267) at
[magnolia-dev] [JIRA] Updated: (MGNLFORM-117) One should be able to pre-fill form fields
[ http://jira.magnolia-cms.com/browse/MGNLFORM-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MGNLFORM-117: --- Fix Version/s: 1.3.3 One should be able to pre-fill form fields -- Key: MGNLFORM-117 URL: http://jira.magnolia-cms.com/browse/MGNLFORM-117 Project: Magnolia Form Module Issue Type: Improvement Affects Versions: 1.3.1 Reporter: Will Scheidegger Assignee: Tobias Mattsson Fix For: 1.3.3, 1.4.2 Attachments: formengine.patch Since it apparently is best practice to use the form module to for all kinds of user interaction one should be able to pre-fill form fields when displaying the form. A perfect example to illustrate this need is the stkPURUpdateForm paragraph which allows the user to update info about his/her user account. The form however is displayed empty. One can create a custom form engine and a form step state which sets the values in the fields, but you cannot add this manually created form state to the form engine (no setter method and private formState attribute). So either a setter method should be provided or then we should have an additional formValuesInit method which takes a hash with the values and does the rest. -- 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: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-4367) When you enable config:/server/i18n/content on CE newly created SingletonParagraphTemplateModel pages will crash
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondřej Chytil updated MAGNOLIA-4367: Attachment: stacktrace.txt When you enable config:/server/i18n/content on CE newly created SingletonParagraphTemplateModel pages will crash Key: MAGNOLIA-4367 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-4367 Project: Magnolia Issue Type: Bug Security Level: Public Environment: - Plain vanilla Magnolia CE 4.4.5 - STK 1.4.5 Reporter: Will Scheidegger Assignee: Ondřej Chytil Priority: Major Fix For: 4.4.7 Attachments: stacktrace.txt Steps to reproduce: - Download + bootstrap - Go to config:/server/i18n/content and set enabled to true - Create a new stkNewsOverview page - Try to open page The exception: 2012-02-13 19:50:38,888 ERROR info.magnolia.module.templating.RenderingFilter : Can't create singleton paragraph java.lang.IllegalStateException: Can't create singleton paragraph at info.magnolia.module.templatingkit.templates.SingletonParagraphTemplateModel.createMainArea(SingletonParagraphTemplateModel.java:136) at info.magnolia.module.templatingkit.templates.SingletonParagraphTemplateModel.access$000(SingletonParagraphTemplateModel.java:66) at info.magnolia.module.templatingkit.templates.SingletonParagraphTemplateModel$1.exec(SingletonParagraphTemplateModel.java:80) at info.magnolia.module.templatingkit.util.STKUtil$3.exec(STKUtil.java:640) at info.magnolia.module.templatingkit.util.STKUtil$3.exec(STKUtil.java:636) at info.magnolia.context.MgnlContext.doInSystemContext(MgnlContext.java:396) ... Caused by: java.lang.IllegalStateException: Can only get the aggregation state within a WebContext. at info.magnolia.context.MgnlContext.getAggregationState(MgnlContext.java:221) at info.magnolia.cms.i18n.AbstractI18nContentSupport.getLocale(AbstractI18nContentSupport.java:86) at info.magnolia.cms.i18n.AbstractI18nContentSupport.getNodeData(AbstractI18nContentSupport.java:222) at info.magnolia.cms.i18n.DefaultI18nContentSupport$$EnhancerByCGLIB$$5d958932.getNodeData(generated) at info.magnolia.cms.i18n.I18nContentWrapper.newNodeDataInstance(I18nContentWrapper.java:61) at info.magnolia.cms.core.AbstractContent.setNodeData(AbstractContent.java:212) at info.magnolia.cms.core.AbstractContent.createNodeData(AbstractContent.java:120) at info.magnolia.module.templatingkit.templates.SingletonParagraphTemplateModel.setDefaultValues(SingletonParagraphTemplateModel.java:146) at info.magnolia.module.templatingkit.templates.SingletonParagraphTemplateModel.createMainArea(SingletonParagraphTemplateModel.java:131) -- 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: dev-list-unsubscr...@magnolia-cms.com
