|
Ian Just
|
July 5, 2015 at 4:51 pm
If someone presses the return key while filling out a text field, they get an error displayed:
HTML tags are not permitted in this field.
If they resubmit the data, the error becomes
Your form data could not be applied to any valid registration.
|
|
Ian Just
|
July 5, 2015 at 4:51 pm
This is with EE 4.7.6.p on WP 4.2.2
|
|
Dean
|
July 6, 2015 at 1:59 am
Hi Ian,
I can confirm this is occurring, I will get a developer ticket raised to look into it. Currently I do not have a workaround for it.
|
|
BRAC
|
July 6, 2015 at 5:17 am
This is happening for our customer as well! Please can you fix asap.
|
|
Josh
|
July 6, 2015 at 7:48 am
Hi Simon and Ian,
You can fix this by going into the Registration Form > Questions editor and changing the Question type from Textarea to HTML Textarea.
|
|
BRAC
|
July 6, 2015 at 8:04 am
Hi,
That is fine for Text area but I have been told that it is also happening with just text as well.
Can you check if that is the case. I don’t want to have lots of text areas when I should just be using text.
Thank you.
Simon.
|
|
Josh
|
July 6, 2015 at 8:13 am
Hi Simon,
If you need to allow for more than one line of text, you should be using textarea, not text.
|
|
BRAC
|
July 6, 2015 at 8:15 am
Yes I understand that but my client is telling me they are getting the error on a text field as well as the text area. I have changed them all to Textarea in the sort term. Are you able to test to see if text fields are having an issue?
|
|
Josh
|
July 6, 2015 at 8:26 am
It turns out that Text fields are not designed to handle multi lines. Please see this stackexchange thread for more information:
http://stackoverflow.com/a/6262507
|
|
BRAC
|
July 6, 2015 at 8:31 am
Hi Josh,
I would not expect them to. Can you tell me why this is happening? Is it because the users are cut and pasting from further up the page and it is picking up some html and thus throwing an error?
Simon.
|
|
Josh
|
July 6, 2015 at 8:57 am
Hi Simon,
Can you check your registration page to see if the text fields throw an error when no line breaks or other HTML is added?
|
|
Lucas
|
July 7, 2015 at 1:37 am
Hi,
Well this might explain the error reports I’ve received from a few participants.
bonnevillespeedtrials.com
We have a rather extensive form process for registration that, based on reports, has been encountering issues of this “HTML Tags Are Not Permitted in this field” since at least update 4.7.2. Replicating an error was not happening earlier. Reading other posts I have ensured all other plugins were off that might interfere.
Updated to 4.7.6 this evening after receiving an email from a participant trying to sign up from Australia that is encountering this error. Participant was registering using Chrome.
If the issue is input validation and EE is not handling it properly, I’ll need more information to adjust and recommendations on a mitigation.
|
|
Lucas
|
July 7, 2015 at 1:51 am
Hi,
Update on my testing.. Adding an extra space at the end of the form field entry is causing an error in addition to new lines in Chrome. Remove the space or the lf at the end of the line and the input is accepted. Extra space or lf at end of line and it throws the “HTML Tags Are Not Permitted in this field” error.
|
|
BRAC
|
July 7, 2015 at 2:14 am
Hi Lucas,
So if the field is a text field adding a space throws the error?
Simon.
|
|
BRAC
|
July 7, 2015 at 2:19 am
Is there such a thing as a html text field like a html text area? If that was the case EE could release an update and we just need to change our questions. They could also remove the validation of course for a quick fix.
I have changed all of my questions to html text area for the short term until this is fixed but it sounds like that would be a laborious job.
|
|
Dean
|
July 7, 2015 at 8:04 am
Hi Lucas,
Thanks for that information. I can confirm the additional space in the text field is triggering the validation. I’ll update the ticket to advise this.
|
|
Dean
|
July 7, 2015 at 8:06 am
Hi Simon,
No there isn’t an HTML text field. The developers will look into this and resolve it, most likely by tweaking the validation to not trigger with white space.
We will get back to you on this once we know more.
|
|
Bob Randklev
|
July 7, 2015 at 9:56 am
Our client started reporting this last week, it has to do with spell check.
When a mother tried to register their daughter Alivia the spell check caused the error.
They can’t use St. for street, they have to spell out Street.
I disabled extra plugins on Friday to get through the weekend and they report it’s still happening.
|
|
Lucas
|
July 7, 2015 at 11:07 am
Hi Simon,
I was seeing the error in the “text field” and in the “text” input type.
WP version 4.2.2
EE Version 4.7.6
Forgot to add all of the details this morning 🙂
Thanks,
Lucas
Missed a few of the important details this morning.
|
|
Josh
|
July 7, 2015 at 11:16 am
Event Espresso 4.7.7.p is released and fixes the issues that may occur with validation. Please note that the validation was not removed because removing the validation can potentially cause a security vulnerability.
|
|
Bob Randklev
|
July 7, 2015 at 2:56 pm
Thanks Josh we applied the update 30 minutes ago so we’ll monitor and report any other problems
|
|
Lucas
|
July 7, 2015 at 6:26 pm
Thanks for getting an update turned around so quick. We’ve just applied the update and Iwe’re beginning testing.
|
|
Lucas
|
July 7, 2015 at 9:10 pm
It looks like the update fixed the glitch. Thanks again!
|
|
Dean
|
July 8, 2015 at 6:49 am
You’re welcome!
Thanks to everyone for bringing this to our attention, it’s much appreciated!
Please do let us know if this re-occurs.
|
