Skip Navigation

[Resolved] Editor freezes for Toolset Access on WordPress 5.6

This support ticket is created 3 years, 9 months ago. 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.

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)

This topic contains 3 replies, has 2 voices.

Last updated by Waqar 3 years, 9 months ago.

Assisted by: Waqar.

Author
Posts
#1941279
screenshot.png

The post editor freezes on the pop up screen "Welcome to the block Editor" when Toolset Access is activated on WordPress 5.6 and above. I'm unable to exit the pop up, check the console, look at the html or anything. Seems to be stuck on some kind of infinite loop. This also only happens when I'm logged in as a user role that is not an administrator. If i'm logged in as an administrator it works fine.

The only other plugins installed are Toolset Types and ACF, but the issue only occurs when Access is activated.

#1941959

Hi,

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

I've performed some tests on my website with an "editor" role user, but couldn't reproduce this.

Can you please share temporary admin login details along with the access details for a non-admin user?

Note: Your next reply will be private and please make a complete backup copy, before sharing the access details.

regards,
Waqar

#1946697

Looks like this is a WP 5.6 issue that's been reported here: hidden link (Editor freezes when current user role doesn't have 'edit_posts' capability)

Probably important to note for other users using custom roles/capabilities using the Access plugin.

#1948721

Thank you for sharing this and it will surely help other users too.

I'll pass this on internally too and you're welcome to mark this ticket as resolved.