There are problems with this policy...
- If you have mutiple web servers, it is possible that a child space will be created on a different server than the parent space, in which case the folder will be on a different server and inaccessible via a parent space FTP account (unless we start making changes to Active directory manually... or maybe a dedicated FTP server setup of some kind). I beleive that if this setting is enabled DNP should check before adding new child spaces and force them onto the same server as parent.
-There is a quota calculation issue with this setting.
DNP calculates the files disk space of a child space twice when this setting is enabled. Once as part of the child space and once as part of the parent space files...
-Finally, an FTP user added to the parent hosting space will not have access to spaces created after the FTP account was added.
The workaround we found involves you changing the path of the FTP user to the new child space path, saving and then changing the path back to the parent space folder. This sets the necessary permissions on the child space.
This should be happening automatically.
These are the issues we found that make using this setting very problematic.