error_nopermission hook issue

[dionak]

I have vb integrated into a site with a single sign-on. My logic handles the authentication portion and I have setup a plugin using the error_nopermission hook to redirect a user to the site login page . The issue I'm seeing is that sometimes, but not always, this plugin is being triggered when a user is logged in and trying to reply to a thread or post a new thread.

The use is logged in. Their name appears at the top of the vb interface. It's just when they try to post, it triggers the error_nopermission plugin. Seems odd.

The issue this causes is that the user is redirected to the custom login, which then detects the user is logged in. Once it detects this, it redirects the user to their account page.

We're using VB 3.6.1. Is anyone else using this hook and have you noticed anything similar to this? For instance, the hook being triggered when you are logged in?

Also, how does the Execution Order effect this? I am not familar with the context of the Execution Order although I understand fully the term.

Thanks.

Diona

[Paul M]

What exactly is odd ? - Logged in users will generate no permission errors, just the same as guests, if they try to do something they don't have permission to do.

[dionak]

But why would they not be allowed to post? We're also seeing them able to post sometimes and not at other times. All users are part of the Registered Users group. This group has permission to create threads, post, etc. The forum permissions are all set to allow posts and new threads for Registered Users.

Is there an easy way to output the reason for the error and why permission was denied? (thinking aloud)

[Paul M]

Closed threads would be one example I believe.

There is no way to output a reason - the no permission error is a generic error used in many (many) places.

[dionak]

The threads were open. I wondered if it the error_nopermission was being called incorrectly. I guess if it's not a 'known issue', it could very well be a settings issue somewhere down the line. I'll need to keep looking.

Thanks, Paul.