• Drumsk8

    (@drumsk8)


    So… I run a multipress web site and was looking at this plugin, which at one point looked like it was going to work and I was seriously impressed as my site is massive to say the least and no other plugin has come close to working. (It didn’t complete properly as I have mysql issues, I’ve manually resolved mysql and wish to attempt the ftp transfer again)

    However, I keep seeing version 2.0.1 within the plugin page not 2.1.3 as I would expect.

    Worse when ever I network deactivate and delete the plugin, it appears to have been removed, doens’t show in the admin dashboard or within wp-content/plugins folder either.

    That being said, whenever I re-install the plugin and click network activate it will automatically take me back to my main multipress site and with all the details filled out for that site. Also, showing 2.0.1 at the top!

    Clearly something is being cached somewhere and it’s NOT uninstalling correctly. I’ve tried re-installing 2.0.1 manually, however, the plugin is still broken.

    Please can you tell me were all the files this plugin creates are held so I can nuke the …. out of this dam thing, so that I can properly re-install and test it again.

    Not impressed that uninstall is clearly leaving files in the system that causes the plugin to break every time.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Drumsk8

    (@drumsk8)

    So I got bored and wanted to find where this information was being stored.

    First checked the database for pattern match of the target host db username I had set in the plugin, nothing was found.

    So then I decided to check all the files in wp-content and found a bunch. I used a command like this:

    grep -r -l “target_db_user” /home/domain/public_html/wp-content/cache/object/

    Outputs a list like this:

    /home/domain/public_html/wp-content/cache/object/1/c57/c1b/c57c1b30e7e434011bddae3c48ec0ffd.php
    /home/domain/public_html/wp-content/cache/object/1/62e/3e1/62e3e12cb2116ecb64d5fa09b2ece4a5.php
    /home/domain/public_html/wp-content/cache/object/1/99c/3d7/99c3d7f11981a3b45f3e1700fdda2a94.php
    /home/domain/public_html/wp-content/cache/object/1/046/6cf/0466cfc6407cfe7995699cdc8212b22f.php
    /home/domain/public_html/wp-content/cache/object/1/b5c/d47/b5cd477768d07ac7d15e3619bb02207b.php

    I found a number of php files spread around /wp-content/cache/objects/ so I tried to delete them like this:

    grep -r -l “target_db_user” /home/domain/public_html/wp-content/cache/object/ | xargs rm -f

    Even after deleting these files, it appears they are still being created randomly. So i’ve restarted apache and fpm-php services hoping to flush out any old php task that’s running rouge in the background. Still after running the delete command I get more files appear, this even with the plugin deactivated!

    I am reluctant to reboot the server as it’s a live system, so what could be automatically generating these files, is it a stuck process? as I don’t see anything sticking out with ps -aux

    Any thoughts?

    Thread Starter Drumsk8

    (@drumsk8)

    Purged all object caches in w3tc still files are being found that correspond to a username that’s only used in the cloner plugin.

    I am at a loss to understand how on earth credentials digested only by your plugin are constantly being reformed after all the purging and service restarts the plugin is deleted from the system!

    If I re-install the plugin and network activate I am instantly brought back to the plugin page for the main site within multipress with all the the fields populated.

    This is getting beyond a joke!

    helena46

    (@helena46)

    Hello @drumsk8,

    1) delete plugin folder “/wp-content/plugins/duplicator-clone”. It should be deleted when you delete the plugin;

    2) open the page “<your_domain>/wp-admin/options.php”. Here all WP settings are saved. Duplicator plugin settings are located in “site_duplicator_options” parameter. However, these settings does not influence the plugin version.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Won’t fully uninstall’ is closed to new replies.