Skip Navigation

[Closed] Toolset Access 500 error for non-administrators

This support ticket is created 2 years, 8 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)

Tagged: 

This topic contains 1 reply, has 2 voices.

Last updated by Waqar 2 years, 8 months ago.

Assisted by: Waqar.

Author
Posts
#2326555

When Toolset Access is activated, non-administrator user only sees 500 error.
I thought maybe it was a mixup between Access and WPMU DEV Defender Pro, since it requires 2FA, but the 500 error issue happens even when Defender Pro is not active and in a fresh browser.
When I disable Access, this non-admin user does not have the 500 error.
Oddly, I couldn't find any WP_DEBUG errors so I'm not even sure where to guess or point you toward.

Any known issues like this?

#2326601

Hi,

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

It is strange that no errors are available in the server's error log, despite error 500.

Is it possible that your host or CDN (Cloudflare) is showing the cached error 500 page to the non-admins? I'll recommend turning on WordPress debugging ( ref: https://wordpress.org/support/article/debugging-in-wordpress/ ) and checking again for errors in the log, after clearing all involved caches.

regards,
Waqar

The topic ‘[Closed] Toolset Access 500 error for non-administrators’ is closed to new replies.