Securing images
 

Have a couple questions on how to do this.

1. I am pulling an image for my background via the css. What code do I put in it to make the background secure? Currently I have:


2. I'm trying to add an image to the txt_welcome area of the template. I place this code


It is showing up as a broken image. The image is there... double checked several times. How do I add an image to the txt_welcome area and make it secure?

3. Is there a way to make topsite images incorporated into the secure way of doing things? The code we have to use (an example) is as follows (we have this code in /main/prnotice.tpl):


Is there any way we can alter this or will we need to remove the topsite code?

Thank you.

Re: Securing images
 

Don't put an absolute path in the url portion. Assuming the CSS file is located in the skin1 directory, you should use:

background: #FFEA7B url(background.jpg);



Language variables don't parse the Smarty syntax normally used in the tpl files. You need to double escape it and remove the dollar sign. Try replacing {$ImagesDir} with {{ImagesDir}}

Re: Securing images
 

What is topsite?

Re: Securing images
 

This still makes the background image unsecure.

css file = skin1 directory
background = skin1 directory

I also tried it in the skin1/images directory

Still listing as unsecure.


I changed it to this:


Still not working.

Re: Securing images
 

A Web page that contains a list of links to other Web sites. The order of the list is based on the number of clicks users make to each site. The more clicks, the higher up the list the link to the site moves. Webmasters use topsites as a way of attracting visitors and collecting per-click revenue. Typically written in PHP, although other languages are used, there are free topsite scripts available as well as commercial products.

Re: Securing images
 

Maybe, I mis-interpretated your question. Why would you want to hard-code an image as https (secured) all the time? There is an overhead when serving pages, assets, etc with https versus http. The solution I posted is changing the link to a relative link. When the site is accessed via http, it will load the image via http. If it's accessed via https, it will load via https. If you want it to always load from https, just change the prefix to https.

Re: Securing images
 

Sorry, forgot the other step. In the tpl that this is being called from, you need to call it with the following:

{$lng.txt_welcome|substitute:"ImagesDir":$ImagesDi r}

Re: Securing images
 

In our store, when you log in, it prompts that some information is not secure. If you say "do not load the stuff that is unsecure" what is not loading is these images. Because members can and are newbies, any reference to "unsecure" scares them, which leads to them not purchasing things in our store. So.. I am trying to find a way to make it so this message doesn't appear, and the only way to do that is to make our images secure as well.

If I'm doing something wrong, please let me know. If there is an easier way of doing things .. too let me know.

Re: Securing images
 

Why not allow the content to be shown, and then view the source to see what is being called via http?

Re: Securing images
 

I know what is being called. It's the images... hense me asking how do I make them secure.

Here... My Site

Images that are not secure: home & contact icon in top nav bar. Bottom topsite footer images. Background image. I did make the logo so it wouldn't throw up the error.

I just want it to NOT throw up "This page contains both secure and insecure items..."

But then again... I just realized that it's telling me that the cart isn't secure either, even though everything appears to be working correctly. :sigh One more thing to add to my to do list.