Re: ReadDateFormat bug in 3.x

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 22034
interpreted = N
texte = Helene:If you haven't already received this information, here's what I think is happening - Your WebCatalog admin pages were not updated with the recent releases of 3.0. The first release of 3.0 inserted an improper value for the ReadDateFormat. The proper values should be mdy or dmy (case sensitive). The newer admin pages with 3.01 and greater insert the proper preference value. Deleting the preference altogether fixed things because it defaulted to mdy in that case.John.>>>Is there any *requirement* to leave the ReadDateFormat preference in the >>>WebCatalog Prefs file? I want to leave it out, because it fixes the bug >>>... >>> >>>What kinds of things might get screwed up by leaving it out? >>>Anything? >> >>OK, first off we're not convinced there's a bug in WebCatalog itself. >>There was a template typo in the original 3.0.0 release that made >>ReadDateFormat = mdy instead of MDY. This causes many of the symptoms you >>mention, and has been fixed in the *admin templates* of 3.0.2 (mentioned in >>the Change History) > >I can't find the 3.02 templates on your server. John A. Hill Pacific Coast Software eCommerce / Web Developer Tools http://www.smithmicro.com Associated Messages, from the most recent to the oldest:

    
  1. Re: ReadDateFormat bug in 3.x (John Hill 1998)
  2. Re: ReadDateFormat bug in 3.x (Kenneth Grome 1998)
  3. Re: ReadDateFormat bug in 3.x (Kenneth Grome 1998)
  4. Re: ReadDateFormat bug in 3.x (PCS Technical Support 1998)
  5. Re: ReadDateFormat bug in 3.x (helene 1998)
  6. Re: ReadDateFormat bug in 3.x (PCS Technical Support 1998)
  7. ReadDateFormat bug in 3.x (Kenneth Grome 1998)
Helene:If you haven't already received this information, here's what I think is happening - Your WebCatalog admin pages were not updated with the recent releases of 3.0. The first release of 3.0 inserted an improper value for the ReadDateFormat. The proper values should be mdy or dmy (case sensitive). The newer admin pages with 3.01 and greater insert the proper preference value. Deleting the preference altogether fixed things because it defaulted to mdy in that case.John.>>>Is there any *requirement* to leave the ReadDateFormat preference in the >>>WebCatalog Prefs file? I want to leave it out, because it fixes the bug >>>... >>> >>>What kinds of things might get screwed up by leaving it out? >>>Anything? >> >>OK, first off we're not convinced there's a bug in WebCatalog itself. >>There was a template typo in the original 3.0.0 release that made >>ReadDateFormat = mdy instead of MDY. This causes many of the symptoms you >>mention, and has been fixed in the *admin templates* of 3.0.2 (mentioned in >>the Change History) > >I can't find the 3.02 templates on your server. John A. Hill Pacific Coast Software eCommerce / Web Developer Tools http://www.smithmicro.com John Hill

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

syntax question, not in online refernce (1997) WebCatalog can't find database (1997) WebCat2 Append problem (B14Macacgi) (1997) mass mailing (1998) unable to launch acgi in WebCat (1997) Web Catalog 2 demo (1997) [WebDNA] Libmysql.dll error (2009) More than one db with the same namn (was: WC2f3) (1997) Search/sort in URL Was: GuestBook example (1997) Realtor Search (2000) Showif -what am I missing??? (1999) PROBLEM (1997) Access Denied! But why? (1997) For those of you not on the WebCatalog Beta... (1997) [include ...] behavior (1997) 2nd WebCatalog2 Feature Request (1996) writefile - continued (1997) [WebDNA] Initial setup problems with 6.2 (2009) WC Database Format (1997) Req: Array Tags Explained, simple and clear (2003)