[jmwking]

I'll pull this out and make a new thread.

Originally Posted by jmwking

I manage a vBul board as well, and I've been in touch with WiForums about this issue (it's a deal breaker for me). I got this reply:

"I finally had some time to look into the issue by further examining the vB database schema, and the issue that you brought to my attention is present when database thread read marking is being used, and is due to WiForums not updating the "threadread" table.

I will look into correcting this issue in an upcoming update."

I've asked them to let me know when they issue that update, and I'll pass on any info I get from them.

-jk

I just got this from them:

The conclusion that I came to last week after looking at the vB database schema was incorrect.

The issue that you brought to my attention is caused when database marking of forum and topic reads is NOT being used. The issue can only be re-created when cookie/session tracking for forum reads is enabled, so it will not impact your forum, though I gather that most forums use cookie/session thread marking.

WiForums updates a user's last visit timestamp in the database when they log in wirelessly. When the same user logs in via the vB forum at a later date vB appears to scrap the thread reads tracking that was stored in a cookie because of the differing last visit timestamps between the database and cookie.

So, if BBF sets

vBulletin Options > General Settings > Thread/Forum Read Marking Type, select "Database (no automatic forum marking)"

the WiForums WAP engine should not mark everything as read when you log in.

Can this be changed so WAP doesn't screw everything up? I know I'd certainly appreciate it!

-jk

[JSanders]

Thanks, I will ask Tom to look into this.

[JSanders]

Looks to be fixed now... Tom flipped the switch. I just tested and seems good. Please verify on your end.

And thanks!

[John Clark]

Wow!!! I've hated that for ages!!!! Nice work!!!

[jmwking]

Thanks! Working much better...

-jk

[juwaack68]

Very nice update, thanks for suggesting it!

[jsconyers]

Any correlation between this change and http://www.blackberryforums.com/site...s-changes.html?

[JSanders]

I think they are all tied together. My guess.

[Tom]

Yes, they are.

[JSanders]

My opinion, liking the fix to the WAP site marking all threads read, let's give this a week or two and see how it sorts out before reverting any changes.

[jsconyers]

Thanks for the clarification, Tom.

JSanders, I agree. Let's give it time to see how everyone responds to the changes. It just caught me off guard at first. I am sure I will get used to it. Change is good sometimes

[jmwking]

Just got this from WiForums, with even better honoring of thread read marks.

v3.9.4 has been released.


It features:

- Interoperability with vB's database thread read marking.

On thread listing pages, threads that a user has not read or those which contain new posts are displayed in bold font. Thread read timestamps are also updated when the last page of a thread has been viewed.

*WiForums cannot implement the above features if vB's "Inactivity/Cookie Based" thread marking is used.


- The layout of the XHTML-MP menu options and some of their corresponding access keys have been modified.

Pushing '*' on your keypad now jumps to the menu
Pushing '#' on your keypad now jumps to the top of a page


- Session based user 'Tips' are no longer displayed to guests.