Why no link? This has a very simple explanation, and it's not a bug.
When you change to SSL, without updating the X3 pages, you have CACHED pages from the non-SSL version trying to load non-SSL CDN core assets via SSL page. This will create "insecure requests" which are blocked by the browser.
Furthermore, I can imagine that you now have BOTH SSL and NON-SSL versions of your website available? This will compound the issue.
Why? First of all, because they are two different websites technically, and X3 will cache pages based on where the request comes from ... This will create cached X3 pages on your server, that suit one request method, but not the other. Furthermore, you should never have both SSL AND non-SSL available anyway, because it means your canonical page link will fluctuate, and this is not good for SEO either. Never should two different links be able to access the same page.
netmax wrote:Disabling the CDN delivery fixes the problem, but as far as I know you, you want to fix that in general
It is not a bug, we already have dozens of X3 websites running on SSL, including the demo if you noticed:
https://demo.photo.gallery/
You may therefore need to do the following:
1. Setup a redirect on your website to make sure ALL
http requests are redirected to
https. There is no logical reason why you would want to keep both http and https.
2. Make a small change in panel by clicking "save" somewhere, just to force the cached pages to refresh.
3. When pages are re-loaded from SSL, the CDN core assets will be loaded from a different SSL URL.
It will work fine.
