• Resolved Ov3rfly

    (@ov3rfly)


    After uninstall there are files remaining in uploads folder:

    /wp-content/uploads/wpo/images/wpo_logo_small.png
    /wp-content/uploads/wpo/images/wpo_logo_small.png.webp

    Please remove.

    WP-Optimize 3.2.12, WordPress 6.1.1

Viewing 15 replies - 1 through 15 (of 30 total)
  • Plugin Support vupdraft

    (@vupdraft)

    Hi,

    Apologies for this, I will pass it onto our development team

    Thread Starter Ov3rfly

    (@ov3rfly)

    After uninstall there also remain database tables and option entries.

    $wpdb->base_prefix}tm_taskmeta
    $wpdb->base_prefix}tm_tasks

    This has been reported many times and is still not fixed, example here more than 2 years ago (marked as “resolved” which is clearly wrong).

    Plugin Support vupdraft

    (@vupdraft)

    Hi,

    Sincere apologies for this. I have asked our lead developer for the plugin to follow up on this.

    Thread Starter Ov3rfly

    (@ov3rfly)

    Why has this issue been marked as “resolved”?

    It clearly is not resolved, there are still remaining files, even more now after this weird “re-release” of a changed 3.2.12 version without updated version number.

    /wp-content/uploads/wpo/images/wpo_logo_small.png
    /wp-content/uploads/wpo/images/wpo_logo_small.png.webp
    /wp-content/uploads/.htaccess
    /wp-content/uploads/wpo-plugins-tables-list.json

    Please remove.

    Additionally a Cron error is triggered:

    Cron reschedule event error for hook: wpo_reset_webp_conversion_test_result, Error code: invalid_schedule, Error message: Event schedule does not exist., Data: {"schedule":"wpo_daily","args":[],"interval":86400}

    Please fix.

    WP-Optimize 3.2.12 (new release with same version), WordPress 6.1.1

    Plugin Support vupdraft

    (@vupdraft)

    Hi,

    The post was marked as resolved as it is being investigated by our development team and we will be creating a fix for this (it’s not a setting that I can ask you to change on your side). It will need to done by our development team.

    Thread Starter Ov3rfly

    (@ov3rfly)

    Feel free to mark this issue as ‘resolved’ after a plugin update with a fix has been released by your development team, not before.

    Thanks.

    Plugin Support vupdraft

    (@vupdraft)

    Hi,

    As we have created a corresponding ticket on our development board, this ticket will be marked as resolved.

    We would recommend that you keep your plugin updated and that you keep an eye on the Changelog for further information.

    Thread Starter Ov3rfly

    (@ov3rfly)

    It actually does not matter if/where you create internal tickets somewhere else.

    This issue is not resolved, that’s why this issue is also marked as not resolved.

    Feel free to mark this issue as ‘resolved’ after a plugin update with a fix has been released by your development team, not before.

    Thanks.

    Plugin Support vupdraft

    (@vupdraft)

    Company policy is to mark the issue as resolved once it has been recreated and reviewed and a course of action has been decided . We agree that this should be looked at and a fix will be made.

    As I said before, please keep an eye on our Changelog for further details.

    Thread Starter Ov3rfly

    (@ov3rfly)

    Stop marking this issue as resolved every day.

    This is www.ads-software.com plugin support forum, not your company bug tracker. Your company policy does not matter here.

    Feel free to mark this issue as ‘resolved’ after a plugin update with a fix has been released by your development team, not before.

    Thanks.

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    Moderator note:

    @ov3rfly “resolved” really has no meaning except as a flag for the devs to know what they’ve “done” and what they haven’t. The argument is pointless as long as they keep responding. ?? It’s optics, not meaning.

    Plugin Support vupdraft

    (@vupdraft)

    If you check the changelog, a fix for this has now been implemented in the latest release.

    Thread Starter Ov3rfly

    (@ov3rfly)

    If you check the server after plugin uninstall, there is still remaining file:

    /wp-content/uploads/.htaccess

    Please remove.

    Additionally still a Cron error is triggered:

    Cron reschedule event error for hook: wpo_reset_webp_conversion_test_result, Error code: invalid_schedule, Error message: Event schedule does not exist., Data: {"schedule":"wpo_daily","args":[],"interval":86400}

    Please fix.

    WP-Optimize 3.2.16, WordPress 6.2.2

    Plugin Support vupdraft

    (@vupdraft)

    A ticket has been created on our internal development board.

    As you previously said this forum is not a bug tracker so I am closing the ticket. Please keep an eye on our changelog for a fix.

    Thread Starter Ov3rfly

    (@ov3rfly)

    a fix for this has now been implemented in the latest release.

    An incomplete attempt for a fix has been made. The issue is not fixed. You could also work on handling valuable user feedback. Your behaviour appears unprofessional in a support forum.

Viewing 15 replies - 1 through 15 (of 30 total)
  • The topic ‘Files remaining after uninstall’ is closed to new replies.