• Resolved Silviu

    (@silviu8)


    Hello, I have encountered a lot of false positives (majority of the images) whilst trying to use Media Cleaner for the first time. I may know what the issue is, but wanted to double check and hopefully get some advice, as I couldn’t find the information: is the free version of the plugin compatible with the WordPress Classic Editor plugin? Thank you in advance ^^

    • This topic was modified 1 year, 8 months ago by Silviu.
Viewing 12 replies - 1 through 12 (of 12 total)
  • Thread Starter Silviu

    (@silviu8)

    Hi, could anyone confirm if lots of false positives would be fixed by purchasing the paid version of this plugin?

    Plugin Author Jordy Meow

    (@tigroumeow)

    Hi @silviu8,

    I don’t think a lot of users will reply to you on this, though that would be really cool ?? I wished the forums would work this way.

    Best way is to try it (and I refund anyway if any issue, or just if I am being asked). Also, we can talk about the Pro Version on those forums, it’s not allowed.

    Nearly all my images get dtected now after the WP3.2 update. Worked flawlessly before.

    same issue here, now media cleaner is detecting almost all my images as not in content and ready to be deleted. I think the issue is coming from the last WP update.

    Thread Starter Silviu

    (@silviu8)

    Must be that then, as I only installed the plugin after the latest WordPress update. Suppose there is not much we can do about it? It’d be great for the the plugin (or at least the free version) to be functional, as what it advertises is exactly what I need!

    Plugin Author Jordy Meow

    (@tigroumeow)

    I am reading your comment guys; I don’t encounter the issue. I’d be happy if you could debug a bit more, for example try to see what kind of images are wrongly detected as “not used”, and how they are used in reality? That, I need to know. Then I can replicate, and fix if it’s a bug ?? Thanks!

    hello Jordy, the issue is persisting. Plugin is detecting images to delete that are not attached thru the media, but they ir in use in a post or product. This happens since last WP update. Before, it was working fine.

    Plugin Author Jordy Meow

    (@tigroumeow)

    I think it’s very specific, I have ton of users but I didn’t have any feedback on this really, so I believe it’s something else.

    You are using the Free Version? How those images are used in Posts or Products? You absolutely need to tell me the exact use case, how the images is actually used in the Post Editor (through an Elementor module, if yes, which one, etc, etc).

    Hello, images are used in my case as product images in the woocommerce default product plugin.

    check image here:

    https://ibb.co/s9nTg2Q

    Plugin Author Jordy Meow

    (@tigroumeow)

    Hi guys,

    I found the issue, and indeed, the SQL request related to attached images (and a bit more than that) was completely failing with the new version of WordPress. More specifically, the $wpdb->prepare function that we are supposed to used was returning an empty string in some cases. This is very weird and odd, I haven’t seen that bug mentioned anywhere, but it’s definitely an issue.

    There are workaround, and I applied one for that part of the code which was failing. If you find any issue, absolutely let me know. I am using this prepare function pretty extensively, I am sure it works in 99.9% of the cases, and hopefully, this was the only part of my code that was affected by that issue.

    Please update to the latest version (6.6.3), and try again. I am looking forward to your results ?? Happy Sunday, everyone!

    Hello, I just updated and… it works! Any reward for debugging it? Maybe the pro version for free? ?? Thanks.

    Rather support him an buy the pro version as this little free tool is very good in dectecting not used pictures. After the last update it works also well for me again and iam happy i dont have to manually scan my media libary.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Lots of false positives – potentially a Classic Editor issue?’ is closed to new replies.