-
Notifications
You must be signed in to change notification settings - Fork 11
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
Error on migration: Columns missing or Same version #16
Comments
This is because the Matomo for WordPress plugin does not have the plugin CustomVariables enabled. You would basically need to add these columns manually to your WordPress installation like
Same would probably need to be done for Then similar likely also for the other tables
and
|
I have a similar problem, documented here: https://forum.matomo.org/t/matomo-migration-error-the-following-columns-are-missing-in-the-target-db-table/42184/ I don't necessarily want those (empty?) columns in there if they're not needed/deprecated. Is there a way to skip those columns when migrating? Also, it might be helpful to add a hint to users in the instructions at https://plugins.matomo.org/Migration that if they get a |
I've hit very similar problem, migration plugin complains that some columns missing. It took me a while to realize that this is caused by the different plugins installed. So the message:
is a bit confusing, because to have the same version of Matomo is not enough. You must have also the same version of plugins (at least those that change the database schema). And even if I have the same plugins I can't reach the same schema, maybe because there were some historical version of one of the plugins, but I'm not sure right now. It would be very very helpful to change the exception message to something that notice users to check out the plugins too. This tiny upgrade might help a lot. |
Hello,
I'm trying to migrate data from a Matomo for WordPress instance to Matomo On-Premise. When running the command, I get this error:
Do you know what the issue could be?
Thank you for your help,
François
The text was updated successfully, but these errors were encountered: