You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In file plugins/payplug/src/Model/Lock.php method create_lock_table verifies whether the lock table has the id column with:
$result = $wpdb->get_row(
$wpdb->prepare(
"SELECT count(column_name) as column_exists FROM INFORMATION_SCHEMA.COLUMNS WHERE table_name = '{$wpdb->base_prefix}woocommerce_payplug_lock' AND column_name = %s ", ['id']
)
);
Unfortunately that request totally ignore the database that is containing the table. So if you have two copies of one site (say, production and staging) running on the same database server, with the same tablename prefix (say, staging is a direct duplicate of production), only one of the two site will receive the upgrade -- the other will not.
Expected: both sites receive the upgrade.
Suggested fix: add a WHERE table_schema = '{$wpdb->dbname}' to filter results for the current database only.
The text was updated successfully, but these errors were encountered:
In file
plugins/payplug/src/Model/Lock.php
methodcreate_lock_table
verifies whether the lock table has theid
column with:Unfortunately that request totally ignore the database that is containing the table. So if you have two copies of one site (say, production and staging) running on the same database server, with the same tablename prefix (say, staging is a direct duplicate of production), only one of the two site will receive the upgrade -- the other will not.
Expected: both sites receive the upgrade.
Suggested fix: add a
WHERE table_schema = '{$wpdb->dbname}'
to filter results for the current database only.The text was updated successfully, but these errors were encountered: