Hi aviboy2006,
Thanks, there’s a bug there. I’ll try to get this fixed in the next version.
Scott
Hi.
I had a similar problem on one of my website, but I can confirm that pagination works with Simply Static. aviboy2006, believe me, you should investigate on your website, there’s a “broken” link or ressource somewhere in your website making that page generated ;).
PS. I had a look to your website and the dynamic content you have, is not adapted to static content ;)…
Amicably,
Pierre.
Story time.
WordPress has a feature whereby it automatically redirects URLs without a file extension and without a trailing slash to a URL with a trailing slash.
For example, WordPress would redirect http://www.example.org/blog/page/2 (no trailing slash) to http://www.example.org/blog/page/2/ (trailing slash).
Simply Static normally picks up on redirects and creates a redirect html page. However, in the case of WordPress’s no-trailing-slash to trailing-slash redirect, Simply Static makes an exception, since those URLs are effectively equivalent. If the page that WordPress is redirecting to is the same except for a trailing slash, then Simply Static ignores the redirect.
In the case of aviboy2006’s site the redirect is coming across as just a path — /blog/page/2/. Simply Static is trying to compare that to the full URL of the page — http://www.example.org/blog/page/2 — and is determining that those aren’t equivalent. Simply Static should convert the redirect URL to an absolute URL before doing the comparison.
That’s the bug. You could say that the theme should be fixed so that the URLs have trailing slashes, but I prefer to think that Simply Static should be intelligent enough to accept and understand WordPress’ quirks and work around them.
Thanks for commenting Pierre (as always)! 🙂
Hi aviboy2006,
I wasn’t having much luck recreating the issue locally, but nonetheless I believe I’ve got a fix for you in v1.7.1. Give it a try and let me know if it works.
Best,
Scott
i downloaded new version 2.0.1 but still same issue.
http://localhost/knab-cms/knowledge-centre/page/2
http://localhost/knab-cms/knowledge-centre
causing same issue still in new version