Opened 15 months ago
Closed 15 months ago
#60604 closed defect (bug) (worksforme)
The word Rolex causes publishing to fail
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 6.4.3 |
Component: | General | Keywords: | close |
Focuses: | Cc: |
Description
If you create or modify a post on WordPress, and the post includes the word "Rolex" anywhere - in the heading, body, image caption etc., you will get an error when you try to publish.
Error has been replicated on 6 different WordPress installations, including with all plugins disables and default theme.
Change History (5)
#2
in reply to:
↑ 1
@
15 months ago
Replying to swissspidy:
I can not reproduce this.
This sounds like you have some antivirus software, web application firewall, or browser extension interfering with WordPress.
Thanks for your message, strange you can't replicate it.
If I disable Gutenberg, I can save a post with the word Rolex. Which suggests it is not antivirus software, firewall or browser extension, as enabling/disabling Gutenberg should have no effect if one of them was the cause.
#3
follow-up:
↓ 4
@
15 months ago
enabling/disabling Gutenberg should have no effect if one of them was the cause.
Not necessarily, it could have an effect. Also, in your original report you mentioned this happens even with all plugins disabled.
Does this issue also happen for example on https://playground.wordpress.net/?
#4
in reply to:
↑ 3
@
15 months ago
Replying to swissspidy:
enabling/disabling Gutenberg should have no effect if one of them was the cause.
Not necessarily, it could have an effect. Also, in your original report you mentioned this happens even with all plugins disabled.
Does this issue also happen for example on https://playground.wordpress.net/?
It does not happen on https://playground.wordpress.net/
Others have replicated it, but on the same server I use. What on the server could cause this? Particularly when it only happens on Gutenberg editor not classic?
#5
@
15 months ago
- Milestone Awaiting Review deleted
- Resolution set to worksforme
- Status changed from new to closed
What on the server could cause this? Particularly when it only happens on Gutenberg editor not classic?
This definitely sounds like a server-specific issue then. This may very well be a web application firewall (WAF) causing the issue. The block editor (Gutenberg) uses the REST API for saving posts, whereas the classic editor doesn't. Many WAFs have stricter rules for REST API usage.
I recommend reaching out to your hosting provider about this issue. For now I'm closing this ticket.
I can not reproduce this.
This sounds like you have some antivirus software, web application firewall, or browser extension interfering with WordPress.