Last post 56 min ago

Posts last week 89

Average response time last week 30 min

All time posts 67719

All time tickets 10464

All time avg. posts per day 21

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.

Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!

All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#5914 – purging urls to correct pagination issue

Posted in ‘sh404SEF’

This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Thursday, 25 July 2019 18:29 UTC

joec-siteintelgroup-com

Hello,

I wrote about this issue in a previous ticket a couple years ago: #4034

At the time, purging the urls fixed the problem, and it still does.

But I find that after a period of time, a client will email saying the pagination is broken and I'll have to purge them over again.

Is the addition of new articles over time breaking the pagination again?

And how do I solve this issue without having to periodically purge the Page* urls?

Thanks

Friday, 26 July 2019 12:26 UTC

wb_weeblr

Hi,

Hard to tell really unless we understand what causes the problem. It would also help to specify what "broken" means exactly.

Is the addition of new articles over time breaking the pagination again?

Not on the few hundreds thousands web sites that run sh404SEF :)

And how do I solve this issue without having to periodically purge the Page* urls?

The only thing I have seen in the past that would "break" pagination are:

- using components or template that have their own Pagination class. Nothing can be done against that, it's just not possible. However it's a/pretty rare and b/ pagination would never work, the URLs would be off and the correct page would never show. That does not seem to apply to your case

- Changing the default number of items per page, either globally or otherwise. If such a change is done by the site admin, then all URLs with pagination should be deleted so that new ones, taking into account the new default # of items per page can be created. Purging is one way of achieving this.

If the latters is something that may happen, a safeguard is to enable "Always append #items per page" under the "Main" tab of sh404SEF configuration - then purge URLs. Paginated URLs will change, they will become something like: site.com/blog/page-2-10 instead of site.com/blog/page-2.
If the default page number is changed to 20, then another URL will be created for page 2: site.com/blog/page-2-20. The previous URL site.com/blog/page-2-10, will still be in the database and that's perfectly fine, very desirable actually in case search engines indexed that page or at least crawl it.

Best regards

Saturday, 10 August 2019 05:34 UTC

system

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.