Access plugin - html status codes

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 – 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/Hong_Kong (GMT+08:00)

This topic contains 1 reply, has 2 voices.

Last updated by Luo Yang 1 year, 8 months ago.

Assisted by: Luo Yang.

Author

Posts

February 24, 2023 at 10:05 am #2560699

svenA-3

Tell us what you are trying to do?
I currently work on setting up custom error pages on my CloudLinux7 OS server running Apache and as add-on Litespeed webserver. On the webserver level I have managed to set up .htaccess to re-route to my custom error pages. For wordpress I use a custom filter on wp_die_handler.

What do I observe?
Calls for pages that are limited to logged-in users should end up in a 401 error. I get 404. Today I've set up a guest group in Access in order to handle native WP pages. Before these weren't managed by Access and at least I got a 403 on the described situation (which is faulty, too, as it should be 401).

What do I need to know?
Does the Access plugin - generally speaking - route unauthorized users to 404 for whatever reason? If so, is there a toolset filter I can use to change that behaviour?
At the moment, a general insight in how Access triggers or deals with access permission related errors will suffice.

Hint: yes, all custom error pages have been made accessible for guests in that Access group.

What is the link to your site?
hidden link

Kindest regards,

Sven

February 27, 2023 at 8:59 am #2562171

Luo Yang

Hello,

There isn't such kind of built-in feature, Toolset Access plugin can not return 401 error, and there isn't built-in filter hook to change it:
https://toolset.com/documentation/programmer-reference/access-api-filters/

You can add a feature request, our developers will evaluate it:
https://toolset.com/home/contact-us/suggest-a-new-feature-for-toolset/