wp2static exports first 2 blog pages only
thank you for creating such a great plugin! It's exactly what I was looking for.
After my self-hosted Wordpress account was hacked, I've changed my strategy and will now develop/write my blog locally and export the static pages to my online account.
Unfortunately I'm currently facing the following issue.
I'm using the Wordpress theme "Aperture Portfolio" (version 1.0.5). It's configured so that it doesn't use a static front page but shows the latest three blog posts.
The address on my local PC is http://localhost/shot10000/
The theme shows an "Older posts" and "Newer posts" link.
When exporting the site using your plugin, it creates an html page for page 2 only (folder "page" contains only sub-folder "2" with the "index.html" file).
The other pages are missing and the next-link from page 2 to page 3 is broken.
In the log for the discovered URLs during crawl, only page 2 is listed. In the list of detected Wordpress URLs, even page 2 is missing.
Do you have any idea what I'm doing wrong?
Thanks for your support!
- 14 replies
- Leon Stafford @leonstafford2019-01-27 17:27:04.759Z
Perfect timing! Just released version 6.4 that fixes this :)
Please let me know if that works for you,
you mean Version 6.5, right?
I just updated my installation.
The good news: the missing pages are now listed in the log under "Detected WordPress URLs"
However, the exported index.html page shows the 404-error-page of my blog ("Oops! That page can’t be found.")
Something is still going wrong. :)
- Leon Stafford @leonstafford2019-01-27 18:06:45.757Z
Ok, from 6.4, we have an option Advanced > Debug Mode.
Please check that, run again, then email me through the Export Log to email@example.com, it may yield some clues.
I can check that tomorrow (2am here).
In the meantime, you can try to pinpoint it by switching to the TwentySeventeen theme, disabling all plugins and trying again.
That can tell us if it’s a theme, plugin or other issue.
I sent you the export log and the generated index.html file via Email.
- Leon Stafford @leonstafford2019-01-27 18:36:14.523Z
Took a look and nothing obvious jumped out at me. Are the other URLs fine and just the homepage givinh an issue?
Any luck with the theme/plugin adjustments suggested?
I switched back to TwentySeventeen and disabled all plugins except wp2static.
Unfortunately this didn't help.
The posts themselves (folder /[year]/[month]/[article]/[article]/index.html) are fine.
All overview pages (folder /beiträge/page/[page number]/index.html) and the main file (/index.html) show the 404 error page of WordPress.
Is there anything I can do to help analyze the problem?
PS: in version 6.4 the export worked fine. The only issue I had was related to the missing URLs.
- Leon Stafford @leonstafford2019-01-28 01:39:55.059Z
OK, that helps. Looking at the logs with fresh, caffeinated eyes, I think it's something like this:
BAD RESPONSE STATUS (404): /?post_type=custom_css&p=44
So I think it crawls the homepage properly first, then a subsequent undesired URL is 404'd and saved over.
I'll try to reproduce this here and avoid generating those unintended URLs.
I can confirm that Version 6.5.3 solves the issue with the 404-index-page.
But: the initial bug is back: it exports overview page 1 and 2 only. All other pages are not exported and the links are broken.
Wait… I'm a bit confused.
According to the log (detected URLS), the following pages have been crawled:
If I look at the folder structure of the exported website, it contains:
(3-7 are missing)
But there is a folder "Beiträge" ("Posts" in German) which contains the following subfolders:
And a Folder "Seiten" ("Pages" in German) with sub-Folder
These folders contain an index.html file which shows the 404-"Ooops something went wrong" page.
The broken link is
Is it a maybe a localization issue ("Beiträge"/"Seiten")?
BTW: the following folders are also mentioned in the log "404s encountered"
- Leon Stafford @leonstafford2019-02-06 20:51:45.504Z
I have one more fix ready for next release regarding pagination URLs.
That may be secondary to the higher-order ASCII chars, though, not sure if it will handle those in the URLs currently, has been an ongoing issue I need to deal with.
sorry for my late reply.
I'm sorry to say but the fix regarding the pagination URLs still doesn't work on my installation.
Page1 and 2 are the only ones that are processed.
Page 3 and later are still missing.
If I add them manually to the include section of the plugin, everything works as expected.