Problems with 2.1.5

open_basedir restriction in effect

That sounds like a server configuration issue. Have you spoken to your hosts about it?

OK, after a bit of research, It appears that this limitation is a standard on all Plesk servers.

It is defined in the httpd.include file, located in the conf directory, for every domain, by the following lines:

<IfModule mod_php4.c>
                php_admin_flag engine on
                php_admin_flag safe_mode off
                php_admin_value open_basedir "/var/www/vhosts/<DOMAIN>/httpdocs:/tmp"

Therefore I advise the creator to revisit the plugin’s code, otherwize any WP hosted on a Plesk server will report the same problem!

Hi Fran?ois,

I hear you on this and I think there’s a way around it. But this plugin is actually written to be as vastly compatible with hosting as possible.

I can try tweaking this a little and see what results you get, but it might actually mean you wont be able to do the firewall override.

There may be a native WordPress filesystem check that might get around this for me, but I’ll need to dig into it.

Thanks for pointing this out. If I release an update, would you be open to trying it and reporting back for me?

Thanks,
Paul.

Hi Paul,

I have reviewed all my blogs, and I have new information on the problem.

It seems to happen only if the WP is hosted on a “Debian Plesk” server, as I have no problem with WPs hosted on “CentOS Plesk” servers.

On the “Debian Plesk” server, all WPs that still use v2.0.3 are not affected, and all that have been updated to v2.1.5 are… but one!!!

(No idea why not, WPSF config is identical to all the others’…)

Unfortunately I have no blog in v2.1.4 to compare.

Searching further, I could pinpoint that when, in the Dashboard page, under General Plugin Options, I disable the option Enable Login Protect, the problem disappear.

Once reactivated, the dreaded lines come back.

I hope this can help narrow your search…

And I am all OK to try & report to you!

Regards,
Fran?ois

Hi Fran?ois,

Okay, I’ve released v2.2.0 to be as file system compatible as it gets. I might have missed some places where it’s using older file system methods, but basically they all try to, where possible use the WP Filesystem object and thereby it will also mask errors where they occurs.

So, while this might mean you wont get certain errors, it’ll also mean certain functionality may not work for you on sites that have these file system limitations.

Give the latest version a shot sure and see what you get.
Cheers,
Paul.

Hi Paul,

I have just finished updating all the blogs on the Debian server, and they are all working fine now.

The lines at the bottoml don’t show anymore, even with the Login Protect enabled.

Excellent job, thanks a lot!

Yet I have to confess that I don’t know how I could check if all WPSF functionnalities are operational or not…

Regards,
Fran?ois

The only things that wouldn’t work for you fully are:

1) firewall switch off overrides (mentioned in the FAQs)
2) login cooldown period. This will work in part, but will be limited by how quickly your site can update the db. It uses a file to mark the date of the last login which more reliable than a db entry.

Otherwise though, you’ll be getting everything ??

Cheers!
Paul.

1) Not a problem, I have SSH access to all my websites.
Therefore I can go “under the bonnet”, should need be.

2) If someone (or rather something) tries to repeatedly login, even if WPSF cannot enable the cooldown period quickly enough, I have also installed another plugin, that will stop the intruder, if he tries various login codes…
??

Regards,
Fran?ois

Cool,then it looks like you’re sorted then ??

Thanks again for pointing this out… I appreciated.

If you don’t mind, would you be interested in a leaving a review of the plugin? It just helps raise the profile a little.

Thanks,
Paul.

Hi Paul,

I just left a five star review for WPSF.
:))))

Regards,
Fran?ois

Thanks dude… really appreciate that! ??

Cheers,
Paul.