Object Replacement Character in post title crashes Gutenberg 11.4.0/11.4.1 #34602
Comments
glendaviesnz
added
the
[Type] Bug
|
I was able to replicate this on latest trunk. |
|
I experienced a customer with thi sissue as well. Their title was The "Attempt Recovery" button had no effect. I had to enable the Classic Editor, rewrite the title, save, then I was able to re-open the blog post in Gutenberg. Error output from Gutenberg: |
getdave
added
[Feature] Rich Text
|
Also able to replicate.
Looks like the code that invokes pointer = append(
getParent( pointer ),
fromFormat( {
...replacements[ i ],
object: true,
isEditableTree,
} )
);If we examine this code we can see that there is an explicit code path for the object replacement character so it's obviously a scenario that we are expecting to handle.
Also note that |
|
Encountered on 6 separate sites. |
|
I had a user case with the same issue. |
1 similar comment
|
I had a user case with the same issue. |
|
I encountered another case on a WordPress.com site. |
|
Experienced this bug on a page with extra spaces in the page title. |
|
Just had a user case with the same issue on WordPress.com. Editing the post titles with Quick Edit seems to have resolved it, so that's a workaround if shuffling between Classic and Gutenberg isn't an option. |
|
Encountered another WordPress.com site having similar issue. Editing post titles with "Quick Edit" is an excellent workaround in removing the additional space behind post titles. |
github-actions
bot
added
the
[Status] In Progress
|
I do have a patch for this, but the number of reports here make me suspicious. Is this character appearing in post titles as a side effect of another bug, or are folks actually copying this value over? |
|
Encountered another WordPress.com case today. This is really weird — it does make me feel like it's being added by another bug! It was added to the beginning or end of most but not all posts. |
I spoke to someone who experienced this last week (including the inability to edit afterwards), but I haven't experienced it myself. They were copying the post title over from MS Word. I noticed the object replacement character showed as a blank space in the source HTML of their published post and when I mentioned this, they noted that there was also a space at the end of the post title in Word, which leads me to assume it's being copied in accidentally in at least one or two cases. |
|
I had another case in WordPress.com. The user copied the text from a MS Word doc and they had a blank space at the beginning of the post title. |
|
This is now being worked on in #34851. Essentially we'll not allow the character to be inserted at all. |
|
The issue reported at https://wordpress.com/forums/topic/project-wont-show/ regarding https://elisecutoneportfolio.wordpress.com/portfolio/maui-food-bank/ seems very similar, but I'm not seeing any replacement characters. |
|
Encountered another WordPress.com site with the issue. Editing a post title with "Quick Edit" worked like a charm. |
|
Another WordPress.com site experiencing this issue. Editing with "Quick Edit" is the easiest solution. |
|
Another site experiencing the same issue. I also found editing the title using quick view worked. |
|
Encountered today on a site where the user copied and pasted the title from Microsoft Word. Solved by removing OBJ symbol in Classic View -> Quick Edit. |
|
Another report of this, same cause: copying and pasting the post title over from MS Word. User couldn't see the OBJ symbol in Classic View, using Safari. |
|
I have another report like this in chat as well. Tried to guide the user to remove it themselves from Classic View editor. |
Issue Has Been FixedThis issue has now been fixed in #34851. That will be available when Gutenberg 11.6.0 is released. Update your sites when it's available to get that fix. |
|
Ran into this on a .com Personal plan site |
|
Ran into this on another .com Business site with plugins; let them know this will be resolved with the next Gutenberg update, and directed to remove object from Classic View in the meantime. Thanks for the resolution! |
|
I ran into something that appears to be related this issue on a WordPress.com site. A prior report noted the |
To be clear, as is reported elsewhere, by removing those spaces you're (I'm 99% certain of this) actually removing the offending Object Replacement Character, it's just not rendering the "OBJ" in that view (for whatever reason), so it's not visible. |
|
I had a user case with the same issue. |
|
Another report from a WordPress.com site on a Premium plan. The OBJ character was probably pasted in from another editor (it occurred just after a ® character). "Quick Edit" workaround worked like a charm! |
|
I had a user on a Premium plan who had a similar case. I went to do a |
|
I just took a report from a WordPress.com business user on this issue using 11.8.0, and this issue still persists. In this iteration of the issue, the OBJ didn't necessarily appear in the editor (there was nothing extra, like empty space as in above comments), but did appear in previews/on public pages. There was no Gutenberg crash, but otherwise it appears to be similar to this WordPress.org report. Strangely, if you re-save the post in the Gutenberg editor, sometimes the issue is filtered out. Otherwise, quick/classic edit to fix is still the workaround. |
|
I encountered this on a Russian site. I copy and pasted into plain text editor, deleted the original title, and pasted it back. This was originally copied from Microsoft Word as well. |
and others
Description
I am able to create a new post with a post title containing the OBJ character, after saving or publishing it and exiting the editor, the editor crashes when trying to re-open the post for editing. I was unable to replicate the issue using Gutenberg 11.3.0
Sample post title: "This post title crashes Gutenberg
"Step-by-step reproduction instructions
Screenshots, screen recording, code snippet
Error text from Gutenberg
Environment info
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes
The text was updated successfully, but these errors were encountered: