WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #46309, comment 2


Ignore:
Timestamp:
02/22/2019 11:46:28 AM (2 years ago)
Author:
Blamedutchie
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #46309, comment 2

    initial v1  
    33After the update to WP5.1 I no longer see the JSON error, but updating posts that contain images or galleries still give the red **Updating failed** banner, while the post does get updated.
    44
    5 Interestingly, I am also using the Meow Gallery Block plug-in and whether I use the media gallery OR an upload to add a gallery, the click here to refresh the preview shows no gallery in the editor. When using the standard Gallery Block, this does not happen.
     5Interestingly, I am also using the Meow Gallery Block plug-in and whether I use the media gallery OR an upload to add a gallery, the **click here to refresh the preview** link shows no gallery in the editor. When using the standard Gallery Block, galleries show as expected.
    66
    77In both cases, although the red **Updating failed** banner shows, the post gets updated.
    88
    9 Cutting around corners: I wonder if we are looking at a JSON issue ''or'' a Gutenberg editor design flaw...
     9Cutting around corners: I wonder if we are looking at a JSON issue ''or'' a Gutenberg editor design flaw... Maybe connected to updating existing sites? Legacy php/html giving problems?
    1010
    1111To make things even more intriguing; I have copied my site in a VirtualBox / Turnkey appliance, using the same theme and the same plug-ins and never do I receive a JSON or Updating failed error, even though the Virtualbox (deliberately) allows for smaller uploads and has a lower memory limit. The Virtualbox has cUrl enabled, the live site hasn't, but as far as I know, that should not be an issue when editing posts - it never was...