Absolute paths?

Previous topic

Setup & design

Next topic

Author	Message
Ben Overmyer	Wednesday 26 November 2008 8:32:42 am Currently, our site ( https://lpdaac.usgs.gov ) shows a "insecure items" warning on every single page. I've modified every template, stylesheet, and javascript file to use only absolute paths, but eZ Publish itself is putting relative paths to images into the markup. How do I force eZ Publish to only serve absolute paths?
michiel n.	Wednesday 26 November 2008 9:25:00 am The only problem I see is that I don't have the root certificate of Verisign (read: do not trust verisign). If it shows 'insecure items' because it uses an absolute path, or do I misunderstand you? But to answer your question, check which template is being used for displaying images. Once you found out, check whether it uses src={$image.imagepath\|ezroot} or src={$image.imagepath\|ezurl} You also might want to check your vhosts and rewrite rules, those could screw up your configuration as well. Certified eZ developer looking for projects. michieln at gmail dot com http://ez.no/certification/verify/225305
Ben Overmyer	Wednesday 26 November 2008 9:43:19 am The template for images appears to be using ezroot, not ezurl. I need to use URLs that include the server/host name (e.g., https://lpdaac.usgs.gov) in them in order to get rid of the "insecure items" warnings. I've done this in other templates by doing something like this: <img src="https://lpdaac.usgs.gov{'extensions/etc/images/test.gif'\|ezdesign('no')}" alt="" /> Unless someone has a better solution, that is.

Author

Message

Ben Overmyer

Wednesday 26 November 2008 8:32:42 am

Currently, our site ( https://lpdaac.usgs.gov ) shows a "insecure items" warning on every single page.

I've modified every template, stylesheet, and javascript file to use only absolute paths, but eZ Publish itself is putting relative paths to images into the markup.

How do I force eZ Publish to only serve absolute paths?

michiel n.

Wednesday 26 November 2008 9:25:00 am

The only problem I see is that I don't have the root certificate of Verisign (read: do not trust verisign).

If it shows 'insecure items' because it uses an absolute path, or do I misunderstand you?

But to answer your question, check which template is being used for displaying images.
Once you found out, check whether it uses

 src={$image.imagepath|ezroot}

 src={$image.imagepath|ezurl}

You also might want to check your vhosts and rewrite rules, those could screw up your configuration as well.

Certified eZ developer looking for projects.
michieln at gmail dot com
http://ez.no/certification/verify/225305

Ben Overmyer

Wednesday 26 November 2008 9:43:19 am

The template for images appears to be using ezroot, not ezurl.

I need to use URLs that include the server/host name (e.g., https://lpdaac.usgs.gov) in them in order to get rid of the "insecure items" warnings. I've done this in other templates by doing something like this:

Unless someone has a better solution, that is.