@fxstein:

I don't know how to download the complete nightly build but I managed to download the latest versions of the files you mentioned earlier (like listcat, showcat etc).

I did a small test to look at the url's and it looks better indeed. However, could you please check on the links that are created for pages in flat-view with a pagenumber > 1. The links for 'begin', 'previous' (on page 2) and pagenumber '1' end with '/limit,x/limitstart,0/' which will result in duplicate links. The category number follows the id number for these links as well.

Ofcourse I could be wrong because I did not try the full nightly build but if you could check that would be nice.

I saw that the links from flat view to threaded view vv are still nofollowed. Are you sure this will stop Google to index the threaded pages if the default is flat view?

Thanks,

Rickert

Here is the link to find the latest nightly builds:

joomlacode.org/gf/project/fireboard/frs/

The page links MUST have the limit-start format and so should all other links except for the very first post of a thread. It was not like that before and that cause for huge amounts of URLs pointing to the very same content - not something google & Co like.

@fxstein:

Maybe I misunderstand but

www.bestofjoomla.com/component/option,co...ew/id,36033/catid,3/ (this url of this post is found f.e. in the recent discussions tab and most other places)

and

www.bestofjoomla.com/component/option,co...mit,10/limitstart,0/ (this url is found on page 2 of this post)

represent the same content in my opnion. Why does the pagelink to the first post of a thread have a limit-start format (with limit-start equal to 0)?

Rickert

rickert wrote:
@fxstein:

Maybe I misunderstand but

www.bestofjoomla.com/component/option,co...iew/catid,3/id,53648 (this url is found f.e. in the recent discussions tab and most other places)

and

www.bestofjoomla.com/component/option,co...mit,10/limitstart,0/ (this url is found on page 2 of this post)

represent the same content in my opnion. Why does the pagelink to the first post of a thread have a limit-start format (with limit-start equal to 0)?

Rickert

I am not in charge of BOJ. I only contribute to the code line of FB. The latest builds of FireBoard are ahead of BOJ. BOJ does not have the mentioned SEO optimization in place. The correct format for content on multi page threads is the second one with limit and limitstart. Tools like sh404SEF will convert this to URLs with the ending -PageX

Here is an example of a long multi page thread on my site that has pretty much the latest SEO optimization in place:
www.starvmax.com/Forum/General-VMax-Disc...ne/Page-36.html#7210

Yes but now sh404SEF solves the duplication problem. Indeed urls that end with limit-start equal to 0 are rewritten by sh404SEF to urls WITHOUT a '/Page-1.html' extension, which would otherwise be urls that would introduce duplicate content.

If you deactivate sh404SEF for a moment you will see my point.

Example:

Code:

http://www.domainname.com/component/option,com_fireboard/Itemid,38/func,view/catid,9/id,155/

and

Code:

http://www.domainname.com/component/option,com_fireboard/Itemid,38/func,view/id,155/catid,9/limit,6/limitstart,0/

(in links on subsequent pages > 1)

Both urls are rewritten by sh404SEF to

Code:

http://www.domainname/descriptionforumcategory/155-descriptionsubject.html

For FB without sh404SEF the problem still exists and my point is that urls that end with limit-start equal to 0 should not exist (or the first url from the example should have a limit-start equal to 0 as well).

By the way: I know that FB is ahead of BOJ, I tried to make an example .. which was not to clear I admit.

Rickert

I am not sure I understand.

The lastest nightly build do not create limitstart =0

Here is the code from the class that generates the links:

Code:

function GetThreadPageLink($func, $catid, $threadid, $page, $limit, $name, $anker='', $rel='follow', $class='')     {         if ($page == 1 || !is_numeric($page) || !is_numeric($limit))         {             // page 1 is identical to a link to the top of the thread             $pagelink  = fb_link::GetSefHrefLink(JB_LIVEURLREL.'&func='.$func.'&catid='.$catid.'&id='.$threadid                           .($anker?('#'.$anker):''), $name, $rel, $class);         }         else         {             $pagelink  = fb_link::GetSefHrefLink(JB_LIVEURLREL.'&func='.$func.'&catid='.$catid.'&id='.$threadid                           .'&limit='.$limit.'&limitstart='.(($page-1)*$limit).($anker?('#'.$anker):''), $name, $rel, $class);         }         return $pagelink;     }

As you can see for page=1 it generates a link without any limit and limitstart parameter. Only for pages other than 1 that info gets created.

The code you showed me is the same I use. Nevertheless, I made a fresh install of the latest nightly build to test the urls but too many bugs/problems. I think I give up for now and wait for 1.05 production to show up.

Thanks for your help.

Rickert

I figured out that (in the latest version of view.php) GetThreadPageLink is NOT called to create the page navigation links on the top and bottom of the page. In stead Joomla's writepageslinks is called. This causes the limitstart,0 to be included (f.e. on page 2) in the url's and causes url's with duplicate content.

Rickert

By the way: I saw that the links from flat view to threaded view vv are still nofollowed. Are you sure this will stop Google to index the threaded pages if the default is flat view?

rickert wrote:
I figured out that (in the latest version of view.php) GetThreadPageLink is NOT called to create the page navigation links on the top and bottom of the page. In stead Joomla's writepageslinks is called. This causes the limitstart,0 to be included (f.e. on page 2) in the url's and causes url's with duplicate content.

Rickert

By the way: I saw that the links from flat view to threaded view vv are still nofollowed. Are you sure this will stop Google to index the threaded pages if the default is flat view?

Oh - I see. I must have missed them. I was searching for hrefs in the code, skipped these two. Need to look into this as soon as I have the upgrade process taken care of.