Doesn’t use the specified WP database table prefix when it should

  • Resolved KZeni

    (@kzeni)


    5 years, 11 months ago

    Just wanted to let you know that the plugin is currently always using wp_ as the table prefix for the wp_ada_compliance table rather than using what’s specified in the wp-config.php file. This seems like an issue of the plugin complying with common & established WordPress plugin conventions (this one being a possible security concern, conflict if there’s multiple sites using this plugin in a single database, etc.), and hopefully it’ll be a quick & easy fix.

    I’d imagine this plugin should check to see if the wp_ada_compliance the table exists when wp-config.php has the prefix set to something else when upgrading from a previous version and rename it accordingly (taking care of existing installations), and then have it so all calls to the table always use the specified table prefix everywhere else in the code (simply just using the preferred setup from then on). I’m assuming this is also the case for the paid plugin as much as it is for the free version, currently.

    Thanks for the great plugin and support,
    Kurt

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author seshelby

    (@seshelby)

    Hello and thank you for continuing to report improvements to the plugin. This particular item has been addressed in the latest release of both versions. If you are using the latest release and are still seeing the table name without the prefix you will need to delete the plugin and do a clean install with the latest version.
    Thanks
    Sam

    Thread Starter KZeni

    (@kzeni)

    I see the database updated after upgrading to v2.2 of the paid plugin (which is what my site is running) so there aren’t any tables not using the specified table prefix in my database anymore.

    As an aside, it did take a while for the conversion to complete with >100,000,000 data length (>100,000 rows) for the existing wp_ada_compliance database table. Just mentioning just in case others experience extended periods where this saturates their database resources and/or terminates due to extended execution times. As an aside, it makes me wonder if the query that’s executed could be optimized (does it need to create the new table, insert the items from the old table into the new one, and then delete the old table when RENAME TABLE exists?)

    Thanks for the quick update!

    Plugin Author seshelby

    (@seshelby)

    New tables are created to account for network/multi-site installations.

    Thread Starter KZeni

    (@kzeni)

    That makes sense. So then sites that aren’t network/multi-site installs should be okay with a basic RENAME TABLE at that point? It really was troublesome for the site to do a cumbersome operation like that when it wasn’t a network/multi-site setup & therefore probably didn’t need to go about it that way.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Doesn’t use the specified WP database table prefix when it should’ is closed to new replies.