Today, I tried upgrading from version 16.10.4 to version 16.10.5 and noticed a couple of strange changes.
The first issue is that when I remove my user (the one created after logging in via OIDC, not the built-in admin) from the XWikiAdminGroup, all pages start displaying like the screenshot for all users. However, if I add my user back to the XWikiAdminGroup, the pages display correctly for other users. Do I need to log in as the built-in admin and manually fix every macro to resolve this?
The second issue is with the User List macro: after the update, all users in this macro are displayed as shown in the screenshot, and this happens for all groups displayed in the macro. Does anyone know what could be causing this?
Concerning 1st issue you shouldn’t remove user from XWikiAdminGroup so easily, the best approach either to deactivate that user or to replace him with another user that has same rights.
Concerning 2nd question, it seems that warning message that you see, comes from paid extensions (to be precise User Reference List macro). Remember that this forum is for the xwiki.org community and is not the best place for support with paid apps from XWiki SAS. If you’ve purchased the extension, your license includes a support contract for professional help.
Regarding the first issue, I didn’t encounter this problem in previous upgrades (I upgraded to 16.10.2 and 16.10.4 without any issues). However, after upgrading to 16.10.5, I noticed that the old XWikiAdminGroup was gone, and a new XWikiAdminGroup was created without any users. The issue persisted until I added a specific user to this new group. Replacing this user would be quite difficult because our XWiki instance is large, and such a change could disrupt operations across departments.
As for the second question, thank you for pointing that out. I wasn’t aware that it was a paid extension from XWiki SAS and not a built-in one. I’ll reach out to them for a solution.
If you know and are sure that on previous upgrade, you didn’t have issue and on recent one it raises then you can report it on Jira with detailed prerequisites (including OIDC extension) and steps which lead to issue.
