There are many entries in my Members table that show members who have a M_LASTHEREDATE many dayes earlier than M_LASTPOSTDATE. Thus, for example, a member can be shown as having last visited on February 3rd while his last post date is shown to be February 21st.
This is the result of allowing non-registered guests access to the forums. THAT is not a problen, but allowing them to post a new topic or reply to existing one is. I know, 'that can't happen', but it does. The guest is given the opportunity to specify a username and a password in the post window and so long as those are valid their post is recorded (and their M_LASTPOSTDATE is properly updated.) What is NOT done, however, is an update of the M_LASTHEREDATE.
That can be easily repaired by changing post_info.asp at about line # 68.
Replace the exisiting line:
if mLev = 0 then mLev = cLng(chkUser(strDBNTUserName, strPassword,-1))
with:
if mLev = 0 then
mLev = cLng(chkUser(strDBNTUserName, strPassword,-1))
if mlev >0 then UpdateLastHereDate DateToStr(strForumTimeAdjust),strDBNTUserName
end if
Now there remains some questions:
1) Why is a guest presented with the 'New Topic' option at all?
2) Should the guest become a logged-in user as a result of presenting valid credentials when posting a topic or reply via post_info.asp?
3) Should DoCookies be called at the time M_LASTPOSTDATE is updated?
Thanks for any response here.
Topic Locked
Posted - 23 February 2004 : 11:46:55
