This wasn't the problem, if a path was set via the command line it would and must be the absolete path. It's basically overriding the default path set in the site manager.
The conflicting problem with allowing remote paths via the command line was resolved many many builds ago (as far back as v2.1 I think). Sadly this feature was forgotten about. I'll see about getting it into v2.2
|