Skip Navigation

[Résolu] content template columns not being honored

This support ticket is created Il y a 1 année et 1 mois. 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.

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
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Karachi (GMT+05:00)

Ce sujet contient 4 réponses, a 2 voix.

Dernière mise à jour par Waqar Il y a 1 année.

Assisté par: Waqar.

Auteur
Publications
#2660425

I am trying to: use columns in block editor for a content template

Link to a page where the issue can be seen: site under development

I expected to see: content in columns

Instead, I got: content is stacked.
site is using divi theme.

#2660859

Hi,

Thank you for contacting us and I'd be happy to assist.

Are you seeing any error or warning in the browser's console or in the server's error log?
( ref: https://wordpress.org/documentation/article/debugging-in-wordpress/ )

To troubleshoot this, I'll suggest the following steps:

1. Please make sure that WordPress, active theme and plugins are all updated to the latest versions.

2. It would be interesting to test this with all non-Toolset plugins disabled and a default theme like Twenty Twenty-One.

If it's fixed, you can start adding the disabled items, one-by-one, to narrow down to a possible conflicting one.

3. In case the issue still persists, I'll need to see how this content template and the Divi theme are set up in the admin area. You're welcome to share temporary admin login details, along with the content template's name.

Note: Your next reply will be private and making a complete backup copy is recommended before sharing the access details.

regards,
Waqar

#2661093

Thank you for sharing the access details.

I noticed that the content template 'test' is currently assigned to the post type 'Artworks'. This template is built using the blocks (Gutenberg) editor, but inside there is a Divi layout, which is showing the content in two columns.

Generally, it is not recommended to mix the content created in different page builder or editor environment. For example, if your website is using the Gutenberg as the primary editor, the Toolset's content templates, archives and views can be created using the blocks editor.

But if you prefer classic/legacy editor or a third-party page builder like Divi, then classic editor should be used for the content templates, archives and views.

Your website also has the 'Disable Gutenberg' and 'Classic Editor' plugins active. The purpose of these plugins is to restrict or limit the use of Gutenberg blocks-based editor. That would explain, why styles of the blocks-based template are not loading correctly on the front-end.

So, I'll recommend choosing the primary editor for your website and then structure the inner content templates, accordingly.

#2661119

the test content template was a test suggested by Divi. Disabling Disable Gutenberg worked! In the past having it enabled has not caused this issue. Do I have to go through ALL of my sites to disable it, or will toolset be making any changes so that it is consistent with the past and continues to display columns properly in blocks content template? Thanks.

#2661567

Thanks for the update and glad that it is sorted now.

I'm afraid, I can't say for sure exactly what changed, that resulted in you experiencing this issue now and not earlier.
( Toolset's recent updates don't include any changes specifically around this )

From the release of Toolset Blocks, Toolset's blocks-based elements are designed to work with the Gutenberg editor and it's environment. So any code or plugin that disables or limits the Gutenberg editor, would automatically affect the Toolset's blocks-based elements too.

For any other website too, where you'd like to use the Toolset's blocks-based elements, the 'Disable Gutenberg' plugin will need to be deactivated.