Hi folks,
Just want to bring this to your attention. The new backend interface for Divi, coming soon.
hidden link
Any ideas if this will cause problems for how we make content templates etc?
I know that Marine Larmier on your team has indicated that it isn't alway easy for the team to liaise with Toolset.
Well, Content Templates, however you edit them, will output that data you add.
It's just an editor, a Codemirror instance that produces what you input to the assigned content.
If you start to build a Content Template with a Tool that somehow allows you to add (whatever) content, if that content is WordPress ready, and in form of HTML or ShortCodes (+ the added JS and CSS)... I see nothing that can break.
Of course, if things do break, feel free to report them.
Related to the specific discussion which is about Toolset/DIVI and WooCommerce, we ourselves to allow Customization of WooCommerce Products and Archives.
Here the same rules apply as elsewhere.
If your content matches the criteria it'll be used.
Surely, issues might come up with race conditions of scripts or similar things, but as said, if you stumble over problems that are due to Toolset feel free to communicate them to us so we can have a look
We are always eager to work with other Teams and we as well work with DIVI people 🙂 as both parties time and workload allows.
Thanks Beda for the feedback on that. Makes sense what you are saying. I will keep an eye out for any odd behaviour and will, as usual test the upcoming updates on a local site. Hopefully the REACT implementation of the back end won't cause any problems.
