v6 database upgrade inconsistent

  • gerarde

    (@gerarde)


    6 hours, 41 minutes ago

    I’ve upgraded two slimstat installs on the same mysql/machine and (weirdly) the smaller DB did not complete all the database upgrade steps. Many tables are either not created or not upgraded. Plus despite the following error message telling me the DB does not match the manifest, there migrate option is not offered as an option any more.

    the error message says:

    SlimStat reported a problem while running.
    Tracking and reports kept working. These are maintenance tasks that did not complete, so some data may be missing or a column may be absent. Reinstalling the plugin does not clear these; check SlimStat > Migrations and Settings > Maintenance.

    • Database columns differ from this version
      these columns differ from the manifest: slim_stats.email (255, declared 256), slim_stats_archive.dt_out (absent), slim_stats_archive.email (255, declared 256), slim_stats_archive.fingerprint (255, dec
    • This topic was modified 6 hours, 41 minutes ago by gerarde.
    • This topic was modified 6 hours, 41 minutes ago by gerarde.
Viewing 1 replies (of 1 total)
  • Plugin Contributor Parhum Khoshbakht

    (@parhumm)

    1 hour, 38 minutes ago

    Hi @gerarde ,

    Thanks for the detailed report, and for pasting the exact message. It made this quick to track down.

    You’re right: the warning sends you to SlimStat > Migration, but that page has nothing to run, so the warning never clears. That’s a bug on our side. Sites first set up with a SlimStat version older than 4.8.2 keep a few columns from that era (255 characters wide instead of 256, and an archive table without some columns added later, such as exit time). SlimStat 6 detects them but doesn’t offer a step to repair them yet. That’s also why your two sites differ: it comes down to when each one was first installed, not database size.

    We’ve confirmed the bug and are working on it, and we’ll deliver a fix soon. You can follow its progress on GitHub:
    https://github.com/wp-slimstat/wp-slimstat/issues/360

    The good news is that there’s nothing risky for your site. Your site and visitors aren’t affected, and there’s no need to reinstall SlimStat or change anything in the database. Tracking and reports keep working, and the one-character difference has no practical effect. The only gap is in the archive: pageviews moved there don’t keep a few older fields, such as their exit time. The tables you saw missing are expected too: the heatmap tables are created when you turn on heatmap recording, and the WooCommerce table when you set up the WooCommerce revenue dashboard.

    Your message was cut off at the end, so if the warning lists anything beyond these columns, or shows a second item, please paste the full text here and we’ll confirm it’s covered.

    Thanks again for helping us make SlimStat better.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.