Hi,
run into some issues with the theme mods to the post editing, when using WooCommerce in particular.
1) when editing a product, or post, and switching to visual editor, while in *https*, something loading is not being loaded via https and causes a browser warning (site wide is https) to okay load of insecure content; creates autosave point. In visual editor, elements like bullet points in unordered lists don’t render, but are shown indented but not actually indented on page preview or publish.
2) unable to properly manage some elements in text editor, where some tags don’t function properly. In other words, the theme is “monkeying” with the ability to actually enter HTML properly like line breaks and the <br> tag in particular.
3) the divider line in visual mode is actually distracting when trying to edit content, and option to remove that or toggle off is actually now desirable while I tolerated it originally.
So, is there an option or function I can use to force “disable” the divider line and/or element modifying the post page?
Having this issue with td speedbooster plugin “off” or “on” and no major plugins running during dev cycle (meaning Yoast SEO off, social media stuff totally off, no mod_pagespeed running, no minification, no site caching, etc.).
-
This topic was modified 11 years by
simchris.
Figured out how to work around the line breaks issue since the <br> tag is ignored in text edit.
Basically have to do:
Some text here is really awesome.
& nbsp;
» Click here to learn more.
Since this will not work
Some text here is really awesome.<br>
» Click here to learn more.
Have not been able to determine what is loading via http when switching to visual editor on post or product pages. Everything on the site uses forced 301 redirect for any http requests, so nothing can load via http on our domain; however the admin panel is loading
Oddly Newspaper theme running in different folder on same domain, doesn’t throw any error when editing post in visual mode.
Might be a WooCommerce thing. I will have to try that next.
🙂