{"id":32043,"date":"2025-01-29T18:10:34","date_gmt":"2025-01-29T17:10:34","guid":{"rendered":"https:\/\/mainetcare.de\/?p=32043"},"modified":"2025-02-25T14:52:26","modified_gmt":"2025-02-25T13:52:26","slug":"how-do-i-fix-the-error-in-the-gutenberg-editor-update-failed-or-publish-failed","status":"publish","type":"post","link":"https:\/\/mainetcare.de\/en\/wie-behebe-ich-den-fehler-im-gutenberg-editor-aktualisierung-fehlgeschlagen-bzw-veroeffentlichung-fehlgeschlagen\/","title":{"rendered":"How do I fix the error in the Gutenberg editor \"Update failed\" or \"Publishing failed\"?"},"content":{"rendered":"

If you receive the error message \"Update failed\" or \"Publish failed\" when saving or publishing a post in the WordPress Gutenberg editor and your text contains special characters such as emoticons, this could be due to an incorrect database configuration \ud83d\ude40! <\/p>\n\n\n\n

In this article, I will show you step by step how to fix the problem.<\/p>\n\n\n\n

Cause of the problem: Is the character set correct?<\/h2>\n\n\n\n

The character set utf8mb3<\/code> (or also utf8<\/code> ) only supports characters with up to three bytes<\/strong>. However, emojis and many special characters require four bytes<\/strong>. If your WordPress database is still on utf8mb3<\/code> is set, saving an emoticon will result in an error message.<\/p>\n\n\n\n

Solution: Conversion of the database to utf8mb4<\/h2>\n\n\n\n

Step 1: Backup!!!! <\/h3>\n\n\n\n

As always, before operating on database structures, create a complete backup of your database. We assume that you have access to the \"PHPMyAdmin\" tool.<\/p>\n\n\n\n

    \n
  1. Log in to phpMyAdmin.<\/li>\n\n\n\n
  2. Select the affected database.<\/li>\n\n\n\n
  3. Click above on \"Export\"<\/strong>.<\/li>\n\n\n\n
  4. Select the \"Quick\" option and click on \"OK\"<\/strong>to download the SQL file.<\/li>\n<\/ol>\n\n\n\n

    Step 2: Check the character set of the database<\/h3>\n\n\n\n
      \n
    1. Open phpMyAdmin and select your WordPress database.<\/li>\n\n\n\n
    2. Go to the tab \"Operations\"<\/strong>.<\/li>\n\n\n\n
    3. Check under \"Collation\"<\/strong>whether the character set utf8mb3_general_ci<\/code> or another obsolete character set is used.<\/li>\n<\/ol>\n\n\n\n
      \"\"
      This database still has the old character set<\/figcaption><\/figure>\n\n\n\n

      Step 3: Change character set<\/h3>\n\n\n\n

      Change database character set<\/strong><\/h4>\n\n\n\n
        \n
      1. Select the tab \"Operations\"<\/strong> the new character set utf8mb4_unicode_ci<\/code> from.<\/li>\n\n\n\n
      2. Activate the option \"Change collation for all tables\"<\/strong> and click on \"OK\"<\/strong>.<\/li>\n<\/ol>\n\n\n\n
        \"\"
        Check the \"Change all table collations\" and \"Change all column collations\" boxes<\/figcaption><\/figure>\n\n\n\n

        If not all tables or columns have been automatically adapted to the new character set<\/h3>\n\n\n\n
          \n
        1. Go back to the overview of your tables.<\/li>\n\n\n\n
        2. Click on a table (e.g. wp_posts<\/code>) and open the tab \"Operations\"<\/strong>.<\/li>\n\n\n\n
        3. Change the character set to utf8mb4_unicode_ci<\/code>.<\/li>\n\n\n\n
        4. Repeat this step for all relevant tables (e.g. wp_comments<\/code>, wp_options<\/code>).<\/li>\n<\/ol>\n\n\n\n

          Sometimes individual columns need to be adjusted:<\/p>\n\n\n\n

            \n
          1. Open the table and go to the tab \"Structure\"<\/strong>.<\/li>\n\n\n\n
          2. Edit columns with text content (e.g. post_content<\/code>, post_title<\/code>) and change their collation to utf8mb4_unicode_ci<\/code>.<\/li>\n<\/ol>\n\n\n\n

            Step 4: Customize the WordPress configuration<\/h3>\n\n\n\n

            Make sure that your file wp-config.php<\/code> specifies the correct character set:<\/p>\n\n\n\n

              \n
            1. Open the file wp-config.php<\/code> in the root directory of your WordPress installation.<\/li>\n\n\n\n
            2. Search for or complete the following lines:<\/li>\n<\/ol>\n\n\n
                 define(DB_CHARSET'<\/span>, 'utf8mb4'<\/span>);\n   define(DB_COLLATE'<\/span>, 'utf8mb4_unicode_ci'<\/span>);<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                \n
              1. Save and upload the file again.<\/li>\n<\/ol>\n\n\n\n
                5. reminder: clear cache \/ reload editor<\/h3>\n\n\n\n
                Clear the cache of your website (if available) and the browser cache to ensure that the changes take effect.<\/p>\n\n\n\n
                If your Gutenberg editor is still open, reload the article using the \"Refresh\" function of your web browser<\/p>\n\n\n\n
                Check whether the problem has been resolved<\/h2>\n\n\n\n
                Now try again to save or publish a post with emojis or special characters:<\/p>\n\n\n\n
                  \n
                • Open the Gutenberg editor and insert an emoji into a paragraph.<\/li>\n\n\n\n
                • Save or publish the post.<\/li>\n<\/ul>\n\n\n\n
                  If everything has been done correctly, the problem should be solved.<\/p>\n\n\n\n
                  Conclusion<\/strong><\/h2>\n\n\n\n
                  The error message \"Update failed\" in the Gutenberg editor can be caused by an outdated database configuration, in particular the character set utf8mb3<\/code>. With the changeover to utf8mb4<\/code> not only ensure that emojis are supported, but also make your website future-proof.<\/p>\n\n\n\n
                  \ud83e\udd16<\/p>\n\n\n\n
                  And if all this is too much effort for you, then simply call a website gardener \ud83d\udc69\u200d\ud83c\udf3e<\/p>","protected":false},"excerpt":{"rendered":"
                  If you receive the error message \"Update failed\" or \"Publish failed\" when saving a post in the WordPress Gutenberg editor, this could be due to an incorrect database configuration. The solution is as follows...<\/p>","protected":false},"author":1,"featured_media":32046,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[22],"tags":[],"techdoc_tag":[],"class_list":["post-32043","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-website-pflege"],"acf":[],"_links":{"self":[{"href":"https:\/\/mainetcare.de\/en\/wp-json\/wp\/v2\/posts\/32043","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mainetcare.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mainetcare.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mainetcare.de\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mainetcare.de\/en\/wp-json\/wp\/v2\/comments?post=32043"}],"version-history":[{"count":2,"href":"https:\/\/mainetcare.de\/en\/wp-json\/wp\/v2\/posts\/32043\/revisions"}],"predecessor-version":[{"id":32173,"href":"https:\/\/mainetcare.de\/en\/wp-json\/wp\/v2\/posts\/32043\/revisions\/32173"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/mainetcare.de\/en\/wp-json\/wp\/v2\/media\/32046"}],"wp:attachment":[{"href":"https:\/\/mainetcare.de\/en\/wp-json\/wp\/v2\/media?parent=32043"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mainetcare.de\/en\/wp-json\/wp\/v2\/categories?post=32043"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mainetcare.de\/en\/wp-json\/wp\/v2\/tags?post=32043"},{"taxonomy":"techdoc_tag","embeddable":true,"href":"https:\/\/mainetcare.de\/en\/wp-json\/wp\/v2\/techdoc_tag?post=32043"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}