UX Error handling: structure xml editing fails to give feedback about invalid xml upon "Update"

• Type: Feature Request
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 5.2.3
• Fix Version/s: None
• Component/s: Legacy, Legacy > Control Panel menu
• Labels: None
• Environment: Windows XP, Tomcat 5.x
• Similar Issues: Show 4 results ; ;

  LPS-5505	WCM Structure Editor - UX Improve error messages
  LPS-12116	Web Content fails to render when there's no default language content in the XML file
  LPS-29696	As a DDL administrator I should be able to view and edit the structure XML directly
  LPS-27919	Kaleo Designer doesn't explain how content is invalid

When editing structure, I clicked "Launch Editor" and edited the xml. I left out a closing tag for dynamic-element. The application threw me back to the Control Panel main page when I clicked "Update" and did not display an error message. ERRORs were logged to catalina.out, but I think a user would be confused by this behavior if they did not have access to the server logs. Some notification of "Invalid" or "Poorly Formed" XML would be helpful

[Cynthia Wilburn]

We would like to recommend that you evaluate this ticket in the upcoming weeks to confirm that it is reproducible in the recently released 6 CE GA. As the reporter of the ticket, you may click "Accept Contribution" in the workflow to indicate that it can be considered resolved or you may reactivate it by selecting the "ReOpen by Reporter" link in the workflow.

In recent months Liferay has received a significant number of anomaly reports many of which are really requests for help. Because of this fact, the real bug reports are no longer easily identifiable. To remedy this problem we are asking for your assistance. We will be working towards closing open tickets that meet specific criteria and ask that you reopen those that are truly bug reports. We'll be monitoring those tickets so that they are properly managed.

Thank you,
The Liferay Team

ACW120109

[Randy Zhu]

In preparation for Ideation; we are merging New Feature and Improvement tickets into a singular ticket type called “Feature Request”. Additional information to follow soon.