[magnolia-dev] [JIRA] Created: (MGNLDMS-224) Move/Copy documets to root fails on empty path
Move/Copy documets to root fails on empty path -- Key: MGNLDMS-224 URL: http://jira.magnolia-cms.com/browse/MGNLDMS-224 Project: Magnolia DMS Module Issue Type: Bug Affects Versions: 1.5.3 Reporter: Milan Divilek Fix For: 1.5.4 Attachments: trace.txt When you try copy/move some documents or folders to root of the DMS, it fails on empty path -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MAGNOLIA-3949) Enable the "enabled" flag in DefaultSubscription bean
Enable the "enabled" flag in DefaultSubscription bean - Key: MAGNOLIA-3949 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3949 Project: Magnolia Issue Type: Improvement Security Level: Public Components: activation Affects Versions: 4.4.4 Reporter: Stefan Baur Assignee: Philipp Bärfuss Currently, the bean info.magnolia.module.exchangesimple.DefaultSubscription return true for isEnabled(). It would be nice to actually being able to disable a subscription on a configuration level. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Reopened: (MAGNOLIA-3899) PermissionUtil is too lax when converting permissions; it doesn't take into account custom permissions
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Haderka reopened MAGNOLIA-3899:
---
Assignee: Jan Haderka (was: Tobias Mattsson)
Actually this method was never intended for converting all permissions,
specially as custom permissions do not have corresponding JCR permission. Which
is a reason why for such custom permissions method returned empty string.
In general custom permissions should be checked against {{AccessManager}} not
against the content. Check for custom (64) permission was correctly returning
no corresponding action, check for combination of custom and other permission
(64+Permission.READ) correctly returned JCR {{action_read}} permission.
Naming of the method and javadoc need to be updated to remove this confusion.
For the time being we might also output warning in the log file about checking
no JCR permission against JCR, however throwing exception without giving option
to separate custom and JCR permissions is not correct.
> PermissionUtil is too lax when converting permissions; it doesn't take into
> account custom permissions
> --
>
> Key: MAGNOLIA-3899
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3899
> Project: Magnolia
> Issue Type: Bug
> Security Level: Public
> Components: core
>Reporter: Grégory Joseph
>Assignee: Jan Haderka
>Priority: Blocker
> Fix For: 4.5
>
>
> In the forum module, for example, we added a specific "permission"
> ({{moderation}}). Its code is {{64}}. When doing
> {{PermissionUtil.convertPermissions(64)}}, we get an empty string, which is
> probably (?) going to get the code further down to check for no permission
> instead of checking for the one we want. I don't suppose JCR/JackRabbit can
> handle custom permissions, so these conversion methods should probably just
> throw an exception.
> Consider the following test:
> {code}
> @Test
> public void doesNotAccountForCustomPermissions() {
> try {
> final String result = PermissionUtil.convertPermissions(64);
> fail("Should have failed - but returned ["+result+"] instead.");
> } catch (IllegalArgumentException e) {
> assertEquals("64 is not a standard permission code, please update
> your code to use XYZ instead.", e.getMessage());
> }
> }
> {code}
> Setting the priority to blocker to make sure this gets fixed before the
> release. Please reset to an appropriate priority when 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:
[magnolia-dev] [JIRA] Created: (DOCU-246) Document how to set utf-8 encoding for emails
Document how to set utf-8 encoding for emails - Key: DOCU-246 URL: http://jira.magnolia-cms.com/browse/DOCU-246 Project: Documentation Issue Type: Task Security Level: Public Components: content Reporter: Ruth Stocks Assignee: Ruth Stocks Document how to set utf-8 encoding for emails and add to Modules > Form. See forum discussion at http://forum.magnolia-cms.com/forum/thread.html?threadId=259d159e-86d8-4c62-af30-b1c2c1689aa3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Updated: (MGNLSTK-827) Section variation templates are not available
[
http://jira.magnolia-cms.com/browse/MGNLSTK-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antti Hietala updated MGNLSTK-827:
--
Attachment: availability-config.png
> Section variation templates are not available
> -
>
> Key: MGNLSTK-827
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-827
> Project: Magnolia Standard Templating Kit
> Issue Type: Bug
> Components: templates
>Affects Versions: 1.4.6
>Reporter: Antti Hietala
>Assignee: Philipp Bärfuss
> Attachments: availability-config.png,
> config.modules.extended-templating-kit.config.sites.demo-features.templates.xml,
> templates-missing.png, templates-present.png
>
>
> No availability is configured for section variation templates in the
> demo-features site. You can see the templates assigned to example pages but
> if you double-click the Template dropdown, they are gone. This is confusing
> for beginners.
> Define and bootstrap template availability configuration. Since the section
> variation templates are used only in the demo-features site, define them in
> the demo-features definition. This way they don't clutter the dropdown in
> demo-project. It also makes a nice example of how to extend the default
> availability.
> Find an XML export of availability configuration attached. It is from 4.5
> Beta 3 so it uses the new {{id}} property and {{: path>}} value. Import under Site Definitions > /demo-features.
> As a usability improvement, please sort the dropdown options following the
> order of template configuration nodes. All section templates should be next
> to each other so they are easier to pick.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to:
[magnolia-dev] [JIRA] Created: (MGNLSTK-827) Section variation templates are not available
Section variation templates are not available
-
Key: MGNLSTK-827
URL: http://jira.magnolia-cms.com/browse/MGNLSTK-827
Project: Magnolia Standard Templating Kit
Issue Type: Bug
Components: templates
Affects Versions: 1.4.6
Reporter: Antti Hietala
Assignee: Philipp Bärfuss
Attachments: availability-config.png,
config.modules.extended-templating-kit.config.sites.demo-features.templates.xml,
templates-missing.png, templates-present.png
No availability is configured for section variation templates in the
demo-features site. You can see the templates assigned to example pages but if
you double-click the Template dropdown, they are gone. This is confusing for
beginners.
Define and bootstrap template availability configuration. Since the section
variation templates are used only in the demo-features site, define them in the
demo-features definition. This way they don't clutter the dropdown in
demo-project. It also makes a nice example of how to extend the default
availability.
Find an XML export of availability configuration attached. It is from 4.5 Beta
3 so it uses the new {{id}} property and {{:}}
value. Import under Site Definitions > /demo-features.
As a usability improvement, please sort the dropdown options following the
order of template configuration nodes. All section templates should be next to
each other so they are easier to pick.
--
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:
