Leon Stafford

Hi Lauren,

This is from an older version of the plugin, now called Static HTML Output:

You can get latest version of that:

https://statichtmloutput.com/thanks-for-donating/

For latest version of WP2Static (different plugin than what you have been using):

https://wp2static.com/thanks-for-supporting

I’d suggest trying with WP2Static, we’ll try to put that on wp.org for easier downloading soon.

Else, with your current plugin, you may have luck if you enable Autoptimise plugin and let it optimise your CSS, JavaScript and Font files, that can sometimes be a quick win for the issue you’re seeing.

Cheers,

Leon

Hi @brunowillis,

You can grab from here for now:

https://wp2static.com/thanks-for-supporting

I’m planning a new licensing server and I’ll contact all purchasers when there’s a new place to go.

Please let me know any issues you encounter.

Cheers,

Leon

Many thanks for explaining it and giving me ideas, @alanfuller!

A quick wp_cache_flush() between calls meets my needs for now. It’s a small dev environment, so doesn’t hurt to blow away all cache, but your suggested wp_cache_get() sounds much safer for anyone else looking to solve the same problem.

No, they’re all independent plugins, currently with different approaches that may work better in certain scenarios. There’s a bit about it on the forum, but will announce/do some videos to show the differences.

Which one should I use today? For most general users, I’d say Static HTML Output 6.6.21 gives best results for lowest learning curve.

New WP2Static has quite a few users, but currently leans more towards more advanced/scripted workflows.

SimplerStatic is just an updated version of SimplerStatic at the moment, but that in itself, has benefits for some low resource hosting environments if the other 2 don’t work.

@giancarlo74 if using from GitHub, you can “Watch” the GitHub repository, either for all releases, or for all communications.

For anyone who’s purchased license or submitted email when free downloading from https://wp2static.com/download/, I’ll send emails when there are good stable new releases available (I don’t want to abuse the trust by sending too many emails).

I’m still considering better ways to do things, so may make further changes to website and build in some update mechanisms within plugin. Especially for WP2Static, where there are many add-ons available, will look to make those installable from within the plugin.

Of course, here you go!

https://github.com/WP2Static/static-html-output-plugin/files/4943854/gulshanwinziptest.zip

Known to work with Zip and BunnyCDN deployment methods so far, I haven’t tested the others.

Please let me know if that helps

@quintcyril 6.6.21 here: https://github.com/WP2Static/static-html-output-plugin/files/4822705/static-html-output-plugin-6.6.21.zip

Probably best to deactivate and uninstall any other ones first. Note, this one will show as “Static HTML Output”, not WP2Static.

If you need native Windows filesystem support, ie, for XAMPP, there’s another version I can share. Those changes aren’t yet released anywhere.

Hi @klaro,

Apologies for the alarm/confusion. I posted a little info here:

https://staticword.press/t/removal-of-wp2static-from-wordpress-org/

Cheers,

Leon

Don’t worry, @quintcyril, I feel your pain!

This was my day(s) debugging it a cpl months ago:

https://github.com/WP2Static/static-html-output-plugin/issues/58

The open issue for this is at https://github.com/WP2Static/static-html-output-plugin/issues/15

Hi @quintcyril – OK, this now looks more like an issue with the encoded Japanese(?) chars in filenames.

Unfortunately, the only way I can recommend today for these is to use ZIP export method, then use AWS’s CLI tool to do aws s3 sync to get the files in. This works fine, there’s an open issue around this in one of the GitHub repositories and no quick fix in sight.

Hi @quintcyril is this the first time to try the S3 export or were you successful before and this error has just occurred today?

If this is first time attempting, please try unchecking the 4 boxes for Public ACL settings in the S3 bucket’s properties, this is a common issue, there may be better explanation on our own forum or GitHub Issues.

Basically, we set each object we upload to S3 as public-read, so need those permissions relaxed.

oops, that link to GH: https://github.com/WP2Static/wp2static-addon-cloudflare-workers

Thanks @samunderwood,

Yes, let’s get it sorted!

My next step would be to export the site using ZIP method and then manually deploy to a Workers site using Cloudflare’s Wrangler CLI tool. If that goes smoothly, then it’s less likely a content issue and more a plugin issue.

That can be a bit fiddly, though, so faster would be to check the server’s logs for any errors at the time of export.

It appears to me that it’s failing behind the scenes, but the plugin isn’t capturing/recognizing the error and aborting the deployment.

We can also try deploying via the CLI using the plugin, with the following commands:

– wp wp2static detect
– wp wp2static crawl
– wp wp2static post_process
– wp wp2static deploy

Unfortunately, I haven’t been working on the V7 version that you’re using for a while, instead building up to a long overdue release of an updated V6 before I can focus more on V7, else, there are some updated development builds of V7, not yet made into releases that have some better logging.

This is the GitHub repo for the CloudFlare add-on, which is probably a better place to continue this discussion if you find any more clues after the above or need more ideas.

I can help with the debugging to CF or others if you have no luck if you send me an export of your site.

Speaking of which, if you switch off all other plugins, switch to default theme, will that deploy? If a clean WP with same environment, will it deploy?

Once we can isolate the exact cause, should be able to do something about it.

Cheers,

Leon

Hi @samunderwood,

Sorry to hear about that! Happy to refund if you like.

What I think may be the case here, is an image or file over 10MB or (less likely) site over 1GB.

These are unfortunately limits with Cloudflare Workers/KV sites.

Let me know if you can track down any large files and try to skip them.

Cheers,

Leon

And lastly, when properly exported as an offline site, like with HTTrack, it tries to rewrite all URLs to be document-relative, meaning, from any page in your site, it will adjust links to other pages, images, etc to be a direct route from that page… so instead of /a-link, if you are on your site’s about page and want to go to the homepage, it will link like ../, meaning, go up one level, and will resolve correctly, relative to the about page