Doesn’t Work on Large Sites

Hi,

Unfortunately, the only way is like this; it’s a very intense process and we can’t use WP-CRON for this as it will kill your visitors experience.

Normally, you don’t get logged-out of WordPress like this for a month or so; I am not sure why that happens to you. Maybe a security plugin does it, or your hosting service?

Would be interesting to have feedback from other users; could you change the title from “Doesn’t Work on Large Sites” to “I get logged out before the scan has finished”?

Because it works very fine on large sites, and I would like to help you and find users with exactly the same issue.

Please note that it’s possible to use WP CLI, for advanced users with the Pro version.

Well, so far the only feedback I’ve gotten from you is instructions for how to generate a log file that do not work. I followed your instructions on how to enable debugging in web.config but that didn’t result in anything new being written to the debug.log file which remains the same as it was before I enabled debugging per your instruction.

This problem has remained the same whether I’ve been logged off or not. The log off just seems exclusive to my last attempt to run your plugin which results in several days wasted with nothing to show for it beyond a message saying there were over 47,000 errors.

• This reply was modified 2 years, 6 months ago by notgoodenough.

It wouldn’t surprise me if my last migration alone resulted in over 47,000 images remaining on the file system of the source website which has over 300,000 posts/images.

Screw the user experience, use WP-CRON if that is what it takes. I’d rather leave users frustrated for a few days every few months than have to deal with this crap anymore.

How about simply limiting the maximum result size so that owners of large sites can do it in batches? So, program your plugin to stop scanning at 10,000 images if I enter that into an input someplace.

How do you use WP CLI?

• This reply was modified 2 years, 6 months ago by notgoodenough.

You need the Pro version:

https://meowapps.com/media-cleaner/tutorial/#Basic_Commands

I do have the PRO version, but the instructions stop short at telling anyone how to access WP CLI in the first place. I see screenshots of what to enter into it, but nothing indicating where to find it in WordPress.

What is the WordPress URL for WP CLI?

I’ve been looking all over /wp-admin/ but cannot find the CLI in there anywhere.

The tutorial mentions using SSH, but offers no guidance as to how to access SSH in the first place. I’ve accessed SSH before, but never for the purpose of doing anything with WordPress. Is this something that can be done in cPanel?

If I must use the basic terminal in WHM or my host’s control panel, how do I make sure that I am running it just for one specific site under a specific cPanel account?

• This reply was modified 2 years, 6 months ago by notgoodenough.
• This reply was modified 2 years, 6 months ago by notgoodenough.
• This reply was modified 2 years, 6 months ago by notgoodenough.
• This reply was modified 2 years, 6 months ago by notgoodenough.
• This reply was modified 2 years, 6 months ago by notgoodenough.

Hi @notgoodenough,

WP-CLI is for advanced users ?? I can’t really write a tutorial about SSH, or WP-CLI, because I would need to write very extensive ones as they can get really complicated, also depends on your hosting services and how everything is done on your end. I provide commands for WP-CLI and I can provide support about that, but if you want to learn about SSH and typing commands, it’s probably better if you team up with a friend or someone who is used to do all that.

The main site about WP-CLI is this:
https://wp-cli.org/

I am sure you can have SSH access through cPanel, but cPanel can be set up in many different ways to that’s really up to your hosting services. You could also ask them if you can use WP-CLI on your install. If they say yes, then you can try to use cPanel to access SSH on your install, and run the commands I mentioned in the tutorial.

Jordy,

Your response further proves my point I feel because you’re basically saying that you don’t have time to write a tutorial capable of bridging the gap for users that have been using your plugin for well over a year only to find it broken suddenly due to not being able to handle large amounts of information. I feel that you owe it to everyone whose ever paid you for a PRO subscription to tell them how to keep using the plugin after their sites reach certain sizes.

It seems rather deceptive and lazy for a developer to claim their plugin works with a few lines of code via CLI and THEN say that there is much more to it. It reminds me of the time I migrated a site from .Net framework to .Net Core only to find out the tutorial released by Microsoft didn’t inform anyone that the sample code could only handle a few hundred records tops. The reason for that was that Microsoft for the purposes of providing people with as simple a tutorial as possible told people to get all posts at once and work from there to avoid repeating themselves without mentioning that pagination would need to be added later. I had dealt with pagination before which is why I was surprised to see them get all posts, but I figured they would probably only be doing that if they built pagination into .Net Core so that the user doesn’t need to. Turns out they were just being lazy.

You mention cPanel being up to my hosting service. I have an unmanaged VPS with cPanel installed using whatever default settings plus whatever changes I’ve made. I have a root WHM account and 5 cPanel accounts with multiple domains under each one.

Can you at least tell me how to install WP CLI in that environment?

The tutorials I have seen so far typically only have a generic explanation for how to install WP CLI on the sever, but I don’t see how I could move past them to actually working on my project specifically because wouldn’t I need to install something like that on a site by site basis?

• This reply was modified 2 years, 6 months ago by notgoodenough.

I am using Media Cleaner Pro in a lot of websites with more than 100k images each. I use it both from wp-admin and from wp-cli without any issues. If you have any issues maybe related to your website or your server.

To download wp-cli SSH on your server with the username of the hosting account and run these commands:

cd public_html
curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar
mv wp-cli.phar wp

and then to scan the images run:

./wp media-cleaner scan

Thanks Christos,

I’ve just finished coming to terms with the fact that this could take forever and I will have to dedicate time to figuring this out. Since I have not done it before I don’t know if it will take 2 hours, 2 days, 2 weeks, etc.

When finished I do intend to consider writing an article about how I did it just so that others might save the time. However, I think it would look better if the plugin developer wrote an article like that instead of a user after having to figure it out themselves. I think such an article is likely years overdue since it should have been written when the plugin was released.

It should be assumed that most people that download any plugin don’t know what a command line is let alone how to use one. That is especially true with WordPress which is marketed as a solution for those that cannot code at all.

Christos,

I have just installed it on the right account per your instructions. Now I will try to run the plugin, but first what does “mv wp-cli.phar wp” do?

I ran that but noticed no response

Looks like I spoke too soon. When I type “php wp-cli.phar –info” into the terminal without quotes per the instructions at https://wp-cli.org/ and all I got was “Could not open input file: wp-cli.phar”