 |
jasonbyrne
User
Dec 8, 2004, 1:42 PM
Post #1 of 3
(2331 views)
Shortcut
|
|
unencoded ampersands in URLs
|
Can't Post
|
|
In trying to create pages that can be validated to XHTML 1.0 standards, my search results page is turning up errors. The guidelines say "If you want to use a literal ampersand in your document you must encode it as "&" (even inside URLs!)."
My problem is that I see no way to tell the software to encode the ampersands properly. I am using ver. 1.12. Any help would be greatly appreciated! TIA
|
|
| |
|
Cliff
Staff
Dec 9, 2004, 2:11 PM
Post #2 of 3
(2313 views)
Shortcut
|
|
Re: [jasonbyrne] unencoded ampersands in URLs
[In reply to]
|
Can't Post
|
|
Hi Jason,
Thanks for posting.
What you can do is use a placeholder modifier to HTML encode the placeholder that publishes the content the results page. Placeholder modifiers are special suffixes added to placeholders to modify the content when it's published into the template. They can be used to change the format of a content field, convert the content for use in JavaScript or XML files, and more.
For specific details on how to use place holder modifiers, you can check out this page in our online documentation:
http://www.interactivetools.com/docs/doc.cgi?/searchengine/doc_page46.html
You will want to use the $_he$ modifier. I hope that helps, but if you need any more details just let me know 
Regards,
Cliff Stefanuk - Customer Service Manager
support@interactivetools.com
|
|
| |
|
jasonbyrne
User
Dec 9, 2004, 2:52 PM
Post #3 of 3
(2310 views)
Shortcut
|
|
Re: [Cliff] unencoded ampersands in URLs
[In reply to]
|
Can't Post
|
|
Cliff,
Thanks! I figured out where the problem was and modified the template. The page now correctly validates as XHTML 1.0 compliant.
Next time, I'll try to do a better job of actually reading the documentation :)
Jason
|
|
| |
|
