Re: [WebDNA] Putting '&search' into URL killing all search contexts on my sites

This WebDNA talk-list message is from

2010


It keeps the original formatting.
numero = 105361
interpreted = N
texte = > Chris, > I just don't believe that there is no easy fix other than getting > rid of URL'ed Commmands. That is difficult to sell to a list full of > programmers/scripters. > > Also, I think it's very important to be clear here that this fastCGI > app is not a patch for existing installations (Which use the native > API for apache on the *nix side). > > The fastCGI product will not have commerce tags (so no > SiteBuilder sites will work), will have a different lic. system > entirely, and will not have sandboxes or "Globals" (so sites that > utilize sandbox code or the globals directory will have to be > tweaked/recoded in order to work with this fastCGI product). > > I personally think a rebuild of the Native API app, with the recent > feature additions and bug fixes should accompany the > fastCGI product. > > Donovan I agree with Donovan. It's not a matter of any insensitivity to WSC's position.. but just a matter of so much legacy code. I do not write C++ or whatever webdna is written in, but it must be doable to duplicate the existing [formvariables] code (which loops through all formvars) and if any formvar is in a blacklist (xxx,yyy,zzz..) (the names of the webdna contexts) ... then remove it from the array of formvars, before sending them on to the page (resuming where we were before this new block of C++). On the other hand, I know how it can get, and maybe it is a real nightmare in there.. ;-) ...but certainly less of a nightmare than all the hundreds/thousands of legacy webdna sites we are talking about. Anyway, meanwhile thanks to Brain and Olin for the simple hack-fix! ------------ Govinda govinda.webdnatalk@gmail.com Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Putting '&search' into URL killing all search contexts on my sites ("Mr. Robert Minor Jr." 2010)
  2. Re: [WebDNA] Putting '&search' into URL killing all search (Alex McCombie 2010)
  3. Re: [WebDNA] Putting '&search' into URL killing all search contexts on my sites (Govinda 2010)
  4. Re: [WebDNA] Putting '&search' into URL killing all search contexts (Donovan Brooke 2010)
  5. Re: [WebDNA] Putting '&search' into URL killing all search contexts (Donovan Brooke 2010)
  6. Re: [WebDNA] Putting '&search' into URL killing all search contexts on my sites (Govinda 2010)
  7. Re: [WebDNA] Putting '&search' into URL killing all search contexts on my sites (christophe.billiottet@webdna.us 2010)
  8. Re: [WebDNA] Putting '&search' into URL killing all search contexts (Donovan Brooke 2010)
  9. Re: [WebDNA] Putting '&search' into URL killing all search contexts on my sites (christophe.billiottet@webdna.us 2010)
  10. Re: [WebDNA] Putting '&search' into URL killing all search contexts (Marc Thompson 2010)
  11. Re: [WebDNA] Putting '&search' into URL killing all search contexts on my sites (Govinda 2010)
  12. Re: [WebDNA] Putting '&search' into URL killing all search contexts on my sites (christophe.billiottet@webdna.us 2010)
  13. Re: [WebDNA] Putting '&search' into URL killing all search contexts (Tom Duke 2010)
  14. Re: [WebDNA] Putting '&search' into URL killing all search contexts on my sites (Brian Fries 2010)
  15. Re: [WebDNA] Putting '&search' into URL killing all search contexts on my sites (Govinda 2010)
  16. Re: [WebDNA] Putting '&search' into URL killing all search contexts on my sites (Kenneth Grome 2010)
  17. Re: [WebDNA] Putting '&search' into URL killing all search contexts on my sites (Govinda 2010)
  18. Re: [WebDNA] Putting '&search' into URL killing all search contexts (Tom Duke 2010)
  19. Re: [WebDNA] Putting '&search' into URL killing all search contexts (Donovan Brooke 2010)
  20. Re: [WebDNA] Putting '&search' into URL killing all search contexts (Tom Duke 2010)
  21. Re: [WebDNA] Putting '&search' into URL killing all search contexts on my sites ("Mr. Robert Minor Jr." 2010)
  22. Re: [WebDNA] Putting '&search' into URL killing all search contexts (Donovan Brooke 2010)
  23. Re: [WebDNA] Putting '&search' into URL killing all search contexts (Tom Duke 2010)
  24. Re: [WebDNA] Putting '&search' into URL killing all search contexts on my sites (Brian Fries 2010)
  25. Re: [WebDNA] Putting '&search' into URL killing all search contexts (Tom Duke 2010)
  26. Re: [WebDNA] Putting '&search' into URL killing all search contexts on my sites (Kenneth Grome 2010)
  27. RE: [WebDNA] Putting '&search' into URL killing all search contexts on my sites ("Olin Lagon" 2010)
  28. Re: [WebDNA] Putting '&search' into URL killing all search contexts on my sites (christophe.billiottet@webdna.us 2010)
  29. Re: [WebDNA] Putting '&search' into URL killing all search contexts on my sites (Stuart Tremain 2010)
  30. Re: [WebDNA] Putting '&search' into URL killing all search contexts (Donovan Brooke 2010)
  31. Re: [WebDNA] Putting '&search' into URL killing all search contexts on my sites (Stuart Tremain 2010)
  32. Re: [WebDNA] Putting '&search' into URL killing all search contexts (Tom Duke 2010)
  33. Re: [WebDNA] Putting '&search' into URL killing all search contexts on my sites (christophe.billiottet@webdna.us 2010)
  34. [WebDNA] Putting '&search' into URL killing all search contexts on my sites (Tom Duke 2010)
