Last post 1 hour 49 min ago

Posts last week 81

Average response time last week 4 hours 29 min

All time posts 67931

All time tickets 10501

All time avg. posts per day 20

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.

#1146 – Pagination bug

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.

Sunday, 11 October 2015 10:40 UTC

chicagooogle

Hello, to reproduce this bug you need to:
Clear cache and try to add to any of the pagination page some “GET” parameter (any parameter), right into the browser address bar (before page cached). For example. Clear cache and type:
http://www.example.com/lechenie/page-4?lalala=0

This operation will cache the rest pagination pages (include this one – page-4) with “lalala=0” parameter.

Monday, 12 October 2015 08:43 UTC

wb_weeblr

Hi

Not sure I understand. What do you mean by

will cache the rest pagination pages (include this one – page-4) with “lalala=0” parameter

When and where do you use those links?

If I simply type this in a browser address bar, nothing special happens, and the URL is not stored in the database.

Rgds

Monday, 12 October 2015 15:25 UTC

chicagooogle

I mean the rest urls in pagination block (on cached page-4) will be like “…/page-2?lalala=0”, “…/page-3?lalala=0” etc. Page cached and links on the page are wrong.

Page caches any additional get parameter in pagination block for all of the urls in this block. If it is not clear, I can make some screenshots.

>When and where do you use those links?
I don't by the way. I used the old custom pagination module template (now it replaced by a new one form the latest version of joomla) and "start=0" param came up, I don't know why and how. But search engine cached those pagination pages with a wrong parameter and every time when I refresh joomla cache it caches them again with "start=0" param, because he just hitting/crawling old urls from his database. And as a result I have cached pages pagination pages with "start=0" param all over in my pagination block.

As I mention before, if it's not clear I can make couple of screenshoots.

Regards.

Monday, 12 October 2015 15:39 UTC

chicagooogle

Why sh404sef do not manages the additional url parameters? For example: I can add any parameter to the pagination page "example.org/category/page-2?spam=google.com" and put it to some forums etc, search engine will crawl it and voila, now I have a duplicate:

1 example.org/category/page-2 (the real site page)
2 example.org/category/page-2?spam=google.com (duplicate page)

sh404sef is not counting additional get params as an 404 error

Monday, 12 October 2015 17:42 UTC

wb_weeblr

I mean the rest urls in pagination block (on cached page-4) will be like “…/page-2?lalala=0”, “…/page-3?lalala=0” etc. Page cached and links on the page are wrong.

Well yes, if you request a page with additional query string vars, they will passed by Joomla to the paginated links. What does sh404SEF has to do with that?

Page cached and links on the page are wrong.

What do you call "Page cached"?

I don't by the way. I used the old custom pagination module template (now it replaced by a new one form the latest version of joomla) and "start=0" param came up, I don't know why and how

Well updating the pagination module seems to be appropriate.

Why sh404sef do not manages the additional url parameters?

Interesting. How is sh404SEF supposed to know what the good query strings are and what the bad ones are?

sh404SEF doesn't make any decision and does not create any link. It's not involved at all in that. What it does is receives from Joomla a non-sef URL and turns it into a SEF. If a user, or Joomla (or your custom module) inserts bad variables in the non-sef, there's no way for us to tell the good for the bad.
We have strictly no right to remove any part of the incoming URL because this would break many sites and extensions which relies on them.

sh404sef is not counting additional get params as an 404 error

Of course it's not. If the URL is rendered by Joomla then it's absolutely not a 404. That's exactly the role of query vars, and they are used every day like this, for instance with adsense or many affiliates systems.

Rgds

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.