QR-Code Widget is not SSL Compatible 
Auteur : Peter W.I am in the process of upgrading my websites to be fully SSL compliant and discovered that whenever I have the QR-Code widget on a page, it prevents the page from being marked as "Secure" in Chrome.
I looked at the source code of the webpage and discovered the problem is that the widget obtains the image from http://api.qrserver.com instead of https://api.qrserver.com.
I tested this by copying the generated code into an HTML Code widget and correcting the link. This immediately solved the problem and the page appears as Secure.
Example from my website:
https://www.stnv.de/en/index.php = Page with QR Code updated with https
https://www.stnv.de/en/news-startrektours.php = Using QR-Code widget. Strangely. the QR-Code is still displayed.
Please update the QR-Code widget to use https in order to solve this issue.
Hello Peter,
I also noticed the same behavior and I already informed the developers. They will check the issue and, in case, fix it in the future updates.
Many thanks!
Auteur
Can I also remind you of another issue I reported, that you confirmed on 23 January.
Website x5 13 Pro. Dynamic Content showing control codes on website.
It has still not been fixed and that is stopping me completing major updates to my websites.
Auteur
The QR-Code issue should be easy to fix - just add the s in https and it is fixed.
Please get this fixed quickly as otherwise I will have to manually exchange the widget for html code on several websites.
Hello Peter,
As soon as I have news about the issues I will inform you immediately.
Many thanks!
Auteur
Any news on this. Twitter widgets, etc. had recent updates, but this one has still not been updated. This is a very minor update. I need this as otherwise I have to replace the code on hundreds of pages.
Hello Peter,
As soon as I have any news I will inform you immediately.
At the moment I have no news about it but it will be solved as soon as possible.
Many thanks!
Auteur
Yet another month gone and no movement on this. I am really beginning to ask myself if it is worth my time reporting bugs when they are acknowledged, yet not fixed.
I am going to have to give up on this one and manualy exchange the code on all my websites as it does not look likely that this bug will be fixed anytime soon.
Hello Peter,
Soon it will be released the update of the object where this issue has been solved.
Many thanks!