![Check out Enfold](https://kriesi.at/wp-content/themes/kriesi/images/banner-enfold.jpg)
Tagged: Error fetching content, https, special heading, SSL, Windows 10
-
AuthorPosts
-
December 12, 2015 at 4:49 pm #551453
Hi there!
I just started to work on a new website today using the latest versions of WordPress (v4.4) and Enfold (v.3.4.6). The only additional 3rd-party-plugins I use are WPML and Gravity Forms, but even when I deactivate them I’m still getting the “Error fetching content” message every time I try to edit a special heading.
I never had this problem with other Enfold pages and I didn’t change any of the server settings. The only difference I can think of is that this new website uses SSL.
What am I doing wrong?
Thanks for your help!
Regards,
DanielDecember 13, 2015 at 12:31 pm #551596Ok, so it seems that I am able to edit the special headings again after turning off the SSL encryption for my domain. For the moment I can continue to work on my website, but this seems to be a bug that urgently needs a fix.
December 13, 2015 at 1:06 pm #551602Hi!
We would need to see the error in action in order to debug it, let us know if you decide to turn on SSL again.
Best regards,
JosueDecember 13, 2015 at 1:49 pm #551623Hi Josue,
Please see my comment in the other post and let me know when you want me to turn SSL on again. Thanks!
Regards,
DanielDecember 16, 2015 at 2:33 pm #553679Hi!
I replied to your other post. Lets stick to one topic only in one thread please.
Cheers!
AndyDecember 22, 2015 at 11:42 am #556447Hi Andy,
I just turned SSL on again and the issue I described above still exists. To reproduce it you just need to click on a special header and try to edit it.
Thanks for your help!
DanielDecember 22, 2015 at 11:58 am #556466Hi!
what if you try a plugin like:
https://wordpress.org/plugins/force-ssl-everywhere/
https://wordpress.org/plugins/wordpress-https/
https://wordpress.org/plugins/wp-force-https/Let us know about your results. Try to contact your SSL/Server about it. Does this issue happen when editing special heading only? or for other ALB’s elements as well?
Best regards,
AndyDecember 22, 2015 at 12:33 pm #556487Hi Andy,
I just tried the plugins you suggested, but they don’t make a difference. The other elements seem to be editable with SSL, so for now it’s only the special headings I can’t edit under HTTPS.
By “contact your SSL/Server about it” you mean I should ask my provider Alfahosting or the SSL certificate issuer Comodo? I can give it a shot, but I’m fairly certain they won’t see this as a problem that can be fixed on their end. And frankly I don’t think so either :-)
Best regards,
DanielDecember 24, 2015 at 5:25 am #557349Hi!
I’m not sure what’s going on there but I was able to modify the special heading element without triggering any errors: (s. private content)
Cheers!
Ismael-
This reply was modified 8 years, 8 months ago by
Andy.
December 24, 2015 at 10:53 am #557393Hi Ismael,
it seems to be a browser-related issue. I’m running Windows 10 Pro and in Chrome (v47.0.2526.106 m) I still get the same error message. But in Microsoft Edge (v25.10586.0.0) and Firefox (v43.0.2) I seem to be able to edit the special heading element.
Btw: Can you please remove the link from your post? Thanks!
Merry Xmas,
DanielDecember 27, 2015 at 9:13 am #557583Hi,
Could you try flushing your browser cache and reload few times to see if that helps? Ismael posted the link in private so it’s only visible to you and moderators.
Best regards,
RikardMay 24, 2016 at 8:03 pm #637716This is starting to appear on our sites as well. Some do indeed have SSL, but some do not. They get the same error. Just started happening about a month ago. Trying to get some sort of pattern to figure out the cause. Flushing cache does not seem to solve it. Switching browsers does not seem to solve it, either. I can send screenshots of two browsers on one machine, both hitting the same editor page and getting the same error, even after flushing cache. The screenshots are coming from sites now using ssl as a default transport layer. I am working at getting screenshots of the same error on another site that is using ssl and experiencing the same issues.
May 25, 2016 at 8:06 am #637898 -
This reply was modified 8 years, 8 months ago by
-
AuthorPosts
- You must be logged in to reply to this topic.