I found a bug ...

This WebDNA talk-list message is from

1997

It keeps the original formatting. numero = 12086
interpreted = N
texte = I am running WebCat2 StarNine release 2.0 on a PPC Mac, and I found a bug.Here's the details ...I'm using the standard [date] and [time] tags - without any formatting - toenter those values into the messageDate and messageTime fields of themessages.db whenever someone posts a new message.At the same time, I'm also using a sendmail context on the same template toemail the text of each new message to myself. The [date] and [time] tagsare used in the text portion of the sendmail context so I can see when themessage was posted.Here's what happened - only twice - but it shouldn't have happened at all:When a particular user posted a message, the slashes that *SHOULD HAVE*been placed in the [date] field were replaced by the uppercase letter V... and the colons that *SHOULD HAVE* been placed in the [time] field werereplaced by the lowercase letter a.In other words, 06/16/1997 was entered into the database as 06V16V1997 ...and 14:24:30 was entered as 14a24a30. This screws up the sorting by dateand time, because a message like this always appears as if it were the lastmessage entered ...Please note, this error did NOT happen in the [sendmail] context. I checkedthat mail and the formatting of these values appears the way it should inthe email - so the problem appears to be only in the portion of the WebCat2code that enters these values into the database.This is a bizarre problem because it actually happened twice in a row - butthere was a substantial time lag between the posting of these two messages.The first message with this problem was posted at 09:44:23 and the nextmessage was posted at 10:11:11. There were no other messages posted inbetween these two ... but the same person posted both of these messages,presumeably from the same IP address since they were posted within ahalf-hour of each other.Here's the thing:If I didn't already know that the dates and times entered into themessages.db are done so completely independently of the both the browserand the users's IP address, I would obviously jump to the conclusion thatthis error occured because of a problem on the user's end.However, since the dates and times entered into the messages.db are entereddirectly by WebCatalog 2.0 via an [append] context in my results form, Ifeel almost certain that this problem could *not* have been caused byeither the user's browser or any problems at that person's IP address.The problem happened twice within a half-hour, and it has not happenedsince. I have no idea what this means. If it had happened only once, Iwould be able to chalk it up to a one-time glitch. Unfortunately, ithappened twice, and the occurrences were almost a half-hour apart, which tome seems to rule out the 'one-time glitch' theory.HELP!!! :)Sincerely, Ken GromeWebDNA Solutions Associated Messages, from the most recent to the oldest:

I found a bug ... (Kenneth Grome 1997)

I am running WebCat2 StarNine release 2.0 on a PPC Mac, and I found a bug.Here's the details ...I'm using the standard [date] and [time] tags - without any formatting - toenter those values into the messageDate and messageTime fields of themessages.db whenever someone posts a new message.At the same time, I'm also using a sendmail context on the same template toemail the text of each new message to myself. The [date] and [time] tagsare used in the text portion of the sendmail context so I can see when themessage was posted.Here's what happened - only twice - but it shouldn't have happened at all:When a particular user posted a message, the slashes that *SHOULD HAVE*been placed in the [date] field were replaced by the uppercase letter V... and the colons that *SHOULD HAVE* been placed in the [time] field werereplaced by the lowercase letter a.In other words, 06/16/1997 was entered into the database as 06V16V1997 ...and 14:24:30 was entered as 14a24a30. This screws up the sorting by dateand time, because a message like this always appears as if it were the lastmessage entered ...Please note, this error did NOT happen in the [sendmail] context. I checkedthat mail and the formatting of these values appears the way it should inthe email - so the problem appears to be only in the portion of the WebCat2code that enters these values into the database.This is a bizarre problem because it actually happened twice in a row - butthere was a substantial time lag between the posting of these two messages.The first message with this problem was posted at 09:44:23 and the nextmessage was posted at 10:11:11. There were no other messages posted inbetween these two ... but the same person posted both of these messages,presumeably from the same IP address since they were posted within ahalf-hour of each other.Here's the thing:If I didn't already know that the dates and times entered into themessages.db are done so completely independently of the both the browserand the users's IP address, I would obviously jump to the conclusion thatthis error occured because of a problem on the user's end.However, since the dates and times entered into the messages.db are entereddirectly by WebCatalog 2.0 via an [append] context in my results form, Ifeel almost certain that this problem could *not* have been caused byeither the user's browser or any problems at that person's IP address.The problem happened twice within a half-hour, and it has not happenedsince. I have no idea what this means. If it had happened only once, Iwould be able to chalk it up to a one-time glitch. Unfortunately, ithappened twice, and the occurrences were almost a half-hour apart, which tome seems to rule out the 'one-time glitch' theory.HELP!!! :)Sincerely, Ken GromeWebDNA Solutions Kenneth Grome

DOWNLOAD WEBDNA NOW!

I found a bug ...

1997

Top Articles:

Related Readings: