wired issue with advanced tabs at backend

  • Hi,

    I am experiencing a wired issue with advanced tabs when editing, if I create a advanced tabs and then choose edit as html, first time I can switch back to block editor, but if I switch to html again then it won’t be able to switch back to block editor. It seems switch between block editor and html editor will mess up <!– wp:advgb/adv-tabs …–> makeup.
    And another question is, I have lots of pages with advanced tabs that created when I use 1.0 version of the plugin, is there a easy way to convert all of them to the updated code at once?
    Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter shichenglu

    (@shichenglu)

    by the way, I tried to manually convert 1 old tabs to new one, it works, however it will also generate a error notice “undefined index: pid”, not sure why this happens.

    Hi,

    I see the issue about the HTML invalid issue, it should comes since the latest update. We’ll investigate and fix that.

    Cheers,

    I’ve run some test and about the validation it seems it happens to all blocks since a recent Gutenberg update every time you edit a block using HTML, click in the HTML field and go back to the visual edition.

    We need to escalate that if no one has reported it because it seems général (not only in our plugin).

    Regarding the tab migration, there’s no way to do that, basically this is a totally a different block and every block needs to be checked. But since you don’t update the block, the HTML content should remains intact.

    Hope it helps a bit.

    Cheers,

    Hi,

    We just pushed an update of the plugin with several fix related to the tab block (and others). It also prepares the plugin for the new Gutenberg update to come.

    Please clear your cache and run some test if you can.

    Thanks a lot, cheers,

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘wired issue with advanced tabs at backend’ is closed to new replies.