thank you for update but last version 3.4.1 created mixed content issue on website where SSL is only active on admin side.
I use your plugin in websites where HTTPS is always forced and here no issue and in website where SSL is forced only on admin side but for visitor is possible to load website also with SSL.
After upgrading from 3.4.0 to 3.4.1 now visitor see mixed content warning, same issue also in admin side.
Now i resumed plugin 3.4.0 can be this issue be fixed in last version?
@peopleinside Do you have time to show me what kinds of elements are giving you issues in the latest version? The latest is a huge improvement on speed at the cost of the reliability we’re used to with the plugin. I would love to get it back to where it was, but a lot faster. Thanks for your help!
Actually, I just found an issue that may be responsible! Please download the latest version again and let me know if the issue persists.
the website is http://www.marcoborla.it I can keep last version of the plugin with the issue for short time.
I updated again the plugin but issue persist. With 3.4.0 no mixed content, with the last version I have mixed content.
How can I help you to solve quickly?
Issue seems resolved.
Warning was only preset on backend now after last update and I can solve by disable for that website option “Fixes insecure HTTP elements on HTTPS pages”
Last update help to fix front end issue
thanks all solved.
@peopleinside Thanks so much! Sorry for the hassle! Can you download the latest directly and upload it to your server? https://wordpress.org/plugins/wordpress-https/advanced/#download-previous-link
I just want to make sure that your code has the update I juuuust pushed out. If not, then I would recommend rolling back and I’ll have to see what I can do. This latest version is a huge speed increase, but reliability obviously went down, which I was anticipating. Thanks again!
@peopleinside Awesome! Make sure you test your back-end and front-end in incognito windows to ensure you don’t get any false positives.
@peopleinside If you get a chance, try using the Content Fixer option with 3.4.2 and let me know how that compares to disabling it. I’m hoping that it will work for you because it should be faster than disabling it. Thanks!
Sorry @mvied if you load on incognito https://marcoborla.it you can see mixed content persist in front end and in backend. Issue was not resolved. Only solution is use 3.4.0 for now. Seems all new version made this mixed content issue on that website where:
– front end can be reach by HTTP and HTTPS
– admin will be always HTTPS
@peopleinside Aww, that’s unfortunate. I really need this thing to speed up, so I’m going to keep working towards that. It’s really hard for me to not break anything while trying to do that, though. Thanks so much!
Is very strange issue now this is why so many message from my part solved and not.
Well, if I keep active “Fixes insecure HTTP elements on HTTPS pages.” I have mixed content on Admin side , front end side all OK
If I deselect “Fixes insecure HTTP elements on HTTPS pages.” I have the inverse situation where admin side is OK and front end side is mixed content!
- This reply was modified 6 years, 1 month ago by peopleinside.
@peopleinside I’m changing the internals quite a bit trying to find what isn’t necessary for performance-sake. I will have to do some more testing with the latest to find a balance. I may need to add additional config options to get it just right. Thanks for your feedback, it’s really helpful!
OK Mike if you need me you can find me at URL provided.
Seems now front end is working with “Fixes insecure HTTP elements on HTTPS pages.” active but when I login on admin side there are mixed warning.
If i deselect the option I have the inverse situation maybe not only on home page.
On URL filter I am unable to understand what I can put for tell that all content when is on /wp-admin/ should be HTTPS.
With version 3.4.0 this issue was not present. Thanks and sorry, this plugin is really the best for HTTPS never leaved in many years 😀
If you enable Debug mode, you should be able to see what’s throwing the insecure error on your page. Chrome also does a pretty good job of telling you what’s going on. That would help me narrow down what I need to tweak to get it perfect. At least 3.4.0 is stable, that is the reason I’m able to start making some riskier changes that should make it run a lot faster, which the biggest reason to not use the plugin.
Your ongoing support is much appreciated! I think users underestimate their value to projects like this. 🙂
- This reply was modified 6 years, 1 month ago by Mike Ems.
Can I email to you logs for not put here in a public forum?
Will be this allowed by the WordPress forum rules?
Maybe I can post here and after edit the post, let me try.
Nothing I enable the output but can well understand what put here from develop tool on Firefox.
When I login on admin side I see insecure elements are:
[removed for privacy]
I do not know why other png and elements are correct on HTTPS
@peopleinside Sure! Email me mike at mvied dot com
The short answer is because I changed stuff, haha. Not for you to figure out, that’s my job! How comfortable are you with modifying code? There’s a small section you could mess around with for me that would really help. No pressure.
- The topic ‘Issue mixed content on version 3.4.1’ is closed to new replies.