Doesn’t Work on Large Sites

I also do not see any .phar files in my public_html folder in file manager.

Could I just download the file and upload it via File Manager?

This command renames wp-cli.phar to wp :

mv wp-cli.phar wp

Also I forgot that you need to make it executable:

chmod 755 wp

You can also upload the file using a FTP client. Don’t forget to change the permissions to 755.

I just tried doing it again and it looks like the file is downloaded according to the terminal output, but never installed.

It is installed in the right spot as a filed named wp, but running wp –info still results in an error.

Plus, Stack Overflow indicates that something else might be needed for multi site accounts. I have a primary domain hosted in the public_html folder with another hosted in a subfolder. The primary is the one I am trying to use this on.

The problem seems to be after running

mv wp-cli.phar wp

After that the wp-cli.phar file is changed to just wp after which it cannot be accessed. On the other hand, not running that and running php wp-cli –info works great until the aforementioned line is run.

When I try to run the sudo version of the command I am told that my account “is not in the sudoers file. This incident will be reported.”

How do I add an account to the sudoers file and where is that file?

In the past I have only used sudo as root user

I solved the sudo issue by adding the account to a group in WHM. Unfortunately, this has not solved the problem. When I run the sudo command it appears to work, but wp –info is still nothing. However typing “php wp –info” produces the output I expected before adding the php prefix.

ABRACADABRA!

Turns out Jordy and www.remarpro.com both left the php prefix requirement out of their wp-cli tutorials which is why it wasn’t working. Now if you run the commands from his tutorial with “php ” in front of wp it appears to be working.

Now it seems to be stuck at analyze content 100%. I tried to copy the output by highlighting it in the terminal and pressing control+c but that just appended “^C” without quotes to the end of it.

I ran the command again, but it looks like I jumped the gun. When a new scan is started using wp-cli does that automatically cancel the first one?

The terminal now says:

Error: There has been a critical error on this website. Learn more about troubleshooting WordPress. There has been a critical error on this website.

Method: Media Library
Check Content: yes
Check Live: no

…………

Notice how that error message gives me nothing to work with? It doesn’t give you a status code or a location, so I can’t imaging what the problem could be.

Alright, my WordPress debug log suddenly started working somehow, so I have more information:

PHP Fatal error: Maximum execution time of 999 seconds exceeded in /home/mysite/public_html/wp-content/plugins/media-cleaner-pro/classes/core.php on line 844

I didn’t know anything had a max execution time of 999 seconds. How do I set the max execution time to unlimited?

I increased my max execution time to 3000000 but still got the same error. Is there some cap on the max execution time that I am not aware of?