Since this commit which removed the ability for anonymous/authenticated users to view nodes, when a site is disabled, guests get 'Access denied' viewing the 'disabled' page rather than the disabled page itself.
I can't remember why we implemented this - I enabled 'access content' for the anonymous user, which allowed me to view the Disabled page as expected. I confirmed I was still unable to access various other nodes like sites, packages, tasks etc - I suspect that these restrictions are being caught by other specific access controls per node type, which is good.
This being the case, can we re-instigate setting the 'access content' setting for the anonymous user in the hostmaster.profile?
Comments
Comment #1
Anonymous (not verified) commentedI think we can enable the permission 'access content' for 'anonymous users'. I don't think this privilege will expose any other nodes to anonymous users, because all other node types such as server, platform, site, package and task have their own 'view' permission that is also unchecked for anonymous users.
Unless Antoine or Adrian can see this turning into a migression, I'll be committing this, it's crazy to have a disabled disable page :)
Comment #2
adrian commented"This being the case, can we re-instigate setting the 'access content' setting for the anonymous user in the hostmaster.profile?"
no.
this caused all kind of trouble before.
Comment #3
Anonymous (not verified) commentedOK...
How about a 'view disabled sites' permission in hosting_site and change the 'access arguments' to /hosting/disabled to be 'view disabled sites' from 'access content'
Comment #4
Anonymous (not verified) commentedThats what i ended up doing.