Ce fil est résolu. Voici une description du problème et la solution proposée.
Problem:
divi_cpt_layout_injector Plugin does not print the new (
{!{shortcode}!}) syntax of Toolset shortcodes, but need the old
[]
Solution:
This is solved in the latest divi_cpt_layout_injector plugin version
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
Aucun de nos assistants n'est disponible aujourd'hui sur le forum Jeu d'outils. Veuillez créer un ticket, et nous nous le traiterons dès notre prochaine connexion. Merci de votre compréhension.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| - | - | 14:00 – 20:00 | 14:00 – 20:00 | 14:00 – 20:00 | 14:00 – 20:00 | 14:00 – 20:00 |
| - | - | - | - | - | - | - |
Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)
Ce sujet contient 13 réponses, a 2 voix.
Dernière mise à jour par Il y a 6 années et 7 mois.
Assisté par: Beda.
Hi Beda,
thank you for your detailed reply...
I understand what you're trying to tell me about how you would use Toolset in combination with Divi. But to be honest... that simply doens't work the way it should.
Toolset Content Templates aren't loaded the way Divi loads the Divi Builder Layouts. Please have a look at the attached images.
I'm a Toolset user for many years and love your product. I'm also a Divi user since its first release. I've been combining Divi and Toolset from day one. I love the combination. With the Toolset supporting the use of the Divi Builder in content template, I was jumping up sky high / glad... but sadly it didn't work out as I was hoping. You can see the differences in the attached images.
In the past (when Divi was released, I would create Toolset Content Temaplates containing Divi Builder Shortcodes. Combined with custom single-{post_type}.php it worked out great. But as you probably can imagine it was a hell of a job when layout changes had to be made.
Then Sean Barton came up with the CPT Layout Injector. That was a huge time saver... As you can see, you use Divi Library Layouts. Even better, when you're activating the Page Builder in a custom post, it uses that design... when you don't enable the divi builder in the post... it uses the layout set with the CPT Layout injector.
So from that moment on, our projects could be finished in a much shorter time frame... a small change could be made in the layouts.
For some modules that needed settings from toolset, i would still create a toolset content layout and add the Divi builder shortcode in it.
When Toolset anounched the new short code structure... I was even jumping higher that last time... making a dance throught the office.. as you can image, it would be the time saver of the year. It would be possible to add Toolset shortcodes in the Divi Builder Modules. Think about image urls etc. But nope... it doen't work... 🙁
I directly discovered that the old shortcodes do work in the CPT Layout Injector... so that is how I'm still using it. But with every new project... I was sad... that it doesn't work as what I was hoping too...
So that's why I decided to open this topic...
Please have a look at the images, then you should directly see why I don't use the Toolset way..
INFO ON THE IMAGES:
builder layout.jpg --> this is the layout created with Toolset Content Template (use divi builder option)
Toolset Layout Settings.jpg --> the settings, there you can see i've chosen full width etc...
Toolset.jpg --> this is the output of the Layout.
What you can see, the layout is loaded within a container that isn't full width... it contains padding / margins on all sides.
CPT injector.jpg --> Output of the exact same layout, but now loaded using the layout injector. This is what an experienced Divi user would expect... full width... no margins / paddings around the sections etc.
Best regards,
Herre
Beda,
Thank you for your detailed response, however I have the feeling we won’t come to a solution as your point of view is fully focused on point “3. We do not suggest to use Divi and Toolset this way”
I’ve been a Divi user since it’s first release, have been using Toolset in combination with Divi from the first release of Divi. This works fine, can be managed with no problems at all.
I’ve been using the CPT Layout Injector also since it’s first release, as this simply saves a huge amount of time. This plugin handles the need of creating predefined Divi Layouts and use them as default on Post Types, but at the same time allowing the user to enable the divi builder for themselves and create a post using the Divi Builder. In other words, when not using the Divi Builder and simply adding a title, content and when present also post fields, these will be used with the standard Divi Layout set by the CPT Layout Injector.
But when the user activates the Divi Builder, then the default layout won’t be used. Then simply the Divi Layout created with the Divi Builder when creating the post will be used.
But I think you already figured this out.
This approach has been used in lot’s of my projects which I simply can’t change and there is no need for it to change… as like you already mentioned, the old shortcodes can be used. Although these can’t be used as Divi Module values en for those modules I still need to create Content Templates to output the desired content / look and feel.
Let me respond to your points:
“1. We have a number of BUGs with the DIVI theme integration.”
Indeed, and that’s one of the reasons I am not using this new functionality. There are simply to many issues to use it in our ongoing projects. The Divi settings are a great idea, but they simply don’t come near the wanted effect.
“2. There are style issues surging from how DIVI HTML is coded, we are aware of this, but cannot solve it right now”
Like I mentioned in the previous response, full width? Not working… Paddings (also with Toolset not loading Bootstrap) not as wanted. So that means lots and lots of custom CSS work which I don’t need at all when using my current work-around.
By the way, thank you for those topics, as I didn’t read them yet.
“3. We do not suggest to use DIVI and Toolset this way.”
Well the reason for my way of working is already mentioned at you own responses… There are BUGs with Divi Theme Integration… There are style issues how Divi is coded… well it isn’t how Divi is coded… it is how Divi / Toolset / Bootstrap is coded. There are conflicts on ID’s and Classes that both or even the three of them used I guess.
You already tried to push me in the direction of this process in an earlier response:
- create a CPT with Types
- create some CF's with Types
- create your Layout with the DIVI builder (use the new syntax)
- create a CT with Views
- edit the CT with the Builder
- apply the layout created with Builder previously to the Content Template (inserted from the DIVI library).
But as you know, this does not have the wanted output. Full width isn’t full width…
- there are additional unwanted margins / paddings…
- there are alsomissing paddings / margins missing
Please have a look at the attached images…
Image 1. Toolset.jpg
This is the output of your approach.
The Divi settings set in the CT are fullwidth and show no Title.
As you can see, it isn’t full with at all!! The blue section is still in the middle… ?!?
Also the padding above the blue section shouldn’t be there, even when the top and bottom margins of the blue section have been set at 0px. (while this shouln’t be needed at all, have a look at Image 2. Divi.jpg)
Image 2. Divi.jpg
This is how the post would look like when using the Divi Bulder on a Post…
Image 3. CPT Layout Injector.jpg
This is how the Posts looks when using my current approach , the CPT Layout Injector.
So search for the differences and you can guess why I use which approach….
I fully understand that a Toolset Supporter / Developer etc wants to push me into using the Toolset approach. But come on, you can’t be serious if you see these differences.
Hopefully you can forward my requests to the developers and maybe there will be a solution in the future. But I have the feeling we won’t come to the same level in terms of agreeing on the current approach / needed output.
REMARK: has there been a change in approach of enabling the new shortcodes? I created a new wordpress install to create these images and didn’t see the new shortcode structure… the old ones where being used. Latest Divi and Toolset Plugins were used.
Regards,
Herre
