We are migrating CKEditor issue tracking to GitHub. Please, use GitHub to report any new issues.

The former tracking system (this website) will still be available in the read-only mode. All issues reported in the past will still be available publicly and can be referenced.

Important: we decided not to transfer all the tickets to GitHub, as many of them are not reproducible anymore or simply no longer requested by the community.
If the issue you are interested in, can be still reproduced in the latest version of CKEditor, feel free to report it again on GitHub.
At the same time please note that issues reported on this website are still taken into consideration when picking up candidates for next milestones.

To report a new issue, go to https://github.com/ckeditor/ckeditor-dev/issues and follow the instructions in the issue template.

Context Navigation

← Previous Change
Ticket Comment History
Next Change →

Changes between Initial Version and Version 1 of Ticket #8704, comment 8

Timestamp:: Jul 10, 2012, 1:52:48 PM (12 years ago)
Author:: Amy McCrobie
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #8704, comment 8

initial	v1
1	1	I noticed the status of the ticket was changed to closed and realized I needed to update the ticket with my findings...
2	2
3		Changing the encoding on the database did not resolve the issue.
	3	Changing the encoding on the database did not resolve the issue. The database, its tables and fields, and all pages on my site are now set to encode with UTF-8.
4	4
5	5	On one occasion, the database field contains the text "<p>6/20<br />%uFFFD</p>".