Error Log after upgrade

  • Resolved wlpdrpat

    (@wlpdrpat)


    4 years, 5 months ago

    @johnny5

    Hi John,

    I recently upgraded WP and redirection on my multisite install. Following the upgrade I went to each blog where the plugin is activated and clicked the upgrade DB button and the new ajax load appeared on the page. Success!!

    However, since then I have been getting a ton of errors in my php error log that all look very similar:

    [07-Oct-2020 19:09:00 UTC] WordPress database error Field ‘module_id’ doesn’t have a default value for query INSERT INTO wp_20_redirection_logs (url, created, ip, agent, sent_to, redirection_id, group_id) VALUES (‘/feed/’, ‘2020-10-07 19:08:59’, ‘157.55.39.105’, ‘Mozilla/5.0 (compatible; bingbot/2.0; +https://www.bing.com/bingbot.htm)’, ‘/asthma/feed/’, ’63’, ‘1’) made by RE_Log::create

    I am OK with getting a few errors per day in my php log but in the last 8hrs since completing the upgrade I have logged over 30K lines of the above error over and over. The only thing that changes is the site number the URLs and who accessed it.

    Any thoughts on how to resolve this would be much appreciated.

    Pat

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author John Godley

    (@johnny5)

    Did you perform the Redirection upgrade? What version did you upgrade from? module_id has not been part of the plugin for a long time.

    Thread Starter wlpdrpat

    (@wlpdrpat)

    @johnny5

    Yes, it had been about a year since I updated. Guess I should have upgraded one version at a time. Is there a simple solution for this?

    I am very good at coding and decent with mysql. Is this simply a matter of deleting a specific table or is it more complex?

    Thanks,
    Pat

    Plugin Author John Godley

    (@johnny5)

    The plugin should handle upgrades going back many versions, and I don’t know why it would get into such a situation. If you go to the support page you can change the database back to a previous version and it will re-run the upgrade, and it might push things through. You could try going back one version, which I think is enough for the above error.

    Thread Starter wlpdrpat

    (@wlpdrpat)

    @johnny5

    I tried your suggestion. First, I changed the db version to 4.0 and ran the upgrade script on all sites where the plugin is active. Checked error log and issue persists. Then I changed db version to 2.4 and ran the upgrade script on all sites where the plugin is active and still the issue persists.

    Is is possible that I need to reinstall the plugin? Any other thoughts?

    Thanks,
    Pat

    Plugin Author John Godley

    (@johnny5)

    I’m not sure what is different about your site, and something is not working when the upgrade runs. Are there any errors in the log during the upgrade?

    You could try removing the module_id column from the table mentioned in the error. However, it’s possible that other upgrades may not have occurred.

    Reinstalling should also fix the problem. You can export your data (as JSON) before hand and then import back.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Error Log after upgrade’ is closed to new replies.