Re: [WebDNA] Bug in [thisurlplusget] on v7

This WebDNA talk-list message is from

2011


It keeps the original formatting.
numero = 107371
interpreted = N
texte = > So lighttpd does not work properly? It seems to be working fine for me. It always has, ever since I started using it 2-3 years ago. > How do you know the error is with WebDNA then? Two points to consider here: 1- There is definitely a bug in [thisurlplusget] because it appends "lusget]" to the end of the interpreted value when it should not. This is an issue with a simple workaround, so until the bug gets fixed I'm using the first of these two workarounds: [getchars start=8&from=end][thisurlplusget][/getchars] [middle endbefore=lusget][thisurlplusget][/middle] 2- Since [formvariables] fails to display the name=value parameters that appear after the ? in the originally requested URL, my first thought is that this is also a bug. After all, shouldn't [formvariables] display these name=value pairs? Maybe now! After all, this is a special situation in which the SERVER (not WebDNA) redirects the request to WebDNA's error page. So maybe, just maybe, these name=value pairs are NOT being passed as "formvariables" from lighttpd to WebDNA. If this is true, it would explain why the [formvariables] context does not display them. But if they are not formvariables, what are they??? They are certainly being passed to the page somehow, because [thisurlplusget] is displaying them. In fact, [thisurlplusget] seems to be the ONLY way I can display then in v7. So the big question for me is: How are they getting there, and how can WebDNA access them without using [thisurlplusget]? Or is this actually a bug in the formvariables context in v7 after all? Chris, do you have any insights on this issue? Sincerely, Kenneth Grome Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Bug in [thisurlplusget] on v7 (Kenneth Grome 2011)
  2. Re: [WebDNA] Bug in [thisurlplusget] on v7 (Kenneth Grome 2011)
  3. Re: [WebDNA] Bug in [thisurlplusget] on v7 (christophe.billiottet@webdna.us 2011)
  4. Re: [WebDNA] Bug in [thisurlplusget] on v7 (Kenneth Grome 2011)
  5. Re: [WebDNA] Bug in [thisurlplusget] on v7 (Kenneth Grome 2011)
  6. Re: [WebDNA] Bug in [thisurlplusget] on v7 (Kenneth Grome 2011)
  7. Re: [WebDNA] Bug in [thisurlplusget] on v7 (William DeVaul 2011)
  8. Re: [WebDNA] Bug in [thisurlplusget] on v7 (Kenneth Grome 2011)
  9. Re: [WebDNA] Bug in [thisurlplusget] on v7 (William DeVaul 2011)
  10. Re: [WebDNA] Bug in [thisurlplusget] on v7 (Kenneth Grome 2011)
  11. Re: [WebDNA] Bug in [thisurlplusget] on v7 (Kenneth Grome 2011)
  12. Re: [WebDNA] Bug in [thisurlplusget] on v7 (christophe.billiottet@webdna.us 2011)
  13. Re: [WebDNA] Bug in [thisurlplusget] on v7 (William DeVaul 2011)
  14. Re: [WebDNA] Bug in [thisurlplusget] on v7 (Kenneth Grome 2011)
  15. Re: [WebDNA] Bug in [thisurlplusget] on v7 (christophe.billiottet@webdna.us 2011)
  16. [WebDNA] Bug in [thisurlplusget] on v7 (Kenneth Grome 2011)
> So lighttpd does not work properly? It seems to be working fine for me. It always has, ever since I started using it 2-3 years ago. > How do you know the error is with WebDNA then? Two points to consider here: 1- There is definitely a bug in [thisurlplusget] because it appends "lusget]" to the end of the interpreted value when it should not. This is an issue with a simple workaround, so until the bug gets fixed I'm using the first of these two workarounds: [getchars start=8&from=end][thisurlplusget][/getchars] [middle endbefore=lusget][thisurlplusget][/middle] 2- Since [formvariables] fails to display the name=value parameters that appear after the ? in the originally requested URL, my first thought is that this is also a bug. After all, shouldn't [formvariables] display these name=value pairs? Maybe now! After all, this is a special situation in which the SERVER (not WebDNA) redirects the request to WebDNA's error page. So maybe, just maybe, these name=value pairs are NOT being passed as "formvariables" from lighttpd to WebDNA. If this is true, it would explain why the [formvariables] context does not display them. But if they are not formvariables, what are they??? They are certainly being passed to the page somehow, because [thisurlplusget] is displaying them. In fact, [thisurlplusget] seems to be the ONLY way I can display then in v7. So the big question for me is: How are they getting there, and how can WebDNA access them without using [thisurlplusget]? Or is this actually a bug in the formvariables context in v7 after all? Chris, do you have any insights on this issue? Sincerely, Kenneth Grome 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:

WebCat2b13MacPlugIn - [showif][search][/showif] (1997) founditem align (1998) no template caching (1997) Changing the value assigned to a formvariable (2000) WebCatalog seems to choke on large (2meg) html files. (1998) Another form question (2000) [TEST] - Please Ignore (2000) MasterCounter and capitalization (1997) off topic fetch vs PCS photomaster (1997) New Webcatalog for Mac (1997) RE: Formulas.db + Users.db (1997) Problems searching from a FORM (1997) French characters in variables (2001) [UPPERCASE] (1997) OT bookmark my site (1999) Re:HELP - NONE STOP DIGESTS. Digest for 4/24/97) (1997) Any limit to [include] (1997) [WebDNA] limit found per row (2011) Practice runs ? (1997) WebCat2b15MacPlugin - [protect] (1997)