Just generates empty folders

Hi Acurran,

Please try these steps:

https://forum.wp2static.com/-33/how-to-troubleshoot-a-failing-export

And you may find 5.9 to work better:

https://forum.wp2static.com/-30/how-to-install-the-latest-preview-of-version-59-of-wp2static

Please let me know what works.

Cheers,

Leon

@leonstafford

I can report the same behavior as @accuran with the version provided on the WP Plugin Website.

For version 5.9, it did create the website but it rendered incorrectly. I have a feeling this may be due to how this theme works.

As an example see https://roberttisdale.com vs https://roberttisdale.com/mystaticsite/ .

It does appear that it actually writes the content to the folders and these do appear (mostly) correctly if the pages are accessed directly.

As an example see:

https://roberttisdale.com/mystaticsite/about-me

Also worth noting: I tried both “Intelligent” and “Brute Force” methods. Same results for both.

Hi @rtisdale,

Nice looking site!

On the /mystaticsite, the links are definitely not getting rewritten properly, not sure what’s going on there. A couple of issues I’m working on around rewriting, then it may be worth another shot.

The Brute-force isn’t wired up yet, but is still needed in cases like these. Forgive the technical jargon, but it uses “regular expressions” vs the proper parsing done now in 5.9 (intelligent). Parsing is the best option 90% of the time, but we need that brute force when the parser just can’t deal with the HTML it encounters for whatever reason.

Let’s keep this dialog open and the good thing is that if it’s affecting a few people, it’s a common problem with a common solution waiting to be found ??

Cheers,

Leon

@leonstafford

Thanks! No worries on the technical jargon, I work in tech myself (Infrastructure Automation Engineer)

Stay in touch and if you need any help troubleshooting, happy to give you a hand.

On another note:

https://xkcd.com/1171/

??

Hi,
Thanks for the responses.
I’ve tried version 5.9. Now I get this error:

An error has occurred, but let’s fix it!

Everyone’s WordPress hosting environment and configuration is unique, with different plugins, themes, PHP versions, to name a few. Whilst the plugin does its best to support all environments, sometimes you’ll encounter a new issue. Sometimes we can adjust the settings in the plugin to overcome an issue, other times, it will require a bugfix and a new release of the plugin (usually a quick process).
Troubleshooting:

Switch to the Logs tab to look for obvious errors
Check your PHP/webserver error logs if nothing in WP2Static’s logs
Switch to the Help/Troubleshooting tab to look for obvious errors

Nothing obvious in plugin Logs tab.
Examples of the errors in server error log:

403 GET /wp-content/plugins/wordpress-static-html-plugin//views/wp2static.css?ver=5.9 HTTP/1.0

client denied by server configuration: /****/httpdocs/wp-content/plugins/wordpress-static-html-plugin/views/wp2static.css, referer: https://***/wp-admin/admin.php?page=wp2static

404 GET /wp-content/uploads/WP-STATIC-MODIFIED-CRAWL-LIST.txt HTTP/1.0

500 POST /wp-admin/admin-ajax.php HTTP/1.0

Warning *** mod_fcgid: stderr: PHP Fatal error: Uncaught GuzzleHttp\\Exception\\ConnectException: cURL error 6: Couldn’t resolve host ‘www.***’ (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) in /***/httpdocs/wp-content/plugins/wordpress-static-html-plugin/library/GuzzleHttp/Handler/CurlFactory.php:191, referer: https://www.***/wp-admin/admin.php?page=wp2static

Note the website is not live and does not have a domain name resolving to it, I am just resolving the domain name with my local hosts file. Can this plugin make a static copy under this circumstance?

Hi @acurran,

Aplogies for the late reply, have been on the road a bit the last few days.

Thanks for trying the pre-release version.

If you have control over your hosting environment enough to modify its hosts file, then you can use the same technique that you’re using on your local computer to resolve MYDOMAIN.COM to xxx.xxx.xxx.xxx

Alternatively, if you can’t do that, then you could change WordPress to point to itself, at xxx.xxx.xxx.xxx. Then, when the plugin crawls, it will resolve fine.

One of those techniques should definitely work for you. If still having issues, please let me know.

If you do get it fixed, please let me know and I’ll close this support ticket, else I’ll do so in about a week if I don’t hear from you.

Cheers,

Leon

Version 6.0 is now released, which should solve the rewriting issues.

I have a new diagnostics theme and build tool, which is highlighting any remaining source code rewrite issues, which may come from code generated by certain themes/plugins:

https://wp2static-vultr1.netlify.com/

If you’re still facing any source code rewrite issues with 6.0, please create an issue in https://github.com/leonstafford/wp2static with an example of the original source code you get when you load the WordPress site in your browser and choose “View Source”, along with the output from the plugin, when you visit/open up the generated HTML file.