Web content validation should be more clear with reasons for failure
Activity
Show:
Justin Choi August 6, 2012 at 12:43 PM
PASSED Manual Testing following the steps in the previous comment.
Fixed on:
Tomcat 7.0 + MySQL 5. Portal 6.1.x CE GIT ID: 6c9e7fe207e249a675df09752b429c5deb8267ea.
Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: e2ce76354f70f8f7475421fd124f5d3996169824.
Invalid characters will be logged in the console if log level is set to ERROR.
Justin Choi August 6, 2012 at 10:03 AM
Committed on:
Portal 6.1.x CE GIT ID: a9a0096e0ff6fe2ee5c1ba59d4ef25f7de84b8b0.
Portal 6.2.x GIT ID: 0bcfe9b1f94b41e218cfe58de4fe0fc75b9f9c7b.
Fixed
Details
Assignee
SE SupportSE SupportReporter
Brett SwaimBrett Swaim(Deactivated)Branch Version/s
6.1.xBackported to Branch
CommittedLiferay Contributor's Agreement
AcceptGit Pull Request
Components
Affects versions
Priority
Medium
Details
Details
Assignee
SE SupportReporter
Brett SwaimBranch Version/s
6.1.x
Backported to Branch
Committed
Liferay Contributor's Agreement
Accept
Git Pull Request
Components
Affects versions
Priority
MediumZendesk Support
Linked Tickets
Zendesk Support
Linked Tickets
Zendesk Support
Linked Tickets
Created June 15, 2012 at 5:20 PM
Updated June 24, 2023 at 3:54 PM
Resolved June 16, 2012 at 8:49 AM
Right now if you have an invalid character, it's impossible to know what it is. We should enable logging that will explain what character is wrong, even if it's just in the server logs.