Make WordPress Core

Opened 14 months ago

Closed 14 months ago

Last modified 13 months ago

#60156 closed defect (bug) (invalid)

Unable to save post that contains shrug icon

Reported by: mshekow's profile mshekow Owned by:
Milestone: Priority: normal
Severity: normal Version: 6.4.2
Component: Database Keywords:
Focuses: Cc:

Description

If the text of a post contains 🤷 (that icon), I get back the following response:

HTTP status code: 500
HTTP Body:

{
    "code": "db_update_error",
    "message": "Could not update post in the database.",
    "data": {
        "status": 500
    },
    "additional_data": [
        "WordPress database error: Processing the value for the following field failed: post_content. The supplied value may be too long or contains invalid data."
    ]
}

I cannot imagine that this behavior is intentional.

Change History (2)

#1 @tobifjellner
14 months ago

  • Component changed from General to Database
  • Resolution set to invalid
  • Status changed from new to closed

Hi @mshekow
WordPress core Trac is one of the places where we follow up development of and bufs/fixes for WordPress core.
In this case, I'm not yet convinced that this is actually a problem in WordPress core. While troubleshooting, a better place to discuss would be our support forums, https://wordpress.org/support/forum/how-to-and-troubleshooting/

Anyway. Start by double-checking which character encoding your database uses for the table "wp_posts" (wp_ may be something else, depending on which prefix you chose when installing). Preferred encoding is utf8mb4 nowadays.
If you need to convert your database, then remember to first save a backup. Next keep in mind that conversion happens one database table at a time. (The general database settings for encoding and collation are only used as fallback values when NEW tables are created.)
You can search online for step-by-step instructions "Convert tables to utf8mb4 mariadb" or similar.

I'm going to close this ticket, since there's nothing yet that requires follow-up from WordPress core point of view. If you still find that there's an error in WordPress itself, then please add details for how to replicate this problem (preferably on a fresh WordPress install with no plugins) and re-open the ticket.

Last edited 14 months ago by tobifjellner (previous) (diff)

#2 @swissspidy
13 months ago

  • Milestone Awaiting Review deleted
Note: See TracTickets for help on using tickets.