You need to tell Installatron to stop using suPHP chmod values too. That's the "PHP server type" setting in Administration >> Settings >> Libraries. If the plugin is complaining about 644 on an suPHP server then it does sound like the plugin is only looking at the value and not testing to see if it'...

Are you using suPHP or something like that? If so, then Installatron automatically modifies the chmod values so that they're acceptable on. ie. 666 becomes 644 and 777 becomes 755. I can't think of any circumstance in which you would actually want 666 or 777 on an suPHP server. 644 and 755 should be...

Re error: The errors you're looking for won't show up in error_log, it will be in one of the filesystem*_log logs. The FS log is for all those $this->rm ->chmod ->write etc type commands. It would be interesting to see the entry for one of those CHMODs. I'll get back to you on out-of-install-directo...

Almost all support goes through our tickets system so this forum isn't being overworked at the moment. Installer stuff is probably ideally suited to it. So feel free to post any questions you have. Our long term plans include an overhaul of the installer system, and that will likely go with changes ...

You could use this addition to the version-level init.xml: <information> <info id="default-dir" value="default_directory_name"/> </information> Where default_directory_name would be "wp-content/plugins". However, as I said in the other post, I think you'd be better off asking for the Wordpress root ...

I don't think it should allow you to do anything higher than the install location, so I'm surprised that $this->write("../../sitemap.xml", ""); works. I'll speak to Phil about that today. But it looks like the CHMOD isn't working. If you look in the filesystem_install_log (from administration or /va...