• Resolved gubbigubbi

    (@gubbigubbi)


    Great plugin! One little bug: After saving the header block the button text always seems to revert back to the letter ‘B’. I think this has to do with the way the attributes are setup and being parsed. If you can link me to the GH repo I can do a pull request to try to fix.

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Benjamin Intal

    (@bfintal)

    Hi there!

    I’ve encountered this before also but so far I can’t replicate the problem reliably. So far a quick fix is to re-create the block (not sure if duplicating it and deleting the old one works).

    If you have a way to replicate it, please let me know.

    Thread Starter gubbigubbi

    (@gubbigubbi)

    Sorry – no go with duplicating. Im not really sure how to replicate either. I also tried duplicating the page too. If it helps I have all of the button controls activated such as border radius, color, background color etc

    Plugin Author Benjamin Intal

    (@bfintal)

    Please try version 1.1. The hard part with a Gutenberg/beta plugin is that they change things so fast – apparently RichText.Content should be used for saving RichText fields, I’m hoping this would fix it since I haven’t encountered the problem yet.

    Thread Starter gubbigubbi

    (@gubbigubbi)

    Cheers – yep I tried the development version of the plugin and this problem is fixed – same with on the Card block. Thank you ??

    Plugin Author Benjamin Intal

    (@bfintal)

    That’s great!

    Don’t forget to leave a review ??

    Thread Starter gubbigubbi

    (@gubbigubbi)

    Hey there – sorry I can confirm the problem is still ocurring in the v1.1 release. It was ok when I tried the development branch of the plugin but the official v1.1 plugin still has the button text saving issue.

    Plugin Author Benjamin Intal

    (@bfintal)

    Hey! Sorry but right now I think this might be somehow related to some Gutenberg issue, although I’m not really sure. Reason being is that the way the button block works is almost identical to how the default button block works. Probably the best way to check if the bug also happens Gutenberg’s button block.

    Some of the saving methods for Gutenberg has recently been updated for a future version (v4.0), I’m hoping that this might get fixed by then.

    Plugin Author Benjamin Intal

    (@bfintal)

    With my development version for Stackable 1.3 and Gutenberg 4.0, I have encountered the problem but with no way to replicate it.

    I found a workaround though. Click on the block, then on the toolbar, click on the icon with the 3 dots to show more options. Choose “Edit as HTML”, then click on the 3 dots again then choose “Edit Visually”.

    I think somehow the saved state of the RickText component gets out of sync with its visual state. However, I still think that this is a Gutenberg issue, so I’m resolving this issue here since I have tried the workaround when I encountered the issue and it seemed to have resolved the problem

    I’m having to use your workaround. Every time I want to change the text on any button this happens. Sometimes the button will take my text other times I have to drop to HTML – Brilliant add on to Gutenberg but this issue is driving me nuts lol

    Using Gutenberg 4.11

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Header button text not saving – Gutenberg 3.9 / Stackable 1.0’ is closed to new replies.