joachim aus münchen
Sorry, Anika, in the meantime I have forgotten too many details
to give you a satisfactory answer. What I remember is:
In a redirect farm, you want to delete the directory
in order to prevent accidental utilisation; content
should only go to
At some point in the setup process, however, you may
still want to access configuration pages in <farmer>/conf.
This will result in an error message because <farmer>/lib/exe/css.php
includes <farmer>/inc/init.php which checks for the existence of
the <farmer>/data/ directory; at least, it does so before $conf
is overwritten appropriately.
My point is now: for accessing configuration pages, it is
irrelevant whether or not the directory data/ exists.
Always testing for the existence of data/ introduces
an unnessary dependence. Such testing should only be
performed when pages from data/ are actually needed.