Responsive not working on secure site

Bill Summers1 · #1 06-16-2015, 04:24 PM

We have a secure site at https://www.fake-plastic.com.

When adding Ecwid, using script https://app.ecwid.com/script.js?6347869, the store loads, but the responsive nature of the store does not work. We've stripped every bit of logic, js, and even css from the page we're working on.

When testing from a local connection, we could get http://app.ecwid.com/script.js?6347869 to work responsively, but not https://app.ecwid.com/script.js?6347869.

I'm thinking that the secure version of the Ecwid script is calling out to non-secure servers somewhere.

Any kind of fix or work-around for this?

Regards,
Bill

river · #2 06-19-2015, 01:08 PM

Quote:

Originally Posted by Bill Summers1

We have a secure site at https://www.fake-plastic.com.

When adding Ecwid, using script https://app.ecwid.com/script.js?6347869, the store loads, but the responsive nature of the store does not work. We've stripped every bit of logic, js, and even css from the page we're working on.

When testing from a local connection, we could get http://app.ecwid.com/script.js?6347869 to work responsively, but not https://app.ecwid.com/script.js?6347869.

I'm thinking that the secure version of the Ecwid script is calling out to non-secure servers somewhere.

Any kind of fix or work-around for this?

Regards,
Bill

Hello,

I'm sorry that you are experiencing this issue on your website.

That is rather strange that the responsiveness depends on the protocol in this case. Could you please send the link to the particular page of your website where you have Ecwid doing this?

Meanwhile, I can suggest you using the universal script URL format: //app.ecwid.com/script.js?6347869 It should drop off all the relevance to the protocol - we'll see what happens then.

Looking forward to your reply!

Bill Summers1 · #3 06-19-2015, 04:59 PM

I put in the universal. It automatically pics up the matching protocol, which in this case is the https version. I've edited the page so that you can see the lack of responsiveness. As a work around, we were placing everything in a single column, which isn't optimal, but it works. But that workaround has been removed for the sake of testing.

The specific page is being sent to you in a private message.
Thanks!
Bill

river · #4 06-26-2015, 01:28 PM

Quote:

Originally Posted by Bill Summers1

I put in the universal. It automatically pics up the matching protocol, which in this case is the https version. I've edited the page so that you can see the lack of responsiveness. As a work around, we were placing everything in a single column, which isn't optimal, but it works. But that workaround has been removed for the sake of testing.

The specific page is being sent to you in a private message.
Thanks!
Bill

Hello!

Sorry for the delay with reply, it took some time to understand what was wrong on this page.

Eventually, the answer turned out to be simpler than I thought: there are some errors in the beginning of the page's code which break the responsiveness of Ecwid. As I mentioned earlier, Ecwid Product Browser's responsiveness depends on your website. For example, the correct !DOCTYPE is required in the source code of the page on your website for Ecwid to see that the website is responsive and adapt accordingly.

Take a look at this code from your page:

Code:

<head>
</head>
<body>
<DOCTYPE! HTML>

There are two issues here you need to fix:

1. Delete three tags above the doctype: head and body. The <!DOCTYPE html> tag should be on top of the page with nothing standing above it.

2. Correct the doctype moving the exclamation mark in front of the word like that: <!DOCTYPE html>

After that Ecwid should work responsively as expected.

If you have any more questions, please feel free to ask!

Bill Summers1 · #5 06-26-2015, 01:43 PM

Good catches. I completely missed those somehow. Works like a charm now, thanks!

river · #6 06-26-2015, 03:15 PM

Quote:

Originally Posted by Bill Summers1

Good catches. I completely missed those somehow. Works like a charm now, thanks!

Glad that it works now.

If there's anything else we can help you with, please feel free to ask!