nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Cannot see groups in Manage User Groups

colindstephenso

Hey All,

I recently upgraded my test server from 3.2 to 3.3.1. The upgrade went well, except for one thing. Now I can no longer see the groups under Manage User Groups. They exist but I cannot see them. And I am logged in as admin. Any thoughts?

Thanks,
Colin.

Find more posts tagged with

Comments

dward

To be visible in the UI, groups need to exist in spaces store not only under sys:system/sys:authorities but also sys:system/sys:zones/APP.DEFAULT. Browse to your authorities (groups) in the node browser and check their parent associations. This would not be a problem with groups created through AuthorityService.

Groups that correspond to internal groupings such as sites have been excluded from this zone intentionally and are managed elsewhere in the UI.

colindstephenso

These groups where created in the DM via the Admin Console in 3.2. All the links are there, but I will need to see if parent associations have gotten messed up during the upgrade.

Thanks

colindstephenso

I upgraded another 3.2 system to 3.3 and all groups previously visible through the "Manage User Groups" are no longer visible. They all exist and i can see them through the suggested spaces. Is there a property or an association I need to correct after the upgrade?

dward

Could it be to do with the display name property of the groups. Can you paste in a dump of a typical group from the node browser?

colindstephenso

Before I do this, I tried the upgrade process again, only this time following the Upgrade Wiki - http://wiki.alfresco.com/wiki/General_Upgrade_Process#Target:_Version_3.3 - and this solved my invisible groups issue. previously I had performed an in place upgrade which was probably not the best thing to do.

I can post the other details should you still want to see them,

regards,
Colin.

lboschi

Hi, I met the same problem and resolved deleting tomcat/work/* and tomcat/temp/*.
http://forums.alfresco.com/en/viewtopic.php?f=14&t=28765&p=93930#p93930

Cheers,
Luciano