On Jun 29, 2011, at 12:32 AM, Danilo Ghirardelli wrote: > > I found the source of my problem at last, I'm posting it just in case the > same happens to you. > I copied the skeleton for the new project from another one that used Magnolia > 4.3.8, and had in the repositories.xml a couples of extra lines compared to > the same file of a 4.4.x version: > > <Map name="uri" repositoryName="magnolia" workspaceName="uri" /> <!-- > uri workspace, used currently only for authorization of uri access over > repository security-->
Looking at the latest code on 4.4 branch I don't see anything like that. Are you sure you have not copied such a file from trunk (5.0) ? > > <workspace name="uri" /> > > Those two lines caused a mismatching name for acls in Magnolia 4.4, but ONLY > in the uriSecurity filter where the workspace id is hardcoded and not get > with usual method. Lines removed and problem solved, but this was really hard > to find. > Now I'm really wondering how other updates to 4.4 have worked correctly even > starting from the same situation... Maybe it's just that in this case the > version gap was too wide and this caused some problem? > > > > I compared my "bugged" project acls with working ones, from 4,4 and 4.3 > branches. I was expecting that all acls generated by JCRAuthorizationModule > would have a name like "repo"_default, but I was wrong. > > Working project, acl names: > - dms_default > - uri_default > - website_website > - users_users > - mgnlVersion_mgnlVersion > - config_config > - userroles_userroles > - mgnlSystem_mgnlSystem > - Store_default > - Expressions_default > - usergroups_usergroups > - data_data > - media_media > > My current project, acl names: > - dms_default > - uri_uri > - website_website > - users_users > - mgnlVersion_mgnlVersion > - config_config > - userroles_userroles > - mgnlSystem_mgnlSystem > - Store_default > - Expressions_default > - usergroups_usergroups > - data_data > - media_media > > Uri is the only one that gets a wrong acl name, some gets "default" and some > get a duplicate repo name, I don't really understood why... > > By the way, while debugging I noticed that superuser role node seems to have > a few acls regarding the "forum" repository. Wouldn't be better to have the > forum module add whatever acl needs, when (and if) is installed? > > Regards, Danilo. > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- - Best regards, Jan Haderka, PhD. Magnolia International Ltd. http://www.magnolia-cms.com Magnolia CMS is a Red Herring Europe 100 winner: http://tinyurl.com/redherringE100 -------------------------------------- Magnolia® - Simple Open-Source Content Management ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