> Chris, > I just don't believe that there is no easy fix other than getting > rid of URL'ed Commmands. That is difficult to sell to a list full of > programmers/scripters. > > Also, I think it's very important to be clear here that this fastCGI > app is not a patch for existing installations (Which use the native > API for apache on the *nix side). > > The fastCGI product will not have commerce tags (so no > SiteBuilder sites will work), will have a different lic. system > entirely, and will not have sandboxes or "Globals" (so sites that > utilize sandbox code or the globals directory will have to be > tweaked/recoded in order to work with this fastCGI product). > > I personally think a rebuild of the Native API app, with the recent > feature additions and bug fixes should accompany the > fastCGI product. > > Donovan I agree with Donovan. It's not a matter of any insensitivity to WSC's position.. but just a matter of so much legacy code. I do not write C++ or whatever webdna is written in, but it must be doable to duplicate the existing [formvariables] code (which loops through all formvars) and if any formvar is in a blacklist (xxx,yyy,zzz..) (the names of the webdna contexts) ... then remove it from the array of formvars, before sending them on to the page (resuming where we were before this new block of C++). On the other hand, I know how it can get, and maybe it is a real nightmare in there.. ;-) ...but certainly less of a nightmare than all the hundreds/thousands of legacy webdna sites we are talking about. Anyway, meanwhile thanks to Brain and Olin for the simple hack-fix! ------------ Govinda govinda.webdnatalk@gmail.com Govinda

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:

WebCat2b15MacPlugIn - [authenticate] not [protect] (1997) Cart problem (1999) Passing Username and Password on the command line (2000) webCatalog and Stocks (1998) Wrapping text (1998) Emailing html (1998) Template Cache problem (2000) Cart doesn't interpret tag! (1997) New Mac Emailer... (1997) Hidden or Forbidden? (1998) Version f1 status (1997) Flat-file to XML converter (2006) Linux vs Jaguar (OSX) (2002) Setting up WebCatalog with Retail Pro data (1996) [Fileinfo] Context (2000) OSX b5 [listvariables] (2000) Hyperboard users wanting a quoted message (1998) Today's suggestions (1998) Subject: Authenticating users without dialog box (1997) Back to Authnet with storebuilder (2003)