-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unknown DB column error received #2
Comments
confirmed again via WP_CLI
|
deactivating and activating plugin from this state results in
looks like needing more robust checking/migrating of DB state. my preference would be to look for all fields/seed data we require, if doesn't exist, blow all away and recreate as if new installation. worst case then, should be that we lose caching benefits for a run immediately after a breaking schema change in an addon like this. @john-shaffer what little MySQL knowledge I may have had seems to have disappeared - any thoughts on fixing this? Was this the already similar fix in WP2Static core that I should be able to copy paste into this? |
State: had deactivated/deleted WP2Static core a few times after activating the crawl addon. Didn't do an export initially to confirm if this error is present then, too.
To investigate
The text was updated successfully, but these errors were encountered: