stuck at 35% – database upgrade or not working at all after update

  • Resolved lekkerbezig

    (@lekkerbezig)


    7 months, 3 weeks ago

    Hi Burst,

    I’ve got two errors after updating your plugin on multiple websites.

    One website:

    “An upgrade is running in the background, and is currently at 35%. For large databases this process may take a while. Your data will be tracked as usual.”

    This status keeps popping up, 12 hours after the update.

    Three websites:

    “Door de configuratie van je server of site is het niet mogelijk statistieken bij te houden.”

    The help link leads to a 404 page on your website and the burst plugin worked with previous versions.

    What should I do to fix this or do I have to wait for the next update?

    kind regards

Viewing 12 replies - 16 through 27 (of 27 total)

  • Hi @rogierlankhorst,
    in the php.log file:

    [04-Aug-2024 11:00:55 UTC] PHP Warning: foreach() argument must be of type array|object, string given in /home/html/ah-modely.cz/public_html/pribrat.cz/www/wp-content/plugins/burst-statistics/settings/settings.php on line 1374

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    @nachtwaechter great to hear! Not sure how it’s possible that the upgrade didn’t start, but we can create a check for this.

    As for the php warning: it’s just a warning, so you can ignore it, but we’ll fix it in the next release.

    great to hear! Not sure how it’s possible that the upgrade didn’t start, but we can create a check for this.

    Thank you for the quick and dirty solution, which worked great on another site too. ??

    As for the php warning: it’s just a warning, so you can ignore it, but we’ll fix it in the next release.

    That’s what I expected.

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    @hamil1 @lekkerbezig Based on @nachtwaechter ‘s logs I have created a version which checks if the database upgrade has actually started, and restarts the upgrade if not.

    https://github.com/Burst-Statistics/burst/tree/re-check-interval

    It also includes a fix for the PHP warning.

    Let me know if this works for you.

    I have tried version 1.7.1 on one site so far. The database update has been done. It took units of minutes.
    I don’t see PHP warnings yet. I will double check it later.
    Thank you.

    Thread Starter lekkerbezig

    (@lekkerbezig)

    Hello @rogierlankhorst

    I can confirm this quick update fixed the “server was not configured correctly” notice on the dashboard.
    Thank you and @hesseldejong for the quick response

    Kind regards

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    Glad to hear! Thanks for the confirmation.

    Hello,
    even after 2 days the update process is at 65%. If I update the view, it always changes between 50 and 65%.

    Since today there is a new red X at the bottom right with the error message “Tracking does not seem to work. Please check yourself or contact support. Last checked for 55 YEARS”.

    Plugin Author Hessel de Jong

    (@hesseldejong)

    Hi @zwtros,

    Could you try our latest release and see if this solves your issue?

    Kind regards,
    Hessel

    Hi @hesseldejong,

    problem solved. Thank you.

    Hi @hesseldejong
    First of all, thanks for the update.

    • The problem with the dashboard has been fixed. It works again.
    • However, I still have the problem that the update process jumps back and forth between 50% and 65%, as if it were trapped in a continuous loop.
    • The display in the Statistik Dashboard at the bottom right is now green again and a tick shows that everything is working

    Perhaps it should also be mentioned that I have a small blog with only 39 posts.
    The database should therefore not be large.

    • This reply was modified 7 months, 2 weeks ago by zwtros.
    Plugin Author Hessel de Jong

    (@hesseldejong)

    Hi @zwtros,

    Could you maybe send an email to support[at]burst-statistics.com? If you could attach any information that is in the debug.log that would be great!

    Kind regards,
    Hessel

Viewing 12 replies - 16 through 27 (of 27 total)
  • The topic ‘stuck at 35% – database upgrade or not working at all after update’ is closed to new replies.