Details
Description
Steps to reproduce:
- Create a new Event document
- Add a none breaking space to the xinha field by entering ctrl-space, space, some character.
- Save and close
- Publish
- Edit the xinha field by adding a character
- Save and close
Observed result: the xinha field is not displayed
Old description:
Xinha field text does not show anything upon showing the document in the CMS in the 'preview'.
Xinha field does show when editing a document. Also does show after a publish action.
Document where it happens: news\hidingbody,
To reproduce:
1. Publish the document
2. edit this document
3. add/remove something in the Body field.
4. save & close
5. you'll see the body being empty.
6. Hit edit or publish the document and you will see that there is text in the body field.
Content inside the body text field: (st<p>
<script type="text/javascript" src="http://bb.bbvms.com/p/QuickTour2_526/c/1089249.js"></p><span id="XinhaEditingPostion"></span>
</script>
</p>t)
It also happens with other content such as: (<p> st sd gf as
</p>)
In the logs I see the error Junaidh mentioned in CMS7-4464 (13.09.2010 10:19:18 ERROR [org.hippoecm.addon.workflow.WorkflowsPlugin.onModelChanged():112] 54672a2f-e513-4c78-8b28-f336b8c07f2b: the item does not exist anymore
javax.jcr.InvalidItemStateException: 54672a2f-e513-4c78-8b28-f336b8c07f2b: the item does not exist anymore)
Also other errors with seems to be with this document: (13.09.2010 10:19:18 WARN [org.hippoecm.frontend.plugins.xinha.htmlcleaner.HtmlCleanerPlugin.clean():73] Returning uncleaned HTML because cleaner component produced an error.
13.09.2010 10:19:18 ERROR [org.hippoecm.frontend.editor.viewer.ViewerPlugin.createTemplate():100] Unable to open template)
More from the logs: ([Fatal Error] :11:10: The entity "nbsp" was referenced, but not declared.
javax.jcr.InvalidItemStateException: 45c9a2db-3622-4546-90d4-5803f6c7fdc3: the item does not exist anymore
javax.jcr.InvalidItemStateException: 45c9a2db-3622-4546-90d4-5803f6c7fdc3: the item does not exist anymore)
I'm not 100% sure if those errors/warnings from the log are relevant here. Was unable to reproduce this without having a nbsp or a script element in the html.