• Resolved alx359

    (@alx359)


    I’m seeing this mismatch for years.

    In Database > Tables:

    wp_dppp_plugin_deactivation_rules table is said to belong to wp-fix-it-co-browse – an old and closed plugin since 2022. The table actually belongs to Deactivate Plugins per Page, which I own.

    Are there guidelines of how to avoid such mismatches, from a dev point of view?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support wpmansour

    (@wpmansour)

    Hi @alx359 ,

    Thanks for bringing this to our attention. We use an API to retrieve table names and their usage, but since your plugin isn’t hosted on wp.org, it isn’t automatically included in the data. I’m not entirely sure why the table is being attributed to the wp-fix-it-co-browse plugin, especially since it’s no longer active and we can’t test it.

    That said, if you’re open to it, you can provide us access to your plugin, and we’ll investigate further to resolve this.

    Let me know how you’d like to proceed!

    Thread Starter alx359

    (@alx359)

    Hi @wpmansour,

    Thanks, I’ll contact the author (I’m a license owner only) and refer him of this post.

    Hello.

    I am the plugin author of Deactivate Plugins Per Page. I see that your file with table names here says that the table dppp_plugin_deactivation_rules belongs to the plugin wp-fix-it-co-browse. If you have somehow detected this table in the wp-fix-it-co-browse plugin in the past and stored this, it means that they have copied code from my plugin and didn’t even change the names. Which makes sense, since I read that they had similar features for plugin deactivations like my plugin.

    Anyway, seems to me you just need to update your json file and remove that table from there, so your plugin shows that table as unknown and not used by any free plugin. Otherwise there is a risk that my clients delete all my plugin data with your plugin. Another person has reported this here too: https://www.ads-software.com/support/topic/wp_dppp_plugin_deactivation_rules/

    Regards.

    Plugin Support wpmansour

    (@wpmansour)

    Hi @alx359 and @nnikolov,

    Thanks for the additional details. I’ve brought this issue to the attention of our development team, and we are considering it for future updates.

    We appreciate your understanding and patience!

    Best regards,

    Thanks

    Plugin Support wpmansour

    (@wpmansour)

    You’re welcome : )

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.