When using the search form in articulate and getting a list of results that trigger pagination, it will cause a page not found error when clicking the pager buttons.
The easiest way to see this is to create a blog, add three posts, set your page size to 1 in the back office, navigate to the blog, click the pager button for older posts, recieve the following error:
Page not found
No umbraco document matches the url '/blogs/search?term=test&p=2'.
This page can be replaced with a custom 404. Check the documentation for "custom 404".
This page is intentionally left ugly ;-)
Has anyone else run into this error and found a way to fix it?
I think that you should add the issue on the Articulate issues on github https://github.com/Shandem/Articulate/issues, so Shannon has the issues collected in one place, I have tried to do the same as you describe in your post, at get same result, as you.
Articulate Pager and Search Results
Hello,
When using the search form in articulate and getting a list of results that trigger pagination, it will cause a page not found error when clicking the pager buttons.
The easiest way to see this is to create a blog, add three posts, set your page size to 1 in the back office, navigate to the blog, click the pager button for older posts, recieve the following error:
Page not found
No umbraco document matches the url '/blogs/search?term=test&p=2'.
This page can be replaced with a custom 404. Check the documentation for "custom 404".
This page is intentionally left ugly ;-)
Has anyone else run into this error and found a way to fix it?
Hi Brian,
I think that you should add the issue on the Articulate issues on github https://github.com/Shandem/Articulate/issues, so Shannon has the issues collected in one place, I have tried to do the same as you describe in your post, at get same result, as you.
I can also see there is already a issue on the pager url https://github.com/Shandem/Articulate/issues/30
/Dennis
Thanks Demmis, will do.
hi any answer for this , i am also getting the same error
is working on a reply...