260.000 images: Any solution?

same problem here.

I wrote my own scripts to fix it.

Basically you can simply loop all your attachments, then you check if they are attached to a post. Or if the post exists.

Also I wrote a script to check if all my hundred thousands+ posts have an existing attachement and if it’s physically available. (file_exists)

After that you have a clean database again ??

Wish I could share the code but I sold the project and don’t have any source of it anymore.

Hello mewcrazy,

I’m glad to read that you resolve the problem and you win some money, did you do it in php? normally I can make one script to do the clean up, but I think that can be dangerous, because this one have to have a good configuration for not delete used image(normally the plug-in have this option), if you see in the reviews not all people had a good configuration, and they make mistakes.

Maybe you did one script adapted to your client, this way the result will be fine.

You can always contribute to the main code, I will try to put the new code online (I was/making a new code)

Yea my solution was written in PHP but I developed & used it in CLI only to avoid timeouts or anything.

So my solution was kinda dirty, plus I didn’t use any Javascript or anything. But as much as I can remember, your plugin was working fine. The problem was that my browser performance dropped so much after 50.000 images that every conversion took longer than 10 seconds or so. So what I would say is that you make some kind of reload or cache flush after 15 minutes. Not sure where exactly the roots of this problem is though. That’s just my guess. I know in PHP that you have to flush the cache or all gets written in the memory.

Maybe you’re in luck and your new code works fine ?? If I ever get back into that subject then I’ll be glad to contribute.

In the version PRO you have the Delete All Automatic button, and this will page by page and delete all not used image ??
I put this option only in the pro, because this is a dangerous feature, if the people use for the first time this plugin and they didn’t do testing, they will destroy their site, so first they can use the WordPress version, see if the plugin work fine for them and after they can go and use this feature in the version PRO

Now they can do it with the PRO version