Export gets stuck

Hi Andrew,

Just repeating here what was in the email, for anyone else with the same issue:

What I’m guessing, is that the server has a maximum execution time limit set (30 seconds is common on shared hosting environments). Who’s your hosting provider/plan or are you running from a local computer?

The last release overcame this kind of limitations for just one kind of export (GitHub), but I will need to adjust all parts of the export to run in a way that doesn’t hit these limits.

We can see if we can try different hosting/get the limits removed for you in the meantime, but it will probably require a decent day’s worth of work to get the plugin’s underlying mechanisms rewritten…

Hey Leon – thanks for replying.

I created a Github repo to test it with but the export doesn’t even get going (I just see the old export log and nothing new gets added).

I’ll chat to my hosting provider today to see if they will remove the limits temporarily, but I don’t think they’ll remove them permanently…

I’m happy to use Github, so maybe we can get that going instead? Maybe I’m doing something wrong? Or some access issue on the server etc?

Hi Andrew,

Thanks for following up. I mislead a bit with the GitHub reference – the GitHub export process in my case, at least, was slower than the crawling of a small site. So, the latest release resolved the issue of long-running process just for the GitHub part of the export. In doing this, I realized that the main crawling function likely suffers the same problem on shared/limited hosting. That will be the next main fix.

I’m guessing that it’s what’s causing it for you, either a certain time or amount of memory limit being hit.

There is a chance it’s something else to do with the specific theme you are using.

Could you please try switching to a WordPress default theme like TwentySeventeen and seeing if that completes (no need for trying the GitHub export in this case).

Thanks for your patience while this is being resolved.

Cheers,

Leon

No worries, Leon. I spoke to my hosting provider and got them to increase the exe limit. It does create loads of files now so I think all I need to do is make sure the limit it long enough for the full crawl to take place. There’s about 250 pages with loads of images so I reckon it’ll take upwards of a half hour or more… I’ll update again when I have more news.

Hi Andrew,

I’ve managed to put this together today, which has just worked for me to overcome the limits for large exports. Please see if it gets through for you:

https://github.com/leonstafford/wordpress-static-html-plugin/releases/tag/andrewtest

Cheers,

Leon

Hi Leon

I used the last github release to overwrite the version on available via wordpress plugins that seems to break.

It finishes this time, which is great. Only issues I noticed were no main index.html page was created and it didn’t upload to S3, only made the zip but not sure if that is my end or the plugin.

Thanks for all your hard work.

Let me know if you need help debugging this.

I plan to move many sites to S3.

– Javier

Hi Javier,

Sorry for the late reply, this got buried in my inbox.

Thanks for using the plugin and the kind words.

The latest copy from GitHub (if downloading the zip from master branch) is the development build and I’m not sure if the index.html fix got pushed up from my local box yet, but I’m closer to pushing some more fixes up and then it will be there.

The best would be to hold out for the next main release, else, what issue did you encounter with the current official release from www.remarpro.com?

Thanks for your patience. I’m trying to get the next release out ASAP to get these main issues with maximum execution time resolved for all those on shared/limited hosting. It’s looking quite promising so far, just a matter of hours on keyboard ??

Cheers,

Leon

Hi Leon, sorry for not replying sooner but it’s been hectic here. This plugin did work once I extended exe time, but the issue that ruined the whole static page thing for me is the developers used WooCommerce for absolutely everything! This means the site would need a lot of work to be able to operate as a static site. That’s time I cannot put into it, so I’ve had to shelve it for the meantime and simply find a better WP host! Very frustrating!

But thank you very much for the work you put in; it’s a great plugin. In the end it took almost 2 hours to run, but the site is over 7GB, so not surprising….

Would you like me to leave this issue as unresolved until you and Javier have sorted your issues out?

Hi Andrew,

No worries. Wow, 7GB, that’s a decent export!

Yes, that’s fine to leave this issue unresolved, though you may get a notification for it later. Else, it’s OK to mark it resolved and we can make new issues for anything remaining.

Shoot me an email if you need ideas for setting up the new server. I have experience with “infrastructure as code”, ie defining your server configuration in code, then deploying it, along with your codebase to a standalone server or cloud provider, like AWS. Makes testing out the same configuration on servers of differing performance/capabilities much easier after the initial investment.

That’s a nice way to do it, but I also know of some *very* trafficked WordPress websites making $ that are held together by chewing gum, so depends what the needs are ??

Cheers,

Leon

@leonstafford.

Thanks for your reply.

No worries.

We had to go back to older version, 1.9 I think to upload to S3 again.

Please email me: [email protected]

I want to help you test whatever the next latest release is.
I can test/QA this for you on various platforms services and give you my feedback.

I don’t get the updates of this thread without manually checking so email is best.

Also, happy to donate to your cause.

– Javier

• This reply was modified 6 years, 9 months ago by javierj.
• This reply was modified 6 years, 9 months ago by javierj.

Leon, thanks for the kind offer. Our WP site is merely a stepping stone while we dev our own so there’s no need to go to too much trouble. (I thought generating static pages was going to be a few hours work, boy was I wrong!)

I’m going to mark this as resolved, hope that’s ok.

@andrewpery

Why would you mark this as resolved if others are still having issues?

This isn’t resolved in this version.