[mattrubinstein]

Sorry I’m not 100% sure which logs/permissions are relevant. The error log file doesn’t say much.

Here is my .htaccess file for /public_html, I don’t seem to have one in the highest directory I can access:

Code:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

SetENV PHPRC /home/ligature/public_html
AuthName “Ligature”
AuthUserFile “/home/ligature/.htpasswds/public_html/passwd”
RewriteCond %{HTTP_HOST} ^ligatu.re$
RewriteRule ^/?$ “http://www.ligatu.re/&#8221; [R=301,L]

Relevant permissions all seem to be 755 for directories and 644 for files.

Hope that helps, please let me know if there is any more specific information that would be needed.

Best

Matt

[mattrubinstein]

Thanks Key Master, that sounds good. Maybe some kind of “Please wait” like with the fancy login form would be useful too? And the other problem I was having with disabling the button was re-enabling it again if the validation fails. I’ll leave it with you!

[mattrubinstein]

Just to follow up on this, I seem to have solved the problem for now by inserting the following code at the beginning of the _onSubmitEvent function:

Code:

var now = new Date().getTime();

if ((this.beenSubmitted) && (now – this.beenSubmitted < 3000))
{
return false;
}
else
{
this.beenSubmitted = now;
}

So this disables any submission within 3 seconds of the last submission. Is this likely to have negative repercussions or is there a better way?

Thanks

Matt

[Author]

Posts