This is a discussion on Goto First Unread Post within the Troubleshooting forums, part of the vBSEO SEO Plugin category; Originally Posted by COBRAws I want to state that my ticket created 11-16-2007, 04:13 PM has yet not been updated ...
Wow....I can't believe the poor support of this site. Even with a support ticket in from someone in this thread. My first post is over 24 hours ago. They should have a staff person on duty just for these reasons. Hope we get our problem resolved soon.......:(
Please remember, it is a weekend. Oleg is looking into the issue. If it is causing major problems, you can always revert back to vBSEO 3.0.0 until the issue is resolved.
my question is why isn't more people having issues with it?
No one on the pre-release team had this issue, and it only appears to be a small number of people for some reason. That's why Oleg is looking into it.
Update: the following modification in vbseo.php resolved the isue:
this code:
REPLACED WITH:PHP Code:vbseo_set_self($q = 'showthread.' . VBSEO_VB_EXT . '?' . VBSEO_THREADID_URI . '=' . $arr['thread_id'] . '&goto=' . (isset($arr2) ? 'lastpost' : 'newpost'));
Thank-you all for reporting!PHP Code:vbseo_set_self($q = 'showthread.' . VBSEO_VB_EXT . '?' . VBSEO_THREADID_URI . '=' . $vbseo_arr['thread_id'] . '&goto=' . (isset($vbseo_arr2) ? 'lastpost' : 'newpost'));
Oleg Ignatiuk / Crawlability Inc.
Security vbulletin - Patch Level for all supported versions released!
Unveiling the NEW vBSEO Sitemap Generator 3.0. - available NOW for vBSEO Customers!
Yep fixed and flying now. (touch wood) ty oleg.
I was having the problem, but just now discovered it. Thanks for the fix. I suggest sending out a notice and a patch download to all vbSEO users.
We've downloaded latest version yesterday and in our upgrade today, we had the same issue which caused us a lot of trouble and time commitment. We finally fix it with the instructions mentioned here. Wouldn't be nice if you updated the scripts in the download area with this fix?
Fixed!
If its not a problem for everyone, they can't include the fix![]()