ACP Permissions

[bwyatt]

I use ACP Permissions and have struggled for a while trying to find out why my co-admin can't update the chat settings without getting a permission error. Turns out that, after pressing Update Settings, it briefly goes to the Tools & Settings page and then returns to the main chat page.

That means I have to give my co-admin permissions to change settings in general, and I don't want that.

Any chance of some chat-specific permissions for the next release? I posted this as a ticket thinking it was an error, but it's the way it works. It was suggested I post this here to get feedback from the developers (by an IPS support agent with one of the best names ever: Giuseppe Casagrande!)

Thanks.

[bfarber]

This is, unfortunately, a limitation of IPB's settings APIs in general. This isn't specific to IP.Chat.

[bwyatt]

I see.

Any chance a fix for this limitation is in the works for 3.2 or whatever?

[bfarber]

Honestly, it's a lot more difficult to fix than it probably seems on the surface. All IP.Chat is doing to show the settings there is loading up the IPB settings file, and telling it to create the form. Then, after form submission, it asks IPB to send the user back to it's own page, rather than the (same) page in the IPB settings area.

So that form submission is still going to IPB (not the IP.Chat controller), and that's why the user needs permissions there. It would probably take quite a bit of effort to change that, and I've not yet seen a lot of demand for such functionality to date.

[bwyatt]

Perhaps something can be done at the ACP permissions level? So say I allow someone to manage settings for IP. Chat, it would also transfer that permission to Edit Settings for that application. I'm not expecting this now or even soon, but could it be considered/put on the drawing board for 3.2 or something?

[bfarber]

It's something we should look into in a future version.