Hi Brandon, it was me being stupid! The above policies would have worked but I was assigning the role with limitations (it was the standard editor role). Duh! Problem solved by the standard method of going away from it for a few hours and then looking again.
But having said that, I am wanting to have a system with multiple siteaccesses and a Template Look object for each one (so that they can have different logos). How might this be achieved?
Hi Brandon, it was me being stupid! The above policies would have worked but I was assigning the role with limitations (it was the standard editor role). Duh! Problem solved by the standard method of going away from it for a few hours and then looking again.
Hi Andy,
I'm glad you were able to solve that. :) I was going to suggest the default role/policy way but I didn't know if you were doing something exotic I never encountered.
But having said that, I am wanting to have a system with multiple siteaccesses and a Template Look object for each one (so that they can have different logos). How might this be achieved?
That is an excellent question. Greg McAvoy-Jensen, the Executive Director here at Granite Horizon, wrote a tutorial for how to do just that!
Yes, that is an excellent tutorial. I feel his section on multiple language multiple siteaccess eZ Publish setups could be improved with some information on how to switch between language versions. With 2 content trees, each with 2 language versions (so 5 siteaccesses in total including an admin backend) the switchlanguage operator seems to get confused and ends up redirecting to example.com! Somehow it must be reading from the default site.ini, but I can't see how. Everything else works fine.