Re: [ReturnRaw] and hiding FORM data

This WebDNA talk-list message is from

2003


It keeps the original formatting.
numero = 46911
interpreted = N
texte = >Oh... I should have added this. > >I know you can have a results.tpl as a form and pass items to it >with fake field names and have the result page do the [search] with >the real field names. >This would then Hide the WebDNA fields as the results page is parsed. > >It is not just FORM search data I'm trying to hide. >Links generated from WebDNA also display the '&field' names. > >This still does not tell me how to use [ReturnRaw] to do it.ReturnRaw will not do what you seem to think it will do. I think you're misunderstanding what it's for and how it works. You're also missing the more important fact that you should be using search contexts -- and not search commands -- and you should also refrain from passing any unnecessary values to the search context via the form.Why don't you try using method=POST in your search form, then use a search context on your results page. Then *never* pass any db paths. This way, your visitors will never know where your db's are.But it doesn't matter if they know where your db's are anyways, because if you have your preferences set properly, they will never be able to view or download them -- assuming you're not giving them the ability to upload files to your server, of course.By the way, when was the last time you wrote any webdna code or upgraded to a newer version? That $search syntax was deprecated about 5 years ago. Are you still using WebCatalog 2.x? Sincerely, Kenneth Grome--------------------------------------------------- WebDNA Professional Training and Development Center 175 J. Llorente Street +63 (32) 255-6921 Cebu City, Cebu 6000 kengrome@webdna.net Philippines http://www.webdna.net ---------------------------------------------------------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: [ReturnRaw] and hiding FORM data (Kenneth Grome 2003)
  2. Re: [ReturnRaw] and hiding FORM data (Kenneth Grome 2003)
  3. Re: [ReturnRaw] and hiding FORM data (Kenneth Grome 2003)
  4. Re: [ReturnRaw] and hiding FORM data (Kenneth Grome 2003)
  5. Re: [ReturnRaw] and hiding FORM data (Kenneth Grome 2003)
  6. Re: [ReturnRaw] and hiding FORM data (Marko Bernyk 2003)
  7. Re: [ReturnRaw] and hiding FORM data (Tim Robinson 2003)
  8. Re: [ReturnRaw] and hiding FORM data (Marko Bernyk 2003)
  9. Re: [ReturnRaw] and hiding FORM data (Marko Bernyk 2003)
  10. Re: [ReturnRaw] and hiding FORM data (Clayton Randall 2003)
  11. Re: [ReturnRaw] and hiding FORM data (Marko Bernyk 2003)
  12. Re: [ReturnRaw] and hiding FORM data (Tim Robinson 2003)
  13. [ReturnRaw] and hiding FORM data (Marko Bernyk 2003)
>Oh... I should have added this. > >I know you can have a results.tpl as a form and pass items to it >with fake field names and have the result page do the [search] with >the real field names. >This would then Hide the WebDNA fields as the results page is parsed. > >It is not just FORM search data I'm trying to hide. >Links generated from WebDNA also display the '&field' names. > >This still does not tell me how to use [returnraw] to do it.ReturnRaw will not do what you seem to think it will do. I think you're misunderstanding what it's for and how it works. You're also missing the more important fact that you should be using search contexts -- and not search commands -- and you should also refrain from passing any unnecessary values to the search context via the form.Why don't you try using method=POST in your search form, then use a search context on your results page. Then *never* pass any db paths. This way, your visitors will never know where your db's are.But it doesn't matter if they know where your db's are anyways, because if you have your preferences set properly, they will never be able to view or download them -- assuming you're not giving them the ability to upload files to your server, of course.By the way, when was the last time you wrote any webdna code or upgraded to a newer version? That $search syntax was deprecated about 5 years ago. Are you still using WebCatalog 2.x? Sincerely, Kenneth Grome--------------------------------------------------- WebDNA Professional Training and Development Center 175 J. Llorente Street +63 (32) 255-6921 Cebu City, Cebu 6000 kengrome@webdna.net Philippines http://www.webdna.net ---------------------------------------------------------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ 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:

Safari browser and WebDNA set-cookies (2003) Includeform Error (2002) Cut off from the list and can't get an answer to the confused re:QTY price updating question (1998) Calculate UnitShipCost in Formulas.db (1999) Rotating Banners ... (was LinkExchange) (1997) t or f (1997) nested context (1998) WebCat chatroom (1997) problems with 2 tags shakur (1997) Help! WebCat2 bug (1997) Using Grep to Format Text (2001) Not really WebCat (1997) Shipcost formula (2004) [OT] Kerio Mailserver (2003) Netscape Communicator 4 chops off URLs (was No Data) (1997) [isfolder] and [filename] (1997) Roundup function? (1997) Field name-subcategory (1997) serial number generation (1997) GrandTotal not right (1997)