• Resolved cutu234

    (@cutu234)


    Yet again we see problems with the BackWPup notification box that can’t be dismissed. I must admit, it’s getting on my nerves. It is reappearing again and again. This time it’s the “Welcome to BackWPup 5.0!” message.

    Guys, what’s wrong? I maintain hundreds of sites. So, I have some experience with this stuff. BackWPup is the one and only plugin that causes this issue. It’s not a big deal, but please give us a robust solution to fix it.

    Thank you very much for listening!

Viewing 8 replies - 1 through 8 (of 8 total)
  • Hello @cutu234, Sorry for your trouble. The welcome in-app notice should be dismissible and, once dismissed, shouldn’t be shown again. Can you help me identify the issue? Let me know if the message is shown for any specific type of user roles (admin, editor or all), disabling and then re-enabling the plugin still not fixing it or not?

    Thread Starter cutu234

    (@cutu234)

    I can see the message logged in as an admin, but not as an editor. Theme, WP and all plugins are the latest version. The site is running on PHP 8.3. Deactivating and Re-activating the plugin did not change anything. No caching enabled.

    Thank you.

    I also tried to recreate the issue but it’s working fine on my end. Even tested on new fresh install. The issue not there. Can you please check if you see any error message on the console log? See this guide on how to check for console log message

    Thread Starter cutu234

    (@cutu234)

    Yes, I know. I don’t see this issue on just a few customer sites. But if it appears, it’s ALWAYS the BackWPup box. I’ve alread checked the JS console. There are no errors.

    In the past, I had change the database directly. That’s no problem for me. However, something IS wrong, since errors like this appear again and again. I couldn’t find any patterns yet.

    Unfortunately, I couldn’t find any way to reproduce the issue on my end. Let me know if there’s a way to reproduce it and we’ll fix it in the next version.

    Moderator Support Moderator

    (@moderator)

    @cutu234 You other support topic was archived because it was not a support topic. You were not looking for help, that was a blog post.

    If you need support then raise a support topic.

    If you want to help others, reply to their support topics.

    If you want to post articles or blog posts, do not do that on this site. That’s not what these support forums are for.

    Thread Starter cutu234

    (@cutu234)

    If you want to post articles or blog posts, do not do that on this site. That’s not what these support forums are for.

    Sorry, I can’t follow. I am clearly looking for help. My other post contained a link to a similar support thread that could have helped here.

    It is a very strange policy that even I can’t see the “archived” post anymore. So, I am not able to answer properly.

    Back to the issue: In the other post (that was “archived”) was a solution for a similar problem. I had to create a value manually in the options table. Perhaps, there is a similar solution in this case. I would assume that dismissing the box normally creates this database entry to prevent the box from re-appearing again.

    • This reply was modified 1 year, 3 months ago by cutu234.
    Thread Starter cutu234

    (@cutu234)

    OK, I fixed it myself. This was probably one of the worst support experiences ever. There is obviously some bug that prevents the plugin from creating the proper entries in the options table. This meta_key was missing:

    backwpup_dinotopt_new_ui_notice

    I had to create it manually and set it to 1.

    It’s not a super big deal for me, but most users couldn’t do that.

    I wouldn’t complain, if this was the first time. But it happens again and again. I would happily assist you troubleshooting it. But it’s not quite appropriate to let users fix the problem.

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘Yet another notification-box problem’ is closed to new replies.