Hi,
In the template, some of the links inserted in header and footer are not using https and as a result, the SSL security is not valid in browsers.
Please see the site.
Please provide a solution for images and other links to appear as https.
-Ash
|
|
Please let me know the solution to this. This is an urgent issue beofre I can launch my website.
Thanks.
-Ash
|
|
Hi Ash,
We’ve tried to open the page, but your server returned 404 (not found). Can you please check?
BR,
ThemeBurn team
|
|
Sorry, there was a mistake in the URL.
The following is the correct one.
|
|
Please take a look at the corrected URL I have provided.
-Ash
|
|
Hello,
I hope to get your attention because it seems no one is following up on update to this support issue. I cannot launch the store after all this work of setup unless this is resolved.
Thanks.
-Ash
|
|
This is not a theme issue, but a custom one, that is relevant to your manual modifications. Hence, you should resolve it manually.
You have custom html in the menu, which contains hardcoded image, accessed from insecure http link. You have also custom css, which uses insecure image as background url. That’s why there is mixed content notice when accessing the site under https protocol.
You should change these images to be served from https or just remove the http: part, so that the path should begin with //
Regards,
ThemeBurn team
|
|
Hello,
Thanks for that insight. I have corrected these issues and it is better now.
Remaining issue are some Information pages in Menu that are not loaded has https, even though the page itself is secure.
For example, take a look at the “Support menu” item. It is linked without https prefix, but if I prefix it as https:, it loads correctly with security.
How do I control such Information page loads from Menu?
-Ash
|
|
I think you need a something similar.
Regards,
ThemeBurn team
|
|
Ok, thanks.
On second thoughts, I think I can ignore these unsecure page loads because they do not deal with any sensitive account information.
-Ash
|
|
Great,
I mark this issue as resolved.
Regards,
ThemeBurn team
|
|