XF 1.4 Registration problem. "The field 'xxxxxxxx' was not recognised."

[rdn]

Registration Page error:



Page Source:


Why is that?
Already tried most of the things that might be related but still I can't find the reason
Happens maybe once in every 5 first load of Registration page.
Sometimes page works fine.

 

[rdn]

Maybe related to this:

Registration Form Modifications
No images for this part as nothing should be visually different!

The registration form now includes several approaches to interfere with bot registrations, including:

• Invisible honeypot fields that legitimate users won't see but that bots will (usually) see and fill in. If a value is entered, we know the user is a bot.
• The honeypot fields are also inserted randomly in multiple places, which can cause the valid fields to be in different positions (internally; visually they are the same). This can interfere with some bot implementations.
• Field name randomization. Each time the form is viewed, the name of the fields that are submitted to the server varies and thus cannot be predicted by a bot.

 

[Paul B]

It's more likely related to an add-on.

Did you ever test with all add-ons disabled and in a completely unedited default style, as I suggested in the ticket?

The current thinking is it could be related to [bd] Cache.

 

[rdn]

The current thinking is it could be related to [bd] Cache.

I already disabled BD Cache.

Did you ever test with all add-ons disabled and in a completely unedited default style, as I suggested in the ticket?

The only thing I still didn't tried is disable all addon.
For my forum size, hard enough to easily setup a test site.
But I will if my time allow

 

[Paul B]

The first step of troubleshooting is always to test in a default style with all add-ons disabled.

It saves time and effort in trying to track down issues related to add-ons, which we are obviously not familiar with.

 

[Mike]

You also need to disable anything on the server level which is doing caching as well. This issue is down to the registration form being served from a cache.

 

[rdn]

I'm 80% SURE this is related to fastcgi_cache
I just disabled fastcgi_cache of Nginx on the forum and no problem on registration page anymore.

 

[HWS]

You need to exempt the registration form from the cache. Then your cache will work without problems.

 

[rdn]

Yes I already did that like this:

set $no_cache 0;
# Don't cache uris containing the following segments
if ($request_uri ~* "(/register|/login)") {
set $no_cache 1;
}

But then I think those ajax validation (username and email form) still being cached.

 

[rdn]

I'm 80% SURE this is related to fastcgi_cache
I just disabled fastcgi_cache of Nginx on the forum and no problem on registration page anymore.

Just an update, even if fastcgi_cache already disabled.
Still I received some emails complaining that they can't register with the same error.
But I can't even replicate it myself
So not a problem with fastcgi_cache.

Maybe related to memcached? or zend opcache
That's the only caching playing on registration page.

 

[rafass]

I tried and works fine:

 

[rdn]

I tried and works fine:

Yeah it works fine most of the time.
I have an average of 400-500 user's registered per day but only a few encounter it.
Maybe 3-5 people a day report this issue.

 

[rdn]

I track it down.
It's related on Memcached Caching, sometimes memcached connection fail that error happens.

 

[Mike]

That's not particularly surprising then. If you're putting sessions in Memcache and the connection fails, the session can't be loaded so all sorts of unexpected things can happen.