Opened 11 years ago

Closed 10 years ago

Last modified 10 years ago

#195 closed defect (bug) (fixed)

Encoding issues on

Reported by: sergeybiryukov's profile SergeyBiryukov Owned by:
Milestone: Priority: normal
Component: Make (Get Involved) / P2 Keywords:



  1. The posts are now deleted pending further investigation, however there's still an issue with some names:
  2. The invalid characters in are actually non-breaking spaces. I could not reproduce the issue using WordPress Importer 0.6.1, so it appears to be specific to setup. Happy to help with additional debugging or testing if needed.

Change History (13)

#1 @SergeyBiryukov
11 years ago

Same issue on the Polyglots blog: (link).

#3 follow-up: @SergeyBiryukov
10 years ago

Same in contributor handbook: (link).

#4 in reply to: ↑ 3 @kpdesign
10 years ago

Replying to SergeyBiryukov:

Same in contributor handbook: (link).

Those are related to an issue we had last Friday with the CCH:

The editor is blank on 4 pages and 1 glossary item due to the encoding issues:

IIRC, the last time this happened, it had to be fixed in the database.

Last edited 10 years ago by kpdesign (previous) (diff)

#5 @SergeyBiryukov
10 years ago

  • Summary changed from Encoding issues on to Encoding issues on

#6 @Hanni
10 years ago

  • Cc h@… added

#7 @siobhan
10 years ago

  • Cc siobhan added

This ticket was mentioned in IRC in #wordpress-meta by sams. View the logs.

10 years ago

#9 @kpdesign
10 years ago

#569 was marked as a duplicate.

#10 @DrewAPicture
10 years ago

#650 was marked as a duplicate.

#11 @kpdesign
10 years ago

I've checked all of the encoding issues listed in this ticket, and all of them have been fixed except for the one in comment:2:

The editor is blank for this post - if this issue could be fixed, then we could close this ticket.

#12 follow-up: @coffee2code
10 years ago

  • Resolution set to fixed
  • Status changed from new to closed

@kpdesign: I fixed the encoding issue for the post

As such, I'm closing the ticket as fixed as your behest.

#13 in reply to: ↑ 12 @kpdesign
10 years ago

@coffee2code: Thank you for taking care of that - I appreciate it. :)

Note: See TracTickets for help on using tickets.