[magnolia-dev] [JIRA] Created: (DOCU-249) New page that lists effective roles, groups and ACLs for any given user, group or role

New page that lists effective roles, groups and ACLs for any given user, group or role
--------------------------------------------------------------------------------------

                 Key: DOCU-249
                 URL: http://jira.magnolia-cms.com/browse/DOCU-249
             Project: Documentation
          Issue Type: Task
      Security Level: Public
          Components: content
            Reporter: Antti Hietala
            Assignee: Ruth Stocks

Document a new page that lists the roles, groups and ACLs for any given user, group or role. This feature is
tracked in MAGNOLIA-3938 and scheduled for 4.5.

Document the feature in {{/administration/security/}}, after ACL examples. Link to it from
{{/administration/security/users}} and any other pages you think are relevant jump-off points. Link
also from {{/search}}, where JCR queries are discussed, because people are likely to write a custom query
to get this information. With the new page, they don't need to.

--

-- 
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/

[magnolia-dev] [JIRA] Created: (BLOSSOM-76) Update template availability for Magnolia 4.5

Update template availability for Magnolia 4.5
---------------------------------------------

                 Key: BLOSSOM-76
                 URL: http://jira.magnolia-cms.com/browse/BLOSSOM-76
             Project: Magnolia Blossom Module
          Issue Type: Improvement
            Reporter: Tobias Mattsson
            Assignee: Tobias Mattsson
             Fix For: 2.0

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[magnolia-dev] [JIRA] Updated: (BLOSSOM-76) Update template availability for Magnolia 4.5

     [
http://jira.magnolia-cms.com/browse/BLOSSOM-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tobias Mattsson updated BLOSSOM-76:
-----------------------------------

    Description: Now possible to get Node as a parameter.

> Update template availability for Magnolia 4.5
> ---------------------------------------------
>
>                 Key: BLOSSOM-76
>                 URL: http://jira.magnolia-cms.com/browse/BLOSSOM-76
>             Project: Magnolia Blossom Module
>          Issue Type: Improvement
>            Reporter: Tobias Mattsson
>            Assignee: Tobias Mattsson
>             Fix For: 2.0
>
>
> Now possible to get Node as a parameter.

--

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

[magnolia-dev] [JIRA] Updated: (DOCU-178) Adding social media to your site

     [
http://jira.magnolia-cms.com/browse/DOCU-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antti Hietala updated DOCU-178:
-------------------------------

        Summary: Adding social media to your site  (was: Adding Blog Use Case)
       Assignee: Samuel Staehelin  (was: Suzanne Deprez)
    Description: 
Provide an overview of social media features you can add to a Magnolia site. Blog is only one of them.

Social media features:

* Collaboration: Public user registration with PUR module. Collaboration with Forum and Commenting
modules. Embedding an external poll.
* Blogs: Blog module
* Microblogs: Twitter integration with Frisbee or Twigs modules 
* Image sharing: Flickr integration with Frisbee or Twigs. Adding editorial Flickr images with a custom
DAM handler (Teresa's blog post).
* Social bookmarking: Default STK bookmarklets and how to customize them. ShareThis and AddThis with
Frisbee module.
* Social networking: Facebook like, share and commenting with Frisbee or Twigs
* Geographical location: Google Maps with Frisbee or Twigs
* Syndication: RSS feed generation and aggregation, microformats with Twigs
* Advanced social media mashups: VPRO's Pinkpop festival website uses Magnolia CMS, CouchDB and Camel.
The site harvests pictures and video uploaded by festival goers from the Internet and serves the
harvested media back to viewers in a single, browsable repository. Link to the
[presentation|http://www.magnolia-cms.com/community/magnolia-conference/archive/2010/program/presentation-day/pinkpop.html]
VPRO gave at the 2010 Magnolia Conference.

[magnolia-dev] [JIRA] Created: (MAGNOLIA-3957) Synchronize permission names between ACLDilog and Permission list

Synchronize permission names between ACLDilog and Permission list
-----------------------------------------------------------------

                 Key: MAGNOLIA-3957
                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3957
             Project: Magnolia
          Issue Type: Improvement
      Security Level: Public
            Reporter: Milan Divilek
            Assignee: Milan Divilek
             Fix For: 4.5

Create a map of names, which would contain synchronized names of permissions between
info.magnolia.module.admininterface.dialogs.ACLSDialogControl and info.magnolia.module.admininterface.pages.PermissionPage

--

-- 
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-unsubscribe <at> magnolia-cms.com>
----------------------------------------------------------------

Re: [magnolia-dev] Problem with Images error after adding blossom listener

[magnolia-dev] [JIRA] Updated: (MAGNOLIA-1757) Better Exception handling in Group and Role manager

     [
http://jira.magnolia-cms.com/browse/MAGNOLIA-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Milan Divilek updated MAGNOLIA-1757:
------------------------------------

       Assignee: Milan Divilek  (was: Philipp Bärfuss)
    Description: 
When the group doesn't exist info.magnolia.cms.security.MgnlGroupManager.getGroup(String) and
when the property of external user is null
info.magnolia.cms.security.ExternalUser.getProperty(String) unnecessarily log this
information. It makes problem example with ldap module.

  was:
signatures of methods like getGroup should be extended to allow PathNotFoundException, at the moment
PathNotFoundException is just
logged within a method.

> Better Exception handling in Group and Role manager
> ---------------------------------------------------
>
>                 Key: MAGNOLIA-1757
>                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-1757
>             Project: Magnolia
>          Issue Type: Improvement
>      Security Level: Public
>          Components: security
>    Affects Versions: 3.1 M3
>            Reporter: Sameer Charles
>            Assignee: Milan Divilek
>            Priority: Minor
>
> When the group doesn't exist info.magnolia.cms.security.MgnlGroupManager.getGroup(String) and
when the property of external user is null
info.magnolia.cms.security.ExternalUser.getProperty(String) unnecessarily log this
information. It makes problem example with ldap module.

--

-- 
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-unsubscribe <at> magnolia-cms.com>
----------------------------------------------------------------

[magnolia-dev] [JIRA] Updated: (BUILD-91) OutOfMemoryError when running ee-bundle

     [
http://jira.magnolia-cms.com/browse/BUILD-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Lipp updated BUILD-91:
-----------------------------

    Description: 
We regularly get OOME when building the ee-bundle on hudson. Increasing memory in MAVAN_OPTS (e.g. to
2048) did not help.

Example: http://hudson.magnolia-cms.com/view/X/job/ee_bundle/1771/consoleFull

  was:We regularly get OOME when building the ee-bundle on hudson. Increasing memory in MAVAN_OPTS (e.g. to
2048) did not help.

> OutOfMemoryError when running ee-bundle
> ---------------------------------------
>
>                 Key: BUILD-91
>                 URL: http://jira.magnolia-cms.com/browse/BUILD-91
>             Project: Build
>          Issue Type: Bug
>    Affects Versions: POMs 20
>            Reporter: Daniel Lipp
>            Assignee: Grégory Joseph
>            Priority: Critical
>
> We regularly get OOME when building the ee-bundle on hudson. Increasing memory in MAVAN_OPTS (e.g. to
2048) did not help.
> Example: http://hudson.magnolia-cms.com/view/X/job/ee_bundle/1771/consoleFull

--

-- 
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-unsubscribe <at> magnolia-cms.com>
----------------------------------------------------------------

[magnolia-dev] [JIRA] Created: (MGNLDATA-144) Validation does not work for subtype dialogs

Validation does not work for subtype dialogs
--------------------------------------------

                 Key: MGNLDATA-144
                 URL: http://jira.magnolia-cms.com/browse/MGNLDATA-144
             Project: Magnolia Data Module
          Issue Type: Bug
    Affects Versions: 1.6.4
            Reporter: Tobias Mattsson
            Assignee: Philipp Bärfuss

Validation of a subtype dialog uses configuration for the top-level dialog.

Steps to reproduce:
Create a type
Create a subtype
In the dialog for the type set name to be required=true

When you open the dialog for creating a subtype it renders correctly, dont fill in a name, when saving it will
require you to enter one because required=true in the parent.

Also, when the dialog reloads, it now displays the parent dialog instead, this already filed as MGNLDATA-127

--

-- 
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-unsubscribe <at> magnolia-cms.com>
----------------------------------------------------------------

[magnolia-dev] [JIRA] Updated: (MGNLDATA-144) Validation does not work for subtype dialogs

     [
http://jira.magnolia-cms.com/browse/MGNLDATA-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tobias Mattsson updated MGNLDATA-144:
-------------------------------------

    Priority: Major  (was: Neutral)

> Validation does not work for subtype dialogs
> --------------------------------------------
>
>                 Key: MGNLDATA-144
>                 URL: http://jira.magnolia-cms.com/browse/MGNLDATA-144
>             Project: Magnolia Data Module
>          Issue Type: Bug
>    Affects Versions: 1.6.4
>            Reporter: Tobias Mattsson
>            Assignee: Philipp Bärfuss
>            Priority: Major
>
> Validation of a subtype dialog uses configuration for the top-level dialog.
> Steps to reproduce:
> Create a type
> Create a subtype
> In the dialog for the type set name to be required=true
> When you open the dialog for creating a subtype it renders correctly, dont fill in a name, when saving it
will require you to enter one because required=true in the parent.
> Also, when the dialog reloads, it now displays the parent dialog instead, this already filed as MGNLDATA-127

--

-- 
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-unsubscribe <at> magnolia-cms.com>
----------------------------------------------------------------