Fixed The field 'custom_fields[xxxxxx]' was not recognised.

[dabollicks]

Found this little problem

Ive added 2 custom user fields, no problem with that. This problem arises when a user actually fills out the details within these custom fields.

It saves the details, but just puzzling why this error occurs


Is this a bug? Or am i just being special?

 

[MGSteve]

I know its already been confirmed, but I've just got this when I've gone to create a temporary account too.

Not all of them do it, only one of them.

I wonder if the presence of brackets has something to do with it?

 

[Mike]

Fixed.

 

[SchmitzIT]

Fixed.

Is there a quick work around we could employ ourselves, or should we just wait for beta 3?

 

[Mark3121]

Fixed.

Was this fixed for beta3, I'm still getting this.

Thanks

 

[MGSteve]

It was fixed in Beta 2 for me....

 

[Mark3121]

Strange, I don't have any outdated templates so at the moment I'm hiding it with

.formValidationInlineError {
display: none !important;
}

 

[latimer]

It was fixed for the regular profile field in beta 3, but I still see this when I edit a user's custom field in the admin panel.

 

[Paul B]

Confirmed, so I've moved the thread back to bugs.

Mike, this now relates just to the ACP.

 

[Kier]

Should be fixed now.

 

[John L.]

Should be fixed now.

Kier could you post the fix so we could apply to our test installations. Really annoying when doing addon dev work and testing .

 

[Kier]

This is the fix.

 

[Mark3121]

This is the fix.

I still have this problem on beta4, if someone could help me with what to do with Kiers's fix I'd be grateful.

 

[Andrej]

I still have this problem on beta4, if someone could help me with what to do with Kiers's fix I'd be grateful.

http://xenforo.com/community/threads/b4-js-problem-in-acp.22214/#post-279162

 

[markku]

Why am I still getting this?

Just upgraded to 1.1 and filling in the custom field on personal details page works fine, but if I have the custom field enabled for registration page, it gives this exact error as in the first post on this thread.

edit: tested now. when registering, it gives the custom_fieldsx xx was not recognised error, but still saves the info entered in the custom field and it shows up correctly.

why it shows the error?


--
I can hide the error by having the following on extra.css, but to be honest I'd rather have this fixed some other way..?
.formValidationInlineError {
display: none !important;
}

 

[Paul B]

That's a separate bug which has now been fixed: http://xenforo.com/community/thread...m_field_companyname-was-not-recognised.24519/

It will be in the next release.