I don’t think there is an ETA to fix this, as WordPress has moved on from TinyMCE and now uses the Block Editor.
The Block Editor has an html block, so switching between Visual & Text no longer is even a concept.
If you are stuck with the ‘classic editor/Tiny MCE’ there are ways you can work around this, such as creating shortcodes for your html/javascript elements.
I see.
I’m afraid that I’m rather stuck then. At least as far as my knowledge reaches in this matter.
I’m using WooCommerce with extra tabs for product information. I use the DIVI theme but haven’t dared to mess around with the product pages yet. Even if I mess around with them, I want to use the “Woo Tabs” and not make my own tabs with information. The main reason for that is to keep all product information within WooCommerce and not, for example, in a custom table on a DIVI-page.
And it’s the Woo Tabs that use the TinyMCE as far as I know.
If I was a better programmer, I’d probably be able to shortcode something classy. But in my case, I’m afraid that I’d just end up with thousands, losing control of them, since every product might have 1-10 accessories that needs to be linked.
Anywho! Thanks for the reply.
Ah ha, this is why it is always best to give as much detail as possible in an initial post, to avoid talking at cross purposes.
As this is a WordPress support forum, my natural assumption is that your enquiry is about WordPress, as you mentioned nothing else.
As it seems, the enquiry is about Divi, which is a commercial product so any support or ETA for ‘fixes’ should be addressed to the theme authors, as volunteers here have no access to commercial products. https://www.elegantthemes.com/contact/
Additionally, you mention ‘WooCommerce’ & ‘Woo Tabs’ they is a third party plugin and any information, support or ETA on ‘fixes’ should be address directly to the plugin authors.
https://wordpress.org/support/plugin/woocommerce/
https://wordpress.org/support/plugin/woo-tabs/
Hopefully this points you in the right direction.
-
This reply was modified 2 years, 8 months ago by
Alan Fuller.
OK.
But since neither DIVI nor WooCommerce made the TinyMCE, I thought this was a WordPress question?
If I made new product pages with DIVI everything would probably work but some information would have to be stored outside WooCommerce.
On this page: https://www.xactnodbelysning.se/produktsortiment-nodbelysning-ups/nodbelysning/med-piktogram/shapeled/
I have tabs, not only for decription and more info. I also have tabs for accessories and so on. That information is all stored within the WooCommerce product page using Custom Product Tabs for WooCommerce.
Now, I could use DIVI’s own tab-system. But then it would be smarter to skip Custom Product Tabs and store the additional info directly on the individual page.
BUT!! 😊 If I ever decide to change my template, it would be safe to say that some information would get lost. Therefore, If I keep the info within WooCommerce I have a chance to change template and still keep all the information. At least I think that’s how it works?
Now, WooCommerce just uses the text fields provided by WordPress, as I see it. Hence, they use TinyMCE but aren’t really responsible for making TinyMCE better. Correct?
Of course, there might be changes to WooCommerce further on that are more block friendly.
I’ll just keep on trucking and wait for someone smarter than me to come up with a solution.`
Well WordPress didn’t make TinyMCE either 🙂
I know.
I’ve never used the TinyMCE-editor outside of WordPress, though.
Did WordPress perhaps implement the ability to switch between visual and text mode?
Or do you know if that feature also exist inside the TinyMCE-Editor in itself?
Switching between modes is when the code disapears.
Maybe I should start to poke Tiny instead? 😀
