I have a node, with children and sub children etc., that is only used by the administrators of the site - it is used for storing different kinds of data/info. All this info should not be accessable through the frontend - i could set up a password protection, but would prefeer if the content was completly "unknow" to the frontend - any best practices on this? One could just not publish it, but what if it was done by a mistake etc.
The presence of the document (nodes) themselves do not immediatly make the data of those documents available to the front-end. You would have to apply a template to the documents specifying which data to display. The good news is that if you don't assign a template, or you assign a blank
template(one without any page fields), this would basically "hide" it from the front-end. If they went to the url they would get nothing, blank page.
If you wanted to further hide the existence of the page, you could add a rewrite rule in the config/urlrewriting.config file to navigate all pages under a
certain directory to the 404 page. Everyone would think the page(s) don't exist.
You will also want to make sure you exclude the document type(s) that are private from your xslt macros displaying pages or feeds of pages.
Protect/hide node and children?
I have a node, with children and sub children etc., that is only used by the administrators of the site - it is used for storing different kinds of data/info. All this info should not be accessable through the frontend - i could set up a password protection, but would prefeer if the content was completly "unknow" to the frontend - any best practices on this? One could just not publish it, but what if it was done by a mistake etc.
Dinovo,
The presence of the document (nodes) themselves do not immediatly make the data of those documents available to the front-end. You would have to apply a template to the documents specifying which data to display. The good news is that if you don't assign a template, or you assign a blank
template(one without any page fields), this would basically "hide" it from the front-end. If they went to the url they would get nothing, blank page.
If you wanted to further hide the existence of the page, you could add a rewrite rule in the config/urlrewriting.config file to navigate all pages under a
certain directory to the 404 page. Everyone would think the page(s) don't exist.
You will also want to make sure you exclude the document type(s) that are private from your xslt macros displaying pages or feeds of pages.
Here's some info on rewriting:
http://www.urlrewriting.net/149/en/home.html
-Chris
is working on a reply...