Throws error trying to add table prefix everytime

Same issue here from 3 months ago…

[09-Feb-2021 08:54:38 UTC] Error Table ‘wp_sib_model_contact’ already exists de la base de datos de WordPress para la consulta ALTER TABLE sib_model_contact RENAME TO wp_sib_model_contact; realizada por require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), include_once(‘/plugins/woocommerce-sendinblue-newsletter-subscription/woocommerce-sendinblue.php’), WC_Sendinblue_Integration->__construct, SIB_Model_Contact::add_prefix
[09-Feb-2021 08:54:38 UTC] Error Table ‘wp_sib_model_country’ already exists de la base de datos de WordPress para la consulta ALTER TABLE sib_model_country RENAME TO wp_sib_model_country; realizada por require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), include_once(‘/plugins/woocommerce-sendinblue-newsletter-subscription/woocommerce-sendinblue.php’), WC_Sendinblue_Integration->__construct, SIB_Model_Country::add_prefix

Hi,

For those who are facing this problem…

SendInBlue support will only ask you to delete and reinstall the module.
It won’t work and you will still have to reintegrate it with SiB.

The root cause for this issue is that some previous installation left a table name “sib_model_contact” there, while a new installation, created “wp_sib_model_contact”.
With that, the code will see this “sib_model_contact” table and will try to rename it to “wp_sib_model_contact”. Since this table already exists, it will throw an error.

In order to fix it, just remove the former table.
DROP TABLE sib_model_contact;

Just check if any data migration is needed first.

Hi there,

Thank you for bringing this up and we appreciate the alternative solution suggested by you. I am sure that this would definitely work and we have even asked our Development team to handle in near future.

I would further like to inform you that the above reported issue generally comes up when Old version of the plugin has not been disabled/uninstalled properly and in parallel the latest version of the API ( V3) is being used.

In the above cases , we recommend our clients to completely uninstall the older version and install the new one so as to avoid such situation.

I would like to thank again for analysing the root cause and suggesting the alternative ??

No worries!
Glad to help!

I really tried in different ways to completely uninstall the plugin, but I guess deleting the old table is not part of the removal routine.
That’t why I did that manually and it worked like a charm.

Thanks for your response and kindness.
You and the support team have been really solicitous anyway.
5 stars.

Hello @wilmerlm11

Glad to hear that :). We always try to help our customers in the best possible way. We again thank you in suggesting the alternate solution.

Have a good day!

Regards,