Re: Bad creator codes which cause access denied errormessage

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 14787
interpreted = N
texte = >Now my problem is that when I >go to catalogadmin.tmpl in my browser and make changes over the web, the >edited files override the BBEdit format and are automatically saved as >(in this case) WebSTAR/SSL 2.1 documents whose creator code is >corrupted in the same way. Ken, Paul, or whoever; any thoughts on this >one? Being able to edit over the web is crucial. > >Thanks, again. I'm sure you all know how awesome it feels when someone >gives you a solution, you try it, and bingo!, it works! YES!! Hi John,There's no corruption going on with your creator codes. What you're seeing is WebCatalog's automatic security features being put into action when you use the [writefile] context that's in your catalogadmin.tmpl file.The WebCatalog HTML docs explain exactly what's happening to you. In other words, it's in the manual! Please review the WebCatalog HTML docs under contexts:[writefile] for a complete explanation of how to resolve your problem.In the meantime, here's my quick and dirty explanation:Apparently you're using [writefile] without setting the secure=F >parameter. If you don't set the secure=F parameter in the [writefile] context, WebCat (and Typhoon) assumes that you want the file to be secured, so it sets the Creator code to WWW‡ instead of ttxt. That prevents WebSTAR from serving the file.In other words, if you're going to use the [writefile] context on files you intend to let WebSTAR serve for you, then you have to use the proper syntax in your [writefile] stuff:[writefile file=path/to/file.html&secure=F]Again, this is explained in easy-to-understand detail in the HTML docs. There's also a WebDNA-Talk list (and a Typhoon-Talk list) where I'll be glad to help you some more if you have additional WebCat or Typhoon questions ... :)Sincerely, Ken Grome WebDNA Solutions http://www.smithmicro.com/webdnasolutions/. Associated Messages, from the most recent to the oldest:

    
  1. Re: Bad creator codes which cause access denied errormessage (Kenneth Grome 1997)
  2. Re: Bad creator codes which cause access denied errormessage (Kenneth Grome 1997)
>Now my problem is that when I >go to catalogadmin.tmpl in my browser and make changes over the web, the >edited files override the BBEdit format and are automatically saved as >(in this case) WebSTAR/SSL 2.1 documents whose creator code is >corrupted in the same way. Ken, Paul, or whoever; any thoughts on this >one? Being able to edit over the web is crucial. > >Thanks, again. I'm sure you all know how awesome it feels when someone >gives you a solution, you try it, and bingo!, it works! YES!! Hi John,There's no corruption going on with your creator codes. What you're seeing is WebCatalog's automatic security features being put into action when you use the [writefile] context that's in your catalogadmin.tmpl file.The WebCatalog HTML docs explain exactly what's happening to you. In other words, it's in the manual! Please review the WebCatalog HTML docs under contexts:[writefile] for a complete explanation of how to resolve your problem.In the meantime, here's my quick and dirty explanation:Apparently you're using [writefile] without setting the secure=F >parameter. If you don't set the secure=F parameter in the [writefile] context, WebCat (and Typhoon) assumes that you want the file to be secured, so it sets the Creator code to WWW‡ instead of ttxt. That prevents WebSTAR from serving the file.In other words, if you're going to use the [writefile] context on files you intend to let WebSTAR serve for you, then you have to use the proper syntax in your [writefile] stuff:[writefile file=path/to/file.html&secure=F]Again, this is explained in easy-to-understand detail in the HTML docs. There's also a WebDNA-Talk List (and a Typhoon-Talk List) where I'll be glad to help you some more if you have additional WebCat or Typhoon questions ... :)Sincerely, Ken Grome WebDNA Solutions http://www.smithmicro.com/webdnasolutions/. 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:

Help! WebCat2 bug (Ben's input) (1997) RE: AccountAuthorizer doesn't seem to work (1997) Db design question (relational vs. flat?) (1998) [BULK] Fwd: [WebDNA] [BULK] WebDNA discovery in the Console - [having many crashes] (2011) RAM variables (1997) WCS Newbie question (1997) Mac & Internet Explorer, and # of orders/traffic (2000) problems with 2 tags (1997) Emailer (1997) Writefile problem (1999) NT vs Mac (1997) [isfile] ? (1997) SSL and WebCatalog (1997) list cookies and list http headers (1997) selecting multiple found items (1997) Next X hits (1996) Re:Variable Math (1998) WebDNA maxing out processor (2008) WebCat2b15MacPlugin - [protect] (1997) $Replace with [founditems] (1997)