Re: Re: Page Navigation Bugs on Label Pages

Sadly Brett, I'm still seeing the exact same navigation bugs so many years 
later. It's not just my blog it's all over blogger. Here's an example:

http://mystady.com/search/label/Changelog

Exactly 20 posts for the entry yet it generates an olderPageUrl that takes 
you to a blank page.

Are there any plans to resolve these?

On Tuesday, June 5, 2012 at 11:18:57 PM UTC-4, Brett Morgan wrote:
>
> Thanks for the heads up Alain-Christian!
>
> On Tue, Jun 5, 2012 at 11:07 PM, Alain-Christian <[email protected] 
> <javascript:>> wrote:
>
>> Um... This navigation bug is more complicated than I first 
>> thought. Apparently *you don't always get 20 posts per page*. This also 
>> means anybody using the workaround I posted for older page links should *revert 
>> back to their old code*. Sorry about that. I only just noticed it this 
>> morning. Bug #4 is the same as it ever was so I would continue using 
>> that workaround. It looks like Bug #3 has been fixed. Bug #2 is still 
>> present.
>>
>> Just when you think we have a handle on these navigation bugs I find a 
>> new wrinkle. I was operating under the assumption that blogger always 
>> generates 20 posts per page but that is not the case. For example this 
>> page only has 13 posts 
>> <http://mystady.com/search/label/Photography?updated-max=2008-03-27T03:30:00-04:00&max-results=20&start=40&by-date=false> 
>> and there's more posts on the following page. That makes the workaround I 
>> posted for Bug #1 unreliable because a page with less than 20 entries 
>> doesn't necessarily mean it's the last page. My apologies for any trouble 
>> this may have caused.
>>
>> On Thursday, September 8, 2011 2:33:45 PM UTC-4, Alain-Christian wrote:
>>>
>>> Background
>>> Entries for Label Pages 
>>> <http://mystady.com/2011/05/7-blogger-page-types-analysis-code.html#label-page-type> 
>>> are listed 20 at a time. The only exception would be the last page of an 
>>> entry which could potentially contain less than 20 entries. So for example 
>>> if you have a label for cooking with 99 entries that equates to five pages 
>>> with the last page having 19 entries.
>>>
>>> Bug #1 – Label Pages with less than 20 entries still generate Older Page 
>>> navigation links.
>>> Logically: if a page has less than 20 entries then obviously there are 
>>> no more entries to list. You're on the last page. Because of this bug the 
>>> last page in our cooking example is still generating Older Page links. And 
>>> when the visitor clicks on it they're taken to a blank page. It even 
>>> happens when the first page IS the last page. For example if label has less 
>>> than 20 entries total.
>>>
>>>
>>>    - *Exception:* When the total number of entries for a label is a 
>>>    multiple of and greater than 20 (40, 60, 80, etc.) the last page will not 
>>>    generate an Older Page link. This is ideal behavior; not a bug.
>>>    
>>>
>>> Bug #2 – Label Pages with exactly 20 entries still generate Older Page 
>>> navigation links.
>>> This is what I meant by 'greater than' in the above exception. If you 
>>> have a label with exactly 20 entries the Older Page link will still be 
>>> generated on what should be the first–*and only*–page. Clicking the 
>>> link takes you to a blank page.
>>>
>>> Bug #3 – Newer Page navigation links are present on the first Label Page.
>>> Not much to explain here. There's nothing newer than the first page, 
>>> right? A newer page link on the first page is unnecessary. Not only that 
>>> but it's confusing to visitors. I'm not a big SEO guy but I'm sure search 
>>> engines hate this too. It just keeps taking you back to the first page. An 
>>> endless loop!
>>>
>>> Bug #4 – *newerPageUrl* only uses the *?max-results=20* query parameter.
>>> Let's go back to the cooking example from the beginning. 99 entries on 
>>> cooking equates to 5 pages, remember? Well that means no matter what page 
>>> you're on the link to newer pages will always be *http://example.com/search/label/cooking 
>>> <http://example.com/search/label/cooking>?max-results=20*. My personal 
>>> theory is that this is a new bug. I think we would have noticed this a long 
>>> time ago if it was always like that.
>>>
>>> Workarounds
>>> I've posted workarounds to all these bugs on my Github page 
>>> <https://github.com/Alain-Christian/MY-STADY-Blogger-Template/commit/350b7d1a6b2b740ba772eb6e393b56394c0ad108>. 
>>> Bug #2 and Bug #3 are annoying because they require an entry for every 
>>> label affected. I don't like the workaround to Bug #3 because it 
>>> requires the use of JavaScript which not everybody uses. Security-minded 
>>> visitors have to vet pages before allowing them to use JavaScript. And I 
>>> hate the idea of my navigation being beholden to Javascript. That's almost 
>>> as bad as pages that use Flash for navigation. Remember when that was 
>>> popular for a while?
>>>
>>> Once again, it might be a while before Blogger addresses these issues. I 
>>> personally think Bug #4 should get the highest priority.
>>>
>>> Links
>>> Once again you can find my bugfixes on Github 
>>> <https://github.com/Alain-Christian/MY-STADY-Blogger-Template/commit/350b7d1a6b2b740ba772eb6e393b56394c0ad108>. 
>>> That also means you can't test these bug out on my site because I've fixed 
>>> them for the most part. Or to be precise, applied band-aids.
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Blogger Developer Group" group.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msg/bloggerdev/-/e0bEFAuCjZAJ.
>>
>> To post to this group, send email to [email protected] 
>> <javascript:>.
>> To unsubscribe from this group, send email to 
>> [email protected] <javascript:>.
>> For more options, visit this group at 
>> http://groups.google.com/group/bloggerdev?hl=en.
>>
>
>
>
> -- 
>
> Brett Morgan
>
> Developer Relations Engineer, Blogger
>
>

-- 
You received this message because you are subscribed to the Google Groups "Blogger Developer Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/bloggerdev.
For more options, visit https://groups.google.com/d/optout.