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

This WebDNA talk-list message is from

2011


It keeps the original formatting.
numero = 107375
interpreted = N
texte = Thanks Chris, I'll install them ASAP then report my results, although I'm sure you've already tested them and confirmed that they work properly ... :) Sincerely, Kenneth Grome > The [thisurlplusget] bug is fixed. Ken, i emailed you the > versions for your Ubunutu 64 and Debian 32 > > - chris > > On Sep 18, 2011, at 15:50, Kenneth Grome wrote: > > I think I found an important clue in a PHP / Lighttpd > > online reference ... > > > > PHP has a fuction called REQUEST_URI which does the > > same thing as [thisurlplusget] in WebDNA. They both > > grab the full URL that was requested, including the > > parameters after the question mark. > > > > So it seems that [thisurlplusget] is the only way > > WebDNA can access the URL parameters in a lighttpd > > error handler page! > > > > Note that when I access the error handler page directly > > -- rather than getting there by requesting a > > non-existing page -- the [formvariables] context works > > as expected. > > > > -------- > > > > Bottom line, when using lighttpd you'll need > > [thisurlplusget] if you want to access the URL > > parameters when the visitor tries to visit a page that > > does not exist in the specified location. > > > > Sincerely, > > Kenneth Grome > > > >>> 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 > > > > ------------------------------------------------------- > > -- This message is sent to you because you are > > subscribed to the mailing list . > > To unsubscribe, E-mail to: > > archives: http://mail.webdna.us/list/talk@webdna.us > > Bug Reporting: support@webdna.us > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us 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)
Thanks Chris, I'll install them ASAP then report my results, although I'm sure you've already tested them and confirmed that they work properly ... :) Sincerely, Kenneth Grome > The [thisurlplusget] bug is fixed. Ken, i emailed you the > versions for your Ubunutu 64 and Debian 32 > > - chris > > On Sep 18, 2011, at 15:50, Kenneth Grome wrote: > > I think I found an important clue in a PHP / Lighttpd > > online reference ... > > > > PHP has a fuction called REQUEST_URI which does the > > same thing as [thisurlplusget] in WebDNA. They both > > grab the full URL that was requested, including the > > parameters after the question mark. > > > > So it seems that [thisurlplusget] is the only way > > WebDNA can access the URL parameters in a lighttpd > > error handler page! > > > > Note that when I access the error handler page directly > > -- rather than getting there by requesting a > > non-existing page -- the [formvariables] context works > > as expected. > > > > -------- > > > > Bottom line, when using lighttpd you'll need > > [thisurlplusget] if you want to access the URL > > parameters when the visitor tries to visit a page that > > does not exist in the specified location. > > > > Sincerely, > > Kenneth Grome > > > >>> 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 > > > > ------------------------------------------------------- > > -- This message is sent to you because you are > > subscribed to the mailing list . > > To unsubscribe, E-mail to: > > archives: http://mail.webdna.us/list/talk@webdna.us > > Bug Reporting: support@webdna.us > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us 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:

Re:Emailer and encryption (1997) RAM variables (1997) WC2.0 Memory Requirements (1997) WebCat2b13 Mac plugin - [sendmail] and checkboxes (1997) Hello??? (1997) Max Record length restated as maybe bug (1997) setting username and password using a form. (2000) Plugin or CGI or both (1997) Cookies not being set on PC/ Explorer (2000) Nested tags count question (1997) Another bug to squash (WebCat2b13 Mac .acgi) (1997) customizing the color of user's pages (1997) search across ip/domain addresses? (1998) foriegn characters and webcatalog (1997) [WriteFile] problems (1997) WebDNA on Intel Mac? (2006) Looking for a Webcat developer based in the Netherlands (2000) File upload in Webstar (2001) Date math (1997) More on the email templates (1997)