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 |
|---|---|---|---|---|---|---|
| - | 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 | - |
Zeitzone des Unterstützers: Asia/Karachi (GMT+05:00)
Dieses Thema enthält 4 Antworten, hat 4 Stimmen.
Zuletzt aktualisiert von vor 2 years, 1 month.
Assistiert von: Waqar.
How I identified the Toolset Block plugin responsible for the bug :
- I deactivated all the plugins and reactivated them one by one, only to find that it was Toolset Block that was creating the bug.
I am trying to:
- access a back office page containing dynamic toolset blocks (images, container, grid...)
Link to a page where the issue can be seen:
- it's in the back office -> "Pages" => "Nos experts"
I expected to see:
- access the content page with blocks and be able to make modifications
Instead, I got:
- a blank page with errors in console.
N.B : the front office of this page works
Console Error :
