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

This WebDNA talk-list message is from

2010


It keeps the original formatting.
numero = 105359
interpreted = N
texte = christophe.billiottet@webdna.us wrote: > This is true: this bug has been there for a very long time. There is no easy fix as long as URL commands are active, because if we fix it, then URL commands do not work anymore: we spent a large number of hours on this. The bug has been fixed in the fastCGI version and the URL commands have been removed. The fastCGI version is free to everyone. > > May i add we did not charge for 6.0 to 6.2 upgrades, meaning we globally worked for the community, with scarce return. We now have to make difficult decisions about were we spend our remaining resources, and the fastCGI version is our choice. > > - chris 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 -- Donovan Brooke Euca Design Center [Practical-Ethical-Efficient] www.euca.us egg.bz artglass-forum.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)
christophe.billiottet@webdna.us wrote: > This is true: this bug has been there for a very long time. There is no easy fix as long as URL commands are active, because if we fix it, then URL commands do not work anymore: we spent a large number of hours on this. The bug has been fixed in the fastCGI version and the URL commands have been removed. The fastCGI version is free to everyone. > > May i add we did not charge for 6.0 to 6.2 upgrades, meaning we globally worked for the community, with scarce return. We now have to make difficult decisions about were we spend our remaining resources, and the fastCGI version is our choice. > > - chris 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 -- Donovan Brooke Euca Design Center [Practical-Ethical-Efficient] www.euca.us egg.bz artglass-forum.com Donovan Brooke

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:

OSX - webDNA 4.51 (2003) quitting (1997) SMSI FTP - calander system (2002) FlushDatabase Suggestion (1998) searchable list archive (1997) Protect (1997) SQL connection (2000) Check for OS (2003) multiple price line in formula.db (2004) What abobut variables named max ??? (2000) Search in 2 or more catalogs (1997) WebCatalog for guestbook ? (1997) MacAuthorize order data fields WAS:How To question... (1997) Browser Resolution (1999) Help getting [shownext] to increment (2003) Upgrading old WebCat Database Files (1997) WebCat2 Append problem (B14Macacgi) (1997) carriage returns in data (1997) WebDNA on Intel Mac (2006) WebCat2b13MacPlugin - nested [xxx] contexts (1997)