The vast majority of pages on my v6.2.1 site are secured under Public Access so the page tree has red circles on practically every node. Is there any "proper" way to disable the red circles?
In the meantime I've edited protect_overlay.gif so that it's just a transparent image, but I don't like hacking around in the Umbraco files so if there's a better way then I'd like to hear it :)
Why do you want to disable the "restricted access" logo?
I actually think that the way you've done it seems simple, quick and straightforward. Only caveat is that you need to overwrite it again if you need to do an upgrade.
Otherwise you could probably hook into the API somehow...but given the mentioned solution it sounds like too much work to me :)
I just wanted to disable it because it's a bit jarring having it plastered all over the backend, plus without it it's easier to see the document type of each page at a glance by looking at its icon.
Thanks for the response; I'll just leave it as-is :)
Public Access: Is it possible to hide red circle?
Hi,
The vast majority of pages on my v6.2.1 site are secured under Public Access so the page tree has red circles on practically every node. Is there any "proper" way to disable the red circles?
In the meantime I've edited protect_overlay.gif so that it's just a transparent image, but I don't like hacking around in the Umbraco files so if there's a better way then I'd like to hear it :)
Hi Chris
Why do you want to disable the "restricted access" logo?
I actually think that the way you've done it seems simple, quick and straightforward. Only caveat is that you need to overwrite it again if you need to do an upgrade.
Otherwise you could probably hook into the API somehow...but given the mentioned solution it sounds like too much work to me :)
/Jan
Hi Jan,
I just wanted to disable it because it's a bit jarring having it plastered all over the backend, plus without it it's easier to see the document type of each page at a glance by looking at its icon.
Thanks for the response; I'll just leave it as-is :)
is working on a reply...