Skip Navigation

[Resolved] Issues between Divi and Toolset integration

This support ticket is created 6 years, 7 months ago. There's a good chance that you are reading advice that it now obsolete.

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.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 10:00 - - - - -
- - - - - - -

Supporter timezone: Africa/Cairo (GMT+02:00)

This topic contains 36 replies, has 8 voices.

Last updated by alberto 6 years, 1 month ago.

Assisted by: Mohammed.



Please tell us here what issues you found or missing features in the integration between Divi theme and Toolset.

If you are talking about Divi child themes or addons, remember to explain what you are using and link to it. Include screenshots of the settings that you want Toolset to control and explain how you will use these settings in the sites that you build.

This explanation will help us build it exactly like you need. Thanks!



Just set-up a new test site to tryout the Divi and Toolset intergration

Unfortunately on loading the wp-views.2.5-b2 plugin, I get the following message:

Fatal error: Arrays are not allowed in class constants in /home1/######/public_html/###/wp-content/plugins/wp-views/vendor/toolset/toolset-theme-settings/compatibility-loader/toolset-theme-Integration-settings-collections-factory.php on line 16




Timezone: Europe/Madrid (GMT+02:00)

Hi Dave

Thanks for the feedback.

Yes, it seems that we left some code that requires a minimum version of PHP (at least 5.6) to run properly. I will fix it and eventually push for another beta, for both Views and Layouts. We are commited to support some older versions too, so this is indeed a bug.

In any case, and as a general comment, the whole WordPress community is starting to push to get sites on a modern PHP version. PHP 5.6 was released on August, 2014, and official, security support for older versions ended last year. It would be a good idea to contact your hosting and get some information about their upgrade plans, if any.

Thanks again.


Hi Amir,

I tested the new betas and while the implementation is a good solution for many themes, it is, as I have already said in earlier correspondence to you, redundant for me when it comes to DIvi. The main hurdle is introducing fullwidth sections into the layouts. What follows is an overview of some research and feedback that I recently sent to Elegant Themes.


Below are some observations and suggestions how best to implement layout templates in conjunction with custom post types. This is a long post but please do bear with me as I do cover some user experience, as in the experience for me as the developer.

Custom Post Types have been flagged by Nick as part of the roadmap for future development of the Divi theme.

Use the following page for reference ( I will refer to it as print post ):

hidden link

I am using Toolset Types suite of plugins to create a custom post type and custom fields for my prints catalogue.

Instead of using Toolset’s Layout plugin I opted to use the Divi sections, rows and modules directly, for reasons I will explain shortly.

To make Divi builder work on custom post types I used the Divi Booster plugin.

For the most part, the layout that I use is global and applied to all the custom post types for prints in my catalogue. I load it from the Divi Library each time I add a print post to the site and is saved as locked as a reminder not to edit directly what is in the layout. All relevant information relating to the print is entered into custom backend fields in the post editing dashboard. These are located below the divi builder.

The layout is configured as follows.

The top part, showing the image and text to the left (on desktop) I put the shortcode for the featured image in the left text box and the shortcodes for the title, price, edition size and print description in the right text box. These shortcodes represent the custom fields I made with Toolset Types and Views. Note with the View plugin you can now create a template or templates for these field layouts and (new to views) put a shortcode for the whole template into a Divi text module.

The middle section is made up of a filtered archive view of prints for the related year. This is view is generated with Toolset Views and introduced as a shortcode. This part of the layout is not global because for each year grouping I manually change the shortcode for the years relating to the main print in the post. To the right of this I have a sidebar made up of the search module and links to archives based on the categories for landscape, portrait, small, medium and large.
Below this I have an archive of the years in button format.

Finally, the bottom section is made up of a gravity form. Again introduced by shortcode. One form does all print posts and are differentiated by the post title shortcode:

<h3>Enquire About [wpv-post-title]</h3> = Enquire About Surlvol

The email notification generated when a form is sent is formatted with the same shortcode to state that an enquiry has been sent from the specified print post.

NOTE: the Divi contact module cannot do this. It would be good if it could!

I used this approach because building the layout with Divi modules this way is by far the easiest and most rewarding way to do so. There is a bit of work with CSS to prepare the general page container but once this is done things work nicely. I suspect that in the future when custom post types are introduced to the Divi theme, this step will not be required.

Toolset has had several iterations of their Layouts plugin for this purpose but they don’t quite fit into how pages can be structured with Divi. For example, with Layouts it is very difficult to implement the full-width sections like I have done with DIvi, where the sections can be coloured across the full width of the browser. Toolset is about to release a new implementation of the Layouts plugin but I don’t know how well this will compare to what I can do with Divi or how well the integration of Toolset into DIvi will ever be. That all depends on how much collaboration there is between the teams from Elegant Themes and Toolset.

There are other things you can do with the Divi builder. With the Divi, sections, rows and, columns in those rows, you can add flexbox rules to control where items appear responsively across the full range of viewports.

Moving on: how layouts are applied to custom post types. I already mentioned the Divi Booster method I used for custom post types. An alternative approach is to use Sean Barton’s layout injector plugin which configures the option globally for the custom post. This works but I prefer the Divi Booster approach because it opens up the possibility to work with a choice of different layouts. Plus you can unlock and disable global on an ad hoc basis where an alternative layout style or configuration is required. Need to return a post to the global layout? Just clear and reload from the library. There is just so much more flexibility with this approach. From what I remember Sean Barton's solution is designed to work with the Advanced Custom Fields plugin.

There are some drawbacks with my Divi Solution.

A number of months ago Elegant Themes changed how the global feature worked by implementing global sync. All in all this works very well and is quite intuitive. But, the global property is only applied to sections, rows and modules and not a full layout for a page or post. This defeats the concept of global templates. For example taking my print post again:

hidden link

Say in the initial build of this website I only included the sections down to my section for year buttons. Then several months later I decide I want to introduce an enquiry form sitewide for all print posts. I can make the section for this global, perfect. But, when I add it to the layout either on a print post or, to the layout in the Divi Library, it is not added globally to all the print posts. This means I have to add this new section individually to all 199 print posts in my catalogue.

The global option needs to be brought back to Layouts in Divi.

The next suggestion/observation: Defaults.

I mention that when a new custom print post is created I must load the layout I want to use from the Divi Library. This is not so bad. just an extra step or two in my workflow. But if I build a site for a colleague or client, not as adept in the ways of site development, I want to make the experience as pleasant and simple as possible. Sean Barton’s layout injector in a way does this, but I want the flexibility offered by my Divi booster solution.

Lastly. Toolset is quite sophisticated in how it implements custom fields and custom post types and quite frankly indispensable when it comes to serious work developing for custom post types.

Types and Views offer such features as repeating fields whereby users can repeat the the field in the backend and front end to bullet list events in an itinerary which are then consistently styled by the developer in a pre formatted layout template on the front end. Toolset Types allows for parent/child post hierarchies. And Views allows the developer to introduce filtered archives into page layouts with shortcodes. Trying to emulate and match all the hard work achieved by the Toolset Types team would be a big ask so I hope that Elegant themes work to allow Toolset plugins to play well with Divi into the future.

I hope what I have outlined will give insight into how to implement new features concerning custom post types and layouts in the future.


In the last few paragraphs I talk about how powerful the Toolset suite is and implied in this is a hint to Elegant These not to go head to head with Toolset. Preferably I would like to see Elegant Themes set up Divi to integrate with the custom post types created by Types. In this way perhaps Toolset could create Divi modules for templates and viiews that we could add to the layouts with Divi Builder.

I will post a screenshot below of the back end of my print page example.


Backend layout with Divi


Thanks for the reply.


Hi Amir,

i installed the beta of Layouts and Views. Now i got in the Header of Layout a Message for "The divi-social-icons cell type is no longer available.<br> (Make sure that the cell type is available and that you have the required user permissions to handle that cell type."

How can i fix it? Is it wrong? I use the Divi Release 3.0.76.

Thanks for an reply. alex



I uploaded the Layouts beta for DIVI theme but I still could not see the "Theme Options" as described in the video demo. Did I install it wrong? I renamed the old "layouts" folder to "layouts-old" and upload the new "layouts" folder from the beta version and then activate the plugin. Please let me know. Thank you.


Thanks @stephen for all the information you've provided, I will escalate them to the management to take the best action.

@alex and @Kan I'm working on your issues now. please wait and I will get back to you ASAP.


Edit layout ‹ Replicate — WordPress - Mozilla Firefox 2017-09-27 12.50.20.png

Hi Alext,

The new integration works in a different way. You have the control over the theme options and setting and by doing this, you will be able to change how it looks in addition to the features that Layouts offer.

For the Social icons, you can control them in your Layout by showing or hiding them in the seetings available under the Layout itslef in the Layout editing screen.

Please check the attached screenshot.




Stephen, your explanation helps very much.

We're trying to push an update to Views 2.5 (the upcoming version), which will allow you to edit Content Templates with the Divi editor. This way, you can let Toolset manage template assignments and design inside with the Divi builder.

I bet that this will be a step forward, but probably will leave some things unresolved. We too didn't find a way to just tell Divi to output full-width rows. I'm not an expert in Divi inner-working. As an outsides, it looks to me like a bit of over-engineering to go through the process that you described, just to get rid of the sidebar.

We're very happy to work with ElegantThemes team on complete integration. We want clients to get a good workflow with Toolset and Divi. The more ET clients request it from ET, the more likely this will happen.


Hi Amir,

That all sounds good to me. There are a few things that Elegant Themes need to resolve like making the layouts in the library global and not just the sections, rows and modules. In any event the 2.5 Views update may be a solution to all of these design issues and will obviate the need for over-engineered lengths that I have gone to. One way or the other it all sounds positive.

Screenshot 2017-09-26 11.58.20.png

@mohammed - no i mean other thing - here is a Screenshot


Hi @dave,

Can you please test the issue in the new Beta release Views 2.5-b3 and Layouts 2.1-b4




Hi all, I have been using the new Beta releases for Views 2.5-b3 and Layouts 2.1-b4. However, like I mentioned, for some reason, I could see the "Theme Options" section under the Layouts and Views with DIVI theme for me to make any changes. Did I install it incorrectly? Or, please let me know how to install the beta versions correctly or I have to turn on something to be able to see the "Theme Options" section. Thank you.

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.