FileManager backend: fixes as follow-up on the last merge: make sure all default option/configuration paths are coded so they are consistently pointing at various mootools-filemanager subdirectories and files.
FileManager backend: fixes as follow-up on the last merge: make sure all default option/configuration paths are coded so they are consistently pointing at various mootools-filemanager subdirectories and files.

Note that, previously, our code did for a while assume user-specified relative paths were relative to the path of the main script loading this file/class (SCRIPT_NAME). While this seemed like a good idea at the time, it makes for hard-to-predict results when PHP scripts residing in multiple directories do handle server requests and use the fileManager class in doing so.

Requests may post/submit relative paths as arguments to their FileManager events/actions, and those relative paths should preferably be relative to the request URI path, i.e. SCRIPT_NAME, but any relative paths specified in the FileManager options[] array passed to its constructor will, for reasons of consistency and security, always be considered relative to the FileManager.php path itself: this ensures we won't have any unpleasant surprises regarding important directory roots such as options['directory'].

cpojer/mootools-filemanager,cpojer/mootools-filemanager