Fran?ois G.

Hi Paul,

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

Regards,
Fran?ois

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

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

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

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!