Toolset Types disables block editor

This support ticket is created Il y a 3 années et 10 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.

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

Supporter timezone: America/Jamaica (GMT-05:00)

Marqué : Types plugin

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

Last updated by hugoC-3 Il y a 3 années et 10 mois.

Assisted by: Shane.

Auteur

Publications

juin 1, 2020 at 12:07 pm #1646401

hugoC-3

When creating or editing pages the block editor is not available; I can only use the classic editor. Editing posts with the block editor is no problem.

When I disable Types everything works well.

I also get this error message from the Site Health plugin: The REST API call gave the following unexpected result: (403) {"code":"rest_cookie_invalid_nonce","message":"Cookie nonce is ongeldig","data":{"status":403}}

What is the link to your site? hidden link

juin 1, 2020 at 4:04 pm #1646711

Shane

Supporter

Languages: Anglais (English )

Timezone: America/Jamaica (GMT-05:00)

Screenshot 2020-06-01 at 11.02.45 AM.png

Hi Hugo,

Thank you for getting in touch.

If you go to Toolset -> Post Types -> Pages ensure that the editor selection is set to the block editor. See Screenshot

This should resolve your issue.

Thanks,
Shane

juin 1, 2020 at 6:20 pm #1646815

hugoC-3

Very strange; the editor was already set to blocks but nevertheless it didn't work. I switched to classic ad then back to blocks and now it works.

My issue is resolved now. Thank you!

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