Bug 1056296 - Parse errors in updating homepage html are not shown to the user
Summary: Parse errors in updating homepage html are not shown to the user
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Zanata
Classification: Retired
Component: Component-UI
Version: 3.4
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 3.7
Assignee: Sean Flanigan
QA Contact: Ding-Yi Chen
URL:
Whiteboard:
Depends On: 1198433
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-21 22:33 UTC by Damian Jansen
Modified: 2015-07-22 02:19 UTC (History)
3 users (show)

Fixed In Version: 3.7.0-SNAPSHOT (git-jenkins-zanata-server-github-pull-requests-3566)
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-07-22 02:19:45 UTC
Embargoed:


Attachments (Terms of Use)

Description Damian Jansen 2014-01-21 22:33:39 UTC
Description of problem:
Entering some level of invalid html will generate a parse error, eg.
08:21:56,991 WARN  [org.jboss.seam.ui.component.UIFormattedText] (http-/127.0.0.1:8080-2) Seam Text parse error: expecting a doublequote \", found '''
Despite not being an "error" per se, it could be indicated to the user as a notification along with the "Home content was successfully updated." message.

Version-Release number of selected component (if applicable):
3.3

How reproducible:
Easy always

Steps to Reproduce:
1. Sign in as admin
2. Click the Home button
3. Press the "Edit Page Code" button
4. Enter into the box:
<img src="<some image url>" width='600' />
5. Press Update

Actual results:
The warning is displayed to console:
Seam Text parse error: expecting a doublequote \", found '''
but is not shown to the user.

Expected results:
Some kind of error notification

Additional info:

Comment 1 Sean Flanigan 2015-05-15 05:02:30 UTC
Eliminating Seam Text should eliminate Seam Text parser errors: https://github.com/zanata/zanata-server/pull/732

Comment 2 Ding-Yi Chen 2015-05-18 08:19:27 UTC
VERIFIED with Zanata 3.7.0-SNAPSHOT (git-jenkins-zanata-server-github-pull-requests-3566)


Note You need to log in before you can comment on or make changes to this bug.