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
