Forums / Setup & design / valid HTML4 URLs in eZ

"Please Note:

At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

valid HTML4 URLs in eZ

Previous topic

Setup & design

Next topic

Author	Message
Marko Žmak	Tuesday 11 September 2007 12:44:23 am I was dealing with having one of my eZ sites pass the W3c validator (http://validator.w3.org/), and I came accross the problem of some URLs breaking the validity check. The problem is that these URLs have the ampersand ("&") in it. According to W3c specifications, the ampersand in the URL should be escaped with "&". So I was wondering if there is an operator in eZ that would convert such a URL in a valid one? Also I'm wondering what should I do to make this conversions in ALL the URLs in my site? As far as I can think of now, I have to: - convert the URLs that I display from my templates (e.g. the URL attribute of an object) - convert the URLs that are embeded in XML attributes (override their templates) - convert the static URL in my templates (hardcoded in the template code) if such exsist This are all the possibilities of invalid URLs that I can think of for now. Does anyone have any other idea? -- Nothing is impossible. Not if you can imagine it! Hubert Farnsworth

Author

Message

Marko Žmak

Tuesday 11 September 2007 12:44:23 am

I was dealing with having one of my eZ sites pass the W3c validator (http://validator.w3.org/), and I came accross the problem of some URLs breaking the validity check. The problem is that these URLs have the ampersand ("&") in it. According to W3c specifications, the ampersand in the URL should be escaped with "&".
So I was wondering if there is an operator in eZ that would convert such a URL in a valid one?

Also I'm wondering what should I do to make this conversions in ALL the URLs in my site?
As far as I can think of now, I have to:

- convert the URLs that I display from my templates (e.g. the URL attribute of an object)
- convert the URLs that are embeded in XML attributes (override their templates)
- convert the static URL in my templates (hardcoded in the template code) if such exsist

This are all the possibilities of invalid URLs that I can think of for now. Does anyone have any other idea?

--
Nothing is impossible. Not if you can imagine it!

Hubert Farnsworth