• Resolved spherical

    (@spherical)


    Just updated to 1.8.2 and there is a nag at the top of the screen:

    Ultimate Addons for Gutenberg requires Block Editor. You can change your editor settings to Block Editor from here. Plugin is currently NOT RUNNING.

    During this period of transition between Classic and Block Editors, which may or may not end, we ARE using the Block Editor and have the ability to switch between the two. At this point, the setting is to use Classic Editor as default for those a bit less adventuresome, but they can switch if they like, due to the Classic-Editor plugin.

    Never was an issue that we found in versions prior to 1.8.2. Changing the setting in Writing makes it go away, but it doesn’t stick. Changing the editor back to Classic Editor brings the nag back. If it were a latch operation to dismiss the nag, that would be OK, but it isn’t.

    And, as I go through my day, it appears on every page in the Admin.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Vrunda

    (@vrundakansara-1)

    Hey,

    Thank you for reaching us out. Many times it happens so that users import our Ready to import sites and they have Classic Editor enabled. This forbids them to edit the imported designs.

    This notice helps them know what they are missing. Indeed we will make it dismissible.

    Thank you for bringing this to us. We appreciate it.

    Regards,
    Vrunda Kansara

    Thread Starter spherical

    (@spherical)

    Thank You! I understand that there was an underlying reason. It is good to not have a plugin running when not needed (does it self-enable when the Block Editor is switched to from Classic Editor and disable itself when switching back to Classic?) or, as you state, a theme import would certainly have problems.

    Plugin Author Vrunda

    (@vrundakansara-1)

    Hey,

    The import works smoothly even when the Classic Editor is on. It just adds confusion to the user when they can not edit the imported site due to the wrong editor installed. That is why we give the notice as a heads up to what is actually happening.

    Well, the plugin starts running by itself as and when the Block editor is on, one needs not to do anything else. Also, you can see the changes in front end even when the Classic editor is on.

    UAG keeps the changes made intact. So, one can shift to Classic Editor when done with UAG editing and see the changes as they were without hurdles.

    I hope this clarifies your doubt.

    Regards,
    Vrunda Kansara

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Why is there a new nag?’ is closed to new replies.