YAFLogo

Posted by: mhoweson - Sunday, 31 January 2016 23:25:26
We've recently upgraded to use 2.2.2, from 1.9.3, and noticing what seems to be an anomoly. On the team page, the list of administrators displays administrators for the current board, however the list of moderators appears to show moderators from all boards. I would expect the list of moderators only to include moderators for the current board. We have multiple boards setup, each with their own userbase, and only one host administrator. Is this a bug that other boards can see the moderators of other boards, or am I missing something. Is there a way we can hide the team link from the top menu, as not sure it is needed for us at all. Thanks

Posted by: tha_watcha - Monday, 1 February 2016 18:58:19
In the Host Settings under Host > Host Settings > Display there is a Setting [b]Show Team Page[/b] where you can enable or disable the team page. Next i look in to the problem with the moderators.

Posted by: mhoweson - Monday, 1 February 2016 23:40:30
Thanks for the reply, much appreciated. Unfortunately I have already tried the show team option, it is set to forbidden. This doesn't appear to have any effect, the link in the menu still shows, and the page displays when accessed through the link in the menu.

Posted by: tha_watcha - Tuesday, 2 February 2016 13:30:54
If it's set to forbidden it's only visible to admins and host user.

Posted by: mhoweson - Tuesday, 2 February 2016 13:35:06
Thanks, OK I see, however that doesn't resolve the issue. We want to ensure it is never shown as it lists moderators from all boards. An admin for Board 2 should never see moderators from Board 1, they should run completely separately.

Posted by: tha_watcha - Sunday, 28 February 2016 14:44:41
[quote=mhoweson;66586]Thanks, OK I see, however that doesn't resolve the issue. We want to ensure it is never shown as it lists moderators from all boards. An admin for Board 2 should never see moderators from Board 1, they should run completely separately.[/quote] Yes this is definitly a bug. This will be fixed in YAF 2.2.3