Skip Navigation

[Résolu] Again! Layouts Content Window doesn't work anymore!

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.

Marqué : 

This topic contains 2 réponses, has 2 voix.

Last updated by dianaM-4 Il y a 4 années et 9 mois.

Assigned support staff: Luo Yang.

Auteur
Publications
#473332

There is my last thread to this problem:
https://toolset.com/forums/topic/layouts-content-window-doesnt-work-anymore/

Minesh helped me out by updating all Toolset components. That worked for me for a little while. But now the exact same problem is back again! Perhaps with my last CRED-update? Just looked for new updates, nothing in the line. So what to do?

As I mentioned in the other thread: I disabled all plugins, switched back to the Toolsets Template, tried in different browsers – no success.

Please for help! That drives me nuts. Can't work with Layouts in the meanwhile!

#473799

Luo Yang
Supporter

Languages: Anglais (English ) Chinois simplifié (简体中文 )

Timezone: Asia/Hong_Kong (GMT+08:00)

Dear diana,

This problem should have already fixed in the Layouts plugin 1.8.7, and the latest version of Layouts plugin is 1.8.10, see similar thread:
https://toolset.com/forums/topic/css-not-working/
and the errata
https://toolset.com/errata/select2-instance-not-reload-data-iframe/

please check these in your website:
1) you are using the latest version of WP-TYPES plugins, you can download it here:
https://toolset.com/account/downloads/
2) deactivate other plugins and switch to wordpress default theme, and test again

#474505

Dear Luo,
thanks for the info. I already had the latest versions of all plugins. And I already tested it without all the other plugins and your Toolsets standard template. Didn't help me.

But now I followed the instructions on your enclosed errata and that worked out for me. Couldn't see a change in the code but saved it anyway. And now it works again.

So thanks again!