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

Jan Haderka reopened MGNLSTK-1036:
----------------------------------


On master you are changing node to property for security callback. However 
there should be update task that changes all config nodes for securityCallbacks 
to properties in core already. So your update task here should be just renaming 
the property. Also what if that old node/property didn't exist at all? You 
should create it in such case.

> securityCallback is not working for custom pattern: PUR pattern not working
> ---------------------------------------------------------------------------
>
>                 Key: MGNLSTK-1036
>                 URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1036
>             Project: Magnolia Standard Templating Kit
>          Issue Type: Bug
>          Components: demoproject
>            Reporter: Christian Ringele
>            Assignee: Ondřej Chytil
>            Priority: Critical
>             Fix For: 2.0.7
>
>
> After setting the ACL of the PUR right (MGNLPUR-68), the standard login form 
> appears and not the PUR login form:
> http://demopublic.magnolia-cms.com/demo-project/members-area/protected.html?something
> Seems as the public securityCallback pattern is ignored.
> Besides:
> Its not viewable&changeable anymore, to what 'location' the default 'form' 
> pattern is matched to.
> So it can't be changed, and for beginners it can't be known where it will 
> apply 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/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to