Disables standard Gutenberg blocks

  • Resolved eelcobruinsma

    (@eelcobruinsma)


    6 years, 8 months ago

    Hi there, I was forced to deactivate and remove Advanced Gutenberg from 4 sites, because it somehow made all other block types, like the standard Gutenberg blocks, disappear from the interface. Which means that the box that normally opens when you start to define a new block ONLY showed the AG blocks, and some blocks from other plugins, but all default Gutenberg blocks were invisible, or just not there. Disabling the AG plugin and reloading the page which was being edited, made all the other options available again. The theme was OceanWP, all plugins, Gutenberg included, were up to date.

Viewing 5 replies - 1 through 5 (of 5 total)
  • JoomUnited

    (@joomunited)

    6 years, 8 months ago

    Hi,

    Thanks for the feedback.
    Would you tell me the update process you followed, maybe 1.6.5 -> 1.6.7 -> 1.7.0 or 1.6.5 -> 1.7.0
    Also did you change any Advanced Gutenberg profile or didn’t you use it at all?

    Cheers

    Thread Starter eelcobruinsma

    (@eelcobruinsma)

    6 years, 8 months ago

    Hi there,

    I used the first update process. Your question about the profile put me on the right track. In 4 out of 5 sites on which I had installed AG, there was a profile that had disables all but a few blocks. These profiles remained in the database even after removing the plugin and became active again after I tested a new installation. This is how I discovered that AG caused the blocks to disappear.

    I forgot all about the existence of these profiles. So I am now in the process of re-installing AG on the remaining sites. I will immediately change the profiles associated with it.

    The remaining mystery is, how these 4 profiles got configured to disable all but a few blocks in the first place. I never consciously disabled 95% of all blocks on multiple sites. And why not on the one remaining site? Since these are all sites for which I am the only editor, there is no one else to blame.

    But all’s well that ends well, it was not a technical issue, and I now know that it is prudent to check the profiles from time to time, because some goblin must be intervening.

    Anyway, I’m happy to be able to use AG again. Thanks for your quick response, which enabled me to solve the issue.

    JoomUnited

    (@joomunited)

    6 years, 8 months ago

    Hi,

    Thanks for your feedback, there was indeed a conflict on our side with a specific version of AG with a specific version of Gutenberg or maybe “because some goblin must be intervening” is another option 🙂

    Anyway, if you like the plugin it would be cool to drop us a review, it really helps us especially our support team here.
    https://wordpress.org/support/plugin/advanced-gutenberg/reviews/?filter=5

    Thanks a lot!

    Cheers,

    Thread Starter eelcobruinsma

    (@eelcobruinsma)

    6 years, 8 months ago

    Hi there,

    Glad that has been cleared up.

    Later today, when I have a bit more time, I will write a review.

    Thanks.

    flexinoodle

    (@flexinoodle)

    6 years, 8 months ago

    Erm no, this isnt fixed, it disables guttenberg blocks entirely here, who actually tests these releases, this happens all the time with this plugin !!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Disables standard Gutenberg blocks’ is closed to new replies.