Navigation überspringen

[Zugewiesen] Fields & Text block is unusable in the back end

This support ticket is created vor 3 days, 6 hours. 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.

Dieses Thema enthält 2 Antworten, hat 1 Stimme.

Zuletzt aktualisiert von cristiD vor 10 hours, 41 minutes.

Assistiert von: Christopher Amirian.

Author
Artikel
#2865262
Screenshot 2026-06-17 104805.jpg

I am trying to: edit the contents of Fields & Text block

Link to a page where the issue can be seen: the problem is only visible in the backend

I expected to see: the editor of the Fields and Text should load normally

Instead, I got: the contents & editor of the Fields and Text block is not visible

In the screenshot you can see a Fields and text bloc is selected, but the neither the contents or the editor are visible.

#2865270

Christopher Amirian
Unterstützer

Sprachen: Englisch (English )

Hi,

Welcome to Toolset support. Would you please follow the steps below?

- IMPORTANT STEP! Create a backup of your website. Or better approach will be to test this on a copy/staging version of the website to avoid any disruption of a live website.
- Go to "WordPress Dashboard > Plugins > Add new > Commercial (tab)".
- Click the "Check for Updates" button.
- Update Toolset and its addons there.

After that, test if there is a possible plugin conflict:

- IMPORTANT STEP! Create a backup of your website. Or better approach will be to test this on a copy/staging version of the website to avoid any disruption of a live website.
- Go to "WordPress Dashboard > Plugins" and deactivate all plugins except:
. Toolset Types
. Toolset Blocks
- Check if you can still recreate the issue.
- If not, re-activate your plugins one by one and check the issue each time to find out the plugin that causes the problem.

#2865736

hi, disabling the plugins did NOT fix the issue

what else can we do?