Hi,
Google Search Console has sent me a warning message to tell me that, from January 2017, Chrome will mark as “not secure” the pages with password or credit card input fields, if these pages are not published with HTTPS.
In the same message, Google says this page is marked as “not secure” but the page does not collect any kind of data with input fields.
Actually no site’s page contains input fields for sensitive data.
Any idea about the reason of that warning message? Have you got similar issues with other customers? Is something that may be related with the theme? Could simply be an error by Google?
Thanks a lot for your answer,
bye.
This is what I did since I don’t use any logins with Newsmag
I opened this file
/theme/parts/header/td-login-modal.php
select all, delete, save; replace on server.
Not sure that will solve your issue, but I’m still using 3.1 and that removed the un-needed login css/code from my header on all pages, which was not needed and should have been an optional on/off item for theme.
All my sites are now https anyway, but seemed like something worth trimming on our sites.
Depending on theme version, also might need to disable the comments box if your site not running https.
-
This reply was modified 9 years by
simchris.
Hello whitehat,
Do you update the latest theme version? If you have not do it you should do it now because in the latest version of the theme, was introduced the option to disable logging section. Please notice that since now, if you will have a log-in on your website and if you do not have the https you will see the no-secure message. You should have the https. For more references about this regard, you should read the following information posted by Google, like this -> http://www.pcworld.com/article/3118164/security/google-chrome-to-start-marking-http-connections-as-insecure.html
Thanks for your understanding!
Hello whitethat,
You should check the Theme panel->Header->Top Bar section and from there you simply disable the login feature, like this ->https://www.screencast.com/t/HIA7zPxXUyg
Thanks for your understanding!