Problem with: Go to last Post and why did he loads showthread.php two times?

You can also reconstruct this error on this site.
To better understand and see the problem, go to
http://www.vbseo.com/usercp/editoptions/
and set for
"Thread Display Mode" the value "Newest First"
(it also works with "Oldest First", but then you need to remenber, which was the last page, you read and if there comes no page after your last page, you need to find a thread, where comes a page after yor last page and this is very boring)

Than go to
http://www.vbseo.com/forums/

And klick on any , where the thread has more than one page and your last seen post ist not on the first page

So try for example
vBulletin 3.7.2 Released - Page 2 - vBulletin SEO Forums

If you already read this thread, it should send you now to something like
vBulletin 3.7.2 Released
but what happend is, that it send you to (or something else, if the thread changes)
vBulletin 3.7.2 Released

As far as i can say, it appear, that wenn i go to
vBulletin 3.7.2 Released - Page 2 - vBulletin SEO Forums

he loads the showthread.php two times.
The first time, he knows the right pagenumber and the secondtime, he did not.

If you look into the vB code and analys the problem, you will see, that when he calculate $vbulletin->GPC['pagenumber'] the first time, he set
$postorder = DESC an has an $postinfo[dateline] set.
At the second time, he also set $postorder = DESC, but know he has no value for $postinfo[dateline]

So he thinks, that all postings are new and calculate a most totally wrong pagenumber.

And if you look closer yu will see, that there is no $_GET['postid'] at the second time.

Please try to modify functions_vbseo_createurl.php file:
FIND:

PHP Code:

if (($bbuserinfo['postorder'] == 1) && !$pinfo['prepostsproc'] && isset($pinfo['preposts']) )
{   
$pinfo['preposts'] = $totr - $pinfo['preposts'] + 2;
} 


and move it a few lines lower, so that it appear right ABOVE this line:

PHP Code:

if (isset($pinfo['preposts']) && $page == 1 && !$gotopost) 


Thanks for the fast Support, works fine for me

You are welcome!

is this a bug fix that everyone should include?

Yes.

Sorry, i just see, that it works now correct for



but i still have the same problem using



So if i want to go to the last unread post, it is perfect, but if i want to go to the last post, he always send me to the last page and ignore the postorder "Newest First", where the last post should be on the first page.

When i think more generell about this, i came up with a new problem, but i think this should be an vBulletin problem:
I think it is difficult, if you want to share links between someone with "Newest First" and "Oldest First", because if you send an Link whitout an postid and only threadid + pagenumber both Users will see other Sites.
So you can't say "Hey dude, look at page 11, awesome posting", or "the solution to your request should be in this thread(whitout postid, only threadid + pagenumber)", when you are not sure, that every user use the same sort rule for postings.

So if i want to go to the last unread post, it is perfect, but if i want to go to the last post, he always send me to the last page and ignore the postorder "Newest First", where the last post should be on the first page.

Can you provide an example URL and testing account in support ticket to check that? It works fine for me.

I go to http://www.vbseo.com/usercp/editoptions/ and use "Newest First" and than i go to
Announcements & Pre-Sales - vBSEO Announcements at vBSEO.com

And than i look for example at "Sticky: vBSEO 3.2.0 Gold Released!"

Then the icon has the link vBSEO 3.2.0 Gold Released!

But it should be
vBSEO 3.2.0 Gold Released!

Because i set "Newest First" and so the last post must be on the first page.
But in fact, everytime i see the link for the last page.

Does that happen on your forum as well? (we do not have the fix mentioned above applied here on vbseo.com yet)

Yes, you can see the Problem at our Forum as well.
United-Forum

Can you provide an example URL and testing account in support ticket?

Sure, there should be an support ticket now.

Was this fix included in 3.2 Gold?