You are viewing limited content. For full access, please sign in.

Question

Question

LF 12 One or more form fields contain illegal character combinations

asked on March 12

Just upgraded to Laserfiche 12 and we came across this message when submitting a form.  One or more form fields contain illegal character combinations (for example, "&# or '<' next to (a-z, /, ?, !)"). Please remove these characters before submitting the form. [LFF2111-RequestValidationException].  our last version was 10.4.  is this a bug?

 

 

0 0

Answer

SELECTED ANSWER
replied on March 17 Show version history

yes, i've realized that the < and > was the issue.  The completed comment was using a stored procedure to grab data sources from a different database.  I had to modify the stored procedure to replace the angled brackets with parentheses instead.  that seem to have fixed the issue.  

2 0

Replies

replied on March 13

Do you get this error when submitting any form or just this specific one? 

Check the following logs for any insight, as if a specific field is the cause, the logs may reference the field number to check:

Event Viewer > Applications and Services Logs > Laserfiche >Forms >App. Obtain Admin and Operational log.
Forms debug logs under C:\ProgramData\Laserfiche\Forms\Logs

0 0
replied on March 16

You can see it on your screenshot I think - that Completed Comment field has values in the middle of it that look like a username or something surrounded by < and > characters.  I think everything from 11 onward has been pickier about that kind of thing.  I've encountered similar behavior when any HTML code ends up in a field from some customization I'm doing.

Depending on what you are doing - could you have some change your process to not use < and > characters - or perhaps have a Javascript replace them? 

1 0
SELECTED ANSWER
replied on March 17 Show version history

yes, i've realized that the < and > was the issue.  The completed comment was using a stored procedure to grab data sources from a different database.  I had to modify the stored procedure to replace the angled brackets with parentheses instead.  that seem to have fixed the issue.  

2 0
You are not allowed to follow up in this post.

Sign in to reply to this post.