I am trying to: load page via https
Link to a page where the issue can be seen: bayfrontchamber.com
I expected to see: lock
Instead, I got: no lock - mixed content error. inpsector shows mixed content error ajax-loader2.gif admin-ajax.php:1 Failed to load resource and other errors that look to be from Views.
by the way, wordpress general settings are http, not https. this is due to the cloudflare flexible ssl we are using.
Hi Malaga,
Thank you for contacting us and I'll be happy to assist.
In the WordPress environment, it is considered a standard and recommended practice, to generate the permalinks or URLs using the base value that is stored at Settings -> General.
WordPress itself, themes, and plugins all rely on "Site Address" value and if that is not set to use "https", you'll continue to run into similar mixed content warnings, if the website is served over the "https".
All official and community guides and documentation that you'll find online on moving from "http" to "https", will suggest this change as a first step.
Following are some plugins and resources which should help in fixing mixed content warnings, but "ideally", you should avoid keeping an SSL setup which requires you to keep "http" in the "General" settings:
hidden link
https://wordpress.org/plugins/ssl-insecure-content-fixer/
hidden link
hidden link
I hope this helps.
regards,
Waqar
ok, thanks. we were getting loops with the cloudflare setup using https but maybe there's a way to avoid that. I'll work on another solution. thanks.
I did set https but still getting the error.
sorry - just seeing your last response. i had already cleared the toolset caches, cloudflare cache, and disabled the site cache. now i've also updated the htaccess file - still getting no padlock.
sorry - confused another email for yours.... in any case still have the issue, and i have also tried adding this to htaccess:
<FilesMatch ".(eot|ttf|otf|woff|css|js)">
Header set Access-Control-Allow-Origin "*"
</FilesMatch>
please advise.
Hi Malaga,
Thank you for sharing these details.
In case the issue still persists, after clearing all involved caches, I'll recommend sharing temporary admin login details, so that I can log in and see how the homepage's view is configured.
I've set your next reply to private so that only you and our support team can access it.
Note: Please make a complete backup copy of the website, before sharing the access details.
regards,
Waqar
Hi Malaga,
Thank you for sharing these details.
I've run some tests on my website and noticed that changing the spinner selection option in the view's "Pagination and Sliders Settings" section forces the spinner graphic's URL to get updated.
( screenshot: hidden link )
At the moment both views, which are used in the homepage are using the spinner graphic "hidden link", which is resulting in the mixed content warning.
Based on the results from my test website, if you'll specifically select any of the available spinner options, the view will update its output to use the link with "https".
Please let me know how it goes.
regards,
Waqar
That's the first thing I thought of too but I couldn't find the option to change it - it's not where i would normally find it. can you give me step by step?
Hi Malaga,
Please open your view's edit screen and scroll to "Pagination and Sliders Settings" section.
Click the "Advanced options" button under "Pagination options" heading and a new set of options will appear.
This screenshot will make it more clear:
hidden link
regards,
Waqar
thanks - that worked! so, is this a bug? do i need to check all views running on https?
Hi Malaga,
Thanks for the update and glad it worked.
Since this has been confirmed now from your website and from my own tests, I've shared these findings to the concerned team. This will need to be reviewed further so that the spinner can adjust better when moving from "http" to "https".
Appreciate you brought this forward and I'll keep you updated with the progress, through this ticket.
For now, yes you'll need to repeat the same step of updating/resaving the spinner setting, for all existing views, which were created before moving to "https".
regards,
Waqar
good to know - will check my other sites. thanks!
