|
While that is a useful method for removing the Unread tally when messages have piled up, it doesn't cover the main issue, which is messages not being noted as read in the first place. Having not delved into the mechanics of vB, it still does seem like an addition of a bool assignment line item would solve this. It would also stop the same pop-ups occurring multiple times.
|
Even if "a bool assignment line item" made sense, it's not as simple as just writing an if statement.
Someone would need to:
- Add a user setting for this. No idea how complicated this is in vBulliten or how often this is done, so it could be anywhere from incredibly easy to a bunch of work (to figure out how this is done, do that, and then figure out what inevitably went wrong along the way)
- Find where in vBulliten the decision is made to see if there are new unread messages when generating a page.
- Read and understand that code.
- Determine if, at that particular point in the code, the necessary variables for accessing the user preferences system have already been set up, and if not, set them up.
- Access the user preference system and check the setting.
- Debug a bunch.
I know nothing about vBulletin either, but I am professional software engineer. When you're working on any large codebase, the hard part is not knowing what line of code to write, but knowing where to put it. And figuring that out can take ages.
Most amazing jew boots
85242
35212
Similar Threads
ramoth