Re: WebCat 3.04-3.07 plug-in dying on server....
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 28695
interpreted = N
texte = >>My gut feeling is that you may see >>the same problems even after you replace the plugin with the cgi, >>thus narrowing things down to either a bug in webcat or a coding >>problem in one of your templates > >It's not going to be a coding problem because it's universal- among >15-20 sites with 5 different developers, so none of the code is all >from one shop.If all the sites are on the same server, then it is very possible -- and very likely -- that someone has uploaded a template that is killing webcatalog, and thereby killing every webcat site on the server. The problem wouldn't show up until someone requests that page, and then the bad code kills webcat ... >Too much variety across the sites. I could see one >shop's code breaking because of a consistent coding problem, but the >upgrade breaks every site.One shop's code can *EASILY* break every site! That's one of webcat's major security and stability problems!================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to
Associated Messages, from the most recent to the oldest:
>>My gut feeling is that you may see >>the same problems even after you replace the plugin with the cgi, >>thus narrowing things down to either a bug in webcat or a coding >>problem in one of your templates > >It's not going to be a coding problem because it's universal- among >15-20 sites with 5 different developers, so none of the code is all >from one shop.If all the sites are on the same server, then it is very possible -- and very likely -- that someone has uploaded a template that is killing webcatalog, and thereby killing every webcat site on the server. The problem wouldn't show up until someone requests that page, and then the bad code kills webcat ... >Too much variety across the sites. I could see one >shop's code breaking because of a consistent coding problem, but the >upgrade breaks every site.One shop's code can *EASILY* break every site! That's one of webcat's major security and stability problems!================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to
Kenneth Grome
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:
WebCat b15 Mac plug-in (1997)
generator prob (2001)
Modifying order output (1997)
restart needed???? (1997)
all records returned. (1997)
WebCat cannot handle compatible search parameters? (1997)
PCS Customer submissions ? (1997)
[cart]'s ever get recycled? (2000)
enhanced ErrorMessages.db (2002)
CommandSecurity? (1997)
any limitations on # of users.db entries (1999)
Re:Signal Raised (1997)
Nesting format tags (1997)
2nd WebCatalog2 Feature Request (1996)
Trouble with Netscape (1998)
PCS Frames-Default page is solution! (1997)
Formulas.db + Users.db (1997)
emailer settings and control questions (1997)
Showif, Hideif reverse logic ? (1997)
Field name-subcategory (1997)