Version 1.12.5 splits layouts. The width of the columns is no longer editable.

  • Resolved solaris04

    (@solaris04)


    2 months, 2 weeks ago

    After the update from 1.12.4 to 1.12.5, rows are displayed as invalid in the block editor!
    “Block contains unexpected or invalid content.”
    After clicking on the “Attempt recovery” button, the row is edited again, but it is also displayed incorrectly or differently.
    Here, for example, an “Overall Color” has been added (this can be edited as usual).
    Another error is more intolerable…
    The Background (AWB) line contained an image that should be displayed over the full page width. Columns were displayed with a fixed width (i.e. with a gap to the left and right). This no longer seems to work.
    The page width of the columns can still be edited in the backend editor, but in the browser the columns are processed in full width.

    • This topic was modified 2 months, 2 weeks ago by solaris04.
Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Nikita

    (@nko)

    Hi,

    Thank you for your report. We made changes to some block attributes defaults, but they caused more problems than improvements. We have reverted these changes in version 1.12.6.

    Regards,
    Nikita.

    Thread Starter solaris04

    (@solaris04)

    Thank you Nikita,
    but the problems I mentioned are all still there.

    best regards

    Thread Starter solaris04

    (@solaris04)

    After re-examination, slight correction:
    The Advanced Backgrounds row / block is no longer displayed as incorrect “Block contains unexpected or invalid content.”
    The display of the block width in the backend editor still does not correspond to that in the browser (frontend).
    At least not if several “Background (AWB) rows follow each other.

    Thread Starter solaris04

    (@solaris04)

    With the update 1.12.7 the inner blocks are displayed correctly again.
    Settings / Layout / Inner blocks use content width
    I had to turn the switch on and off and save it. After that, the display in the backend and in the browser matched again.

    Thank you very much

    Alison

    (@anonymical7)

    I rolled back to ?1.12.4 for now and it displays correctly. 1.12.7 had the same issue, at least on my installation.

    ps:Thanks for the great plug-in by the way, it’s been a super addition.

    I also thank you for this great plugin but I have now the same problem after update to 1.12.7. Also had to install a rollback plugin and roll back to 1.12.4 until it worked again.

    Why is it remarked as resolved? It was really a great plugin until the latest updates. With the latest updates, my websites look aweful.

    I hope you can fix that soon. I first used WordPress 6.6.2 with Twenty-Twenty-Three theme, updated to AWB 1.12.7, block problem appeared. Then I rolled back to AWB 1.12.4, updated to wordpress 6.7.1 and then updated to AWB 1.12.7 again – still the same problem. So it seems independent from the WP version.

    Plugin Author Nikita

    (@nko)

    @wpzugang Hi. this is how it works for me → https://shot.nkdev.info/L09bp34v3Rdv4XdHWpKq

    Hi @nko what have you changed to make it work again? When I activate “inner blocks use content width” my header gets sequeezed and does not fill the full width anymore. So I have to keep that deactivated.

Viewing 8 replies - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.