• Resolved Jonathon Harris

    (@demo38ltd)


    Hello, I was testing options with your plugin and am switching to a different plugin that integrates differently with my set up. After deleting the Group I had created, then disabling your plugin, then deleting your plugin, I’m still getting the add-on field created by your plugin on my shop for the products that I had tested with.

    I’m working on a local dev install, and switching to WooCommerce Product Add-ons.

    I’ve deleted cache, tried different browsers… How can I remove this that must have been added to the database?

    Thanks,
    Jonathon

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author bizswoop

    (@bizswoop)

    Jonathon,

    Thanks for reaching out to us.

    Right now, as you noticed, if you delete the plugin, this doesn’t delete the data from the database. This is the first request we received on the topic, we will look to add the functionality to drop the tables, if the plugin is deleted in a future release of the plugin.

    To solve the problem, yes, we’d recommend you drop the tables from your database to remove all data created by our Product Add-ons plugin. You will need to drop the entries including the za_ prefix, for the following entries za_add_ons, za_categories_to_groups, za_groups, za_products_to_groups, za_types and za_values from your database.

    Thread Starter Jonathon Harris

    (@demo38ltd)

    Hello, thanks for your help – I just dropped those “za_” tables from the database and cleared browser cache – however, that additional product add-on content is still showing on the front-end.

    It’s not appearing on products I hadn’t tested on, but it is still showing on the 2 products that I had tested it on.

    Where else would that be pulling from?

    Plugin Author bizswoop

    (@bizswoop)

    Very strange.

    This is the expected behavior based upon the action taken:

    Deleting the Plugin, the Product add-ons will be removed from the front-end

    Dropping the Plugin tables, za_ will remove all Product Add-ons plugin data

    No other data outside the tables in the DB is being called or pulled from.

    We just verified this behavior on 2 live servers, and 3 local servers. Unfortunately, we are unable to reproduce this behavior you reported.

    We are thinking a few items could be creating this behavior.

    1. Other Product Add-on type plugins installed during the testing period. Depending on the mix of testing you performed, this could have created an odd conflict. Potentially removing all Product Add-on type plugins and reset DB clean of Product Add-ons might resolve the issue and conflict created during testing.

    2. Server Cache services. You mentioned clearing browser cache, but are you using any cache plugins or server based cache like Jetpack, Cloudflare, Sucuri or etc. You would need to clear the cache from these server based services too.

    I hope that information is helpful. We’re happy to support additional troubleshooting if you can provide more details, like a link to the front-end to view the developer console to see which code is being called on the front-end.

    Thread Starter Jonathon Harris

    (@demo38ltd)

    Hello – I follow what you’re saying, but I only tested your plugin and then switched over to WooCommerce Product Add-ons. I’m not using a CDN at this point.

    I’m using Local by Flywheel, and I’ve restarted the local server…

    It’s a pretty basic setup – Storefront theme, Elementor Pro, WooCommerce, WooCommerce Product Add-ons.

    When I deactivate WooCommerce Product Add-ons, then it hides your plugins info, then when activating it again, it brings back your plugins info.

    I’ve even tried WooCommerce / Status / Tools and deleting transients.

    Not sure what’s going on with it at this point…

    Plugin Author bizswoop

    (@bizswoop)

    Yeah we agree. We are also a bit stumped on our side as well. Why the WooCommerce Product Add-ons data would be linked upon activation and deactivation is very odd…

    Unfortunately, we can’t reproduce the behavior and we don’t have the WooCommerce Product Add-ons plugin to try and test any conflicting behavior that may have occurred or is actively occurring. Plus we don’t have Local by Flywheel configuration to test on.

    One additional idea, you might also consider trying to regenerate the WooCommerce Product lookup tables.

    One question, on the front-end, what does developer console show for the meta data div classes?

    Have you also reached out to the WooCommerce support team as owners of the WooCommerce Product Add-ons plugin? They might have new insights we haven’t thought of yet.

    We will keep trying to reproduce and see if we can create this behavior and follow-up, but right now, we don’t have additional insights minus the lookup tables and the insight on the meta data div classes in the front-end developer console.

    If the issue is caused by our plugin, we will definitely push a fix, but right now, we aren’t able to identify or reproduce the behavior to take any action.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Can’t remove the plugin…’ is closed to new replies.