Deserializing richtext unescapes html-entities

Open
#1,310 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
api

Research direction

Reproduce the issue with a Plone News Item or other richtext content using the HTML example in the report, then trace the API's richtext deserialization path. Check what changes after the first and second saves, and verify that HTML entities remain preserved rather than being unescaped unexpectedly.

Written by the indexing model from the issue text.

Description

01 type: bug

See https://github.com/collective/collective.exportimport/issues/99

To reproduce:

  • Create a News Item (or any content with richtext) in https://6.demo.plone.org
  • Paste the following in the richtext-field: <pre>Code example: <h2>Heading 2</h2> example &lt;h1&gt;heading 1&lt;/h1&gt;</pre>
  • Save
  • 🤯
  • Save again
  • 🤯 🤯
Dominant language
Python
Stars
109
Forks
107
Avg merge
2d 3h
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from plone/plone.restapi

All issues in plone/plone.restapi

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.