mscience

I found some ways to fix the “can’t ping itself” issue. What I had to do is to add a couple entries to my /etc/hosts file. In my case, with my wordpress box running on an AWS EC2 server, I added the IP address cited in the diagnostics report entry, and I also added 127.0.0.1 and pointed both to the url of my wordpress install.

While this fixed the issue – it appears the cancel job can’t truly cancel. Just spins forever.

This appears to have to do with entries it puts in the wp-settings table to track its status. I can clear those records and then I’m able to restart generation job.

Sucks but seems to work for that issue.

Then there’s the “fix the forever but never cancel” issue.

Here’s what I did.

Again, I’m on an EC2 server, and it has a locally install mysql server. I don’t have PHPMyAdmin or anything so I had fix this via command line.

Here’s what I did:

1. run the query select * from wp_options where option_name like ‘%static%’; This will give you the entries that are related to the state of things with the plugin.

2. Look for the record that has the option_name “simply static”. This is the record that contains the current stuck job”. If you delete this record the button resets to the start generation state. You do run the risk of erasing your settings if they differ from the default stuff so check that.

3. This will let you start the job again…

• This reply was modified 5 years, 9 months ago by mscience.
• This reply was modified 5 years, 9 months ago by mscience.