Skip Navigation

[Resolved] CSS not working

This support ticket is created 7 years, 6 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.

Sun Mon Tue Wed Thu Fri Sat
- 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 -
- 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 -

Supporter timezone: Europe/London (GMT+01:00)

This topic contains 23 replies, has 6 voices.

Last updated by Daniel 7 years, 5 months ago.

Assisted by: Nigel.



Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+01:00)

I've pinged the developers asking for an update and will update you here when I hear back from them.

Thanks for your patience.


Any updates on this Toolset Layouts issue? We haven't heard anything in almost a week...



Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+01:00)

The problem has been fixed and the fix will be included in Layouts 1.9.

There are too many affected files for a simple patch and so a hotfix is being prepared and should be available soon, and I will update here when it is.

Thanks for your patience.



Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+01:00)

The fix has been published as a Layouts update to version 1.8.6

Keep an eye out for an update notification on your plugins page.

If that doesn't appear or you don't want to wait you can download the zipped plugin file from your downloads page ( You can use the Upload button on the Add New Plugins page to add the zipped version of Layouts to your site, but that requires deleting the old plugin first.

If you have FTP access you can upload the unzipped file to your plugins folder and overwrite the old plugin version.

Please re-test the issue and let me know if you have any continuing problems.


If I may enter the discussion.

I was looking forward to the 1.8.6 update, since I am having the same problems.
Unfortunately it didn't solv the problem.

I attach a class to a row/element, save it, want to enter another element and get the classes shown from the element before that.

Besides other issues like getting a drop down instead of a text field to enter classes with a handful of classes in the dropdown but no possibility to add one I haven't used before.

So it is still broken for me. This is a huge issue to be honest. I will now try to rollback the layouts version until this issue is solved


Furthermore I get the message

The toolset_select2('destroy') method was called on an element that is not using Select2.

in the chrome console



Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+01:00)

Hi Lars

Could you double-check that you have updated the plugins?

I just set up a fresh WordPress test site with the latest versions of Types (2.2.2), Views (2.2.1) and Layouts (1.8.6) plus the twentysixteen integration plugin which generated the basic layouts.

I edited the layout for posts and added two rows, to which I added a series of classes (test-1-a, test-1-b etc. to the first row and test-2-a, test-2-b etc. to the second row).

I saved the layout, viewed the hello world post on the front end and inspected the source and the classes were correctly added.

I went back in and edited the rows in the layout and the classes were there as expected.

I repeated to double-check, and I couldn't find the problem.

If you are still having problems, please open a new thread so I can deal with you directly there (you are welcome to assign the ticket to me when you do).



Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+01:00)

This is hopefully the last update for this issue.

If you are still experiencing any problems please see this errata and apply the patch described there:

The select2 jQuery library is so deeply embedded in Toolset, updating the version proved quite the headache, and we thank you for your patience.



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