PDA

View Full Version : 4.2.5 broke vBadvanced module


Kirkus
06-12-2017, 01:39 AM
I realize this might not be the right place to post this, but I'm at a loss as I can't get a response from the vBadvanced site as it hasn't been supported for a number of years. I'm hoping some one might be familiar with the vBadvanced CMPS. If I'm out of line posting this on vb.org, please accept my apology and remove the post if necessary. But...

I wonder if anyone can help me fix the Recent Posts module in vBadvanced CMPS.

My vBulletin community uses the Recent Posts module (for about 10 years now) heavily and since the newest version of vBulletin (4.2.5) this module no longer works properly... it doesn't identify and display new posts right. Used to be the thread title would be bold and a go to first new post link would be available if the thread contained new unread posts for the member. That's no longer the case. The bold title and Go to link seem to be random now. The go to first unread post link still seems to work, going to the first unread post, but the indicators seem to be wonky.

vBulletin told me that they removed the option to use cookies for thread marking in the latest update. That thread marking is now done exclusively by the database. Is this what's broken the Latest Topics module? Is the module looking for thread marking in cookies and that info isn't available any longer? (I don't even remember which option, cookie or database, I used before they took this option away.) But would the go to first unread post link work if that were the case?

The module in CMPS is so much better than what's built in to vBulletin, in my opinion.

Any help at all, even just pointing me in the right direction, would be so much appreciated.

Thanks.

--Kirk

PS - Or is anyone aware of an add-on for vBulletin that would do the same thing?

Paul M
06-12-2017, 10:27 AM
I would imagine that the removal of the option has broken it, most likely in the same manner it broke my own unread posts mod. The code likely relies on the option 'threadmarking' existing, which is no longer the case, so it will need to be modified to take any check for that out.

Kirkus
06-13-2017, 11:35 PM
Ah, OK. You think it's the check that might be throwing it off. I think that might be easy enough for me (I know just enough to be dangerous) to find in the code and change.

Is your unread posts mod something from here, Paul? Or is it something you wrote for yourself?

Paul M
06-14-2017, 12:02 AM
Is your unread posts mod something from here, Paul? Or is it something you wrote for yourself?

Both :)

https://vborg.vbsupport.ru/showthread.php?t=231060

Kirkus
06-14-2017, 12:26 AM
Hey! Look at that! LOL.

I know it's no longer supported but I might try it out anyway. You know, since my vBadvanced CMPS thingy is not working.

Paul M
06-14-2017, 09:57 AM
Its still supported while I'm actually around.

Duke49th
05-31-2018, 04:29 PM
Edit:


--------------- Added 1527824932 at 1527824932 ---------------

Ok after I really wanted the solution I figured it out myself. I just checked how forumdisplay.php handles it lol.


In ../modules/recentthreads.php go to the following lines and delete something....change it from

if ($vbulletin->options['threadmarking'] AND $vbulletin->userinfo['userid'])

into

if ($vbulletin->userinfo['userid'])

Do it for Line 151 under // Database read marking and 293 under // Thread read marking

That's all. read post/thread marking works again. yeahhh...:D