Now that we have a settings form it would be handy to have a checkbox to set the 403 page to the m4032404 callback. This can be caught in the admin form submit handler, if the checkbox is set then it calls variable_set('site_403', M4032404_CALLBACK); and then unsets the checkbox element in the $form_state['values'] array.
The menu callback string should be defined as a constant (M4032404_CALLBACK). Then where ever the value is used the constant should be used.
When the form is being built a variable_get call should get the value of site_403 and compare the value to the constant.
I don't currently have time to implement this change, but I'd welcome a patch for it.
Closed: outdated
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This does not seem relevant any longer.
D7 is no longer supported, and the D8+ version uses an event subscriber triggered on all 403 errors. The site_403 parameter is not used in this version, so there would not be a reason to include it in an admin form.
The site_403 path would only be used once these issues are merged:
🐛
User logout without CSRF token redirect to 404
Active
✨
Method to bypass redirection
RTBC