RE: 7.2 B2 - Compass Icon Misaligned / Dockbar now gone for Site Members

Lee Jordan, modified 6 Years ago. Expert Posts: 449 Join Date: 5/26/15 Recent Posts
Found using Chrome, Windows 10.

Of note ... very disapointing that site members have lost the control menu (dockbar), since that's where our branding and access to our help site and intranet apps link lives to have lost that is very sad. Our users even site members are always logged in and have always had the dockbar. We really can't just swipe that away like that emoticon
thumbnail
Dennis Ju, modified 6 Years ago. Regular Member Posts: 228 Join Date: 9/30/10 Recent Posts
Hi Lee,

The Compass icon misalignment is already fixed in master.

The appearance of the Control Menu is dynamic, meaning if there are controls in the Control Menu, it will still appear. The controls you added for the help site and app links should force the Control Menu to always be visible.

Can you reach out to me via email (dennis.ju@liferay.com) with further information on how you included the controls? I want to make sure the way we implemented showing/hiding the Control Menu supports your use case.
Lee Jordan, modified 6 Years ago. Expert Posts: 449 Join Date: 5/26/15 Recent Posts
It doesn't support our use case, we would need a configuration toggle to revert the functionality back to how it is in 7.0/7.1 so that the dockbar was always displaying for "logged in users". We're adding our "portal branding" into the control menu next to the toast (product menu [  ]  icon) so removing that chrome wipes out our indentiy to non site admins. We have about 1,000 site admins and the potentital of 250,000 non-site admins.

This change wipes out our idenity to a quarter of a million users. I understand that the user menu was moved to the user icon and that negated the need for the product menu to exist but this ignores our use case and removes chrome. This change won't be forced on Enterprise Edition will it or can Enterprise Edition keep the chrome for all logged in users.

Example of what is lost attached ...

Attachments:

thumbnail
Dennis Ju, modified 6 Years ago. Regular Member Posts: 228 Join Date: 9/30/10 Recent Posts
Just restating what I replied over email for reference for the community:


The Control Menu was always intended to be a toolbar for configuration, not a global navigation menu. This is what drove the decision to dynamically show/hide the Control Menu, as it didn't make sense to show an admin-oriented toolbar for non-admins. The only reason it was visible in the first place is because the user's personal menu was in the Navigation Menu (which also didn't make sense and was moved in 7.2). 

So as long as you're using the supported framework for adding/customizing the Control Menu, the Control Menu will be visible as long as users have permissions to view at least one custom control. If you're not using the framework and injecting custom code, the simplest workaround would be to add an empty Control Menu entry. You can quickly create one using this blade template.
Lee Jordan, modified 6 Years ago. Expert Posts: 449 Join Date: 5/26/15 Recent Posts
Liferay had from November to now to ask users how this would affect them ... a feature flag would be the best approach so that users who need the dockbar visible can enable that without customization.

---

https://issues.liferay.com/browse/LPS-87868
Move the Personal menu out of the Product Menu and provide a non-admin look & feel to the Personal Applications