/o//commerce-media/accounts/-1/images/18648322?download=true
Dockbar Integration
Identity Management & Governance
Descrição
The application adds a new custom permission called VIEW_DOCKBAR inside
the "General Permissions" section of the role configuration
(except for Guest role).
With this new custom permission, frontend developers can leverage the Liferay permission system to show/hide the portal dockbar inside a custom theme.
Here's how to initialize a Freemarker variable inside the init_custom.ftl file of a custom theme:
<#assign viewDockbar = permissionChecker.hasPermission(themeDisplay.scopeGroupId, "90", "90", "VIEW_DOCKBAR") />
And here's how to use the Freemarker variable:
<#if viewDockbar>
<@liferay.control_menu />
</#if>
On Liferay 7.4+ you need to add this property to your portal-ext.properties file in order to make it working:
resource.actions.strict.mode.enabled=false
With this new custom permission, frontend developers can leverage the Liferay permission system to show/hide the portal dockbar inside a custom theme.
Here's how to initialize a Freemarker variable inside the init_custom.ftl file of a custom theme:
<#assign viewDockbar = permissionChecker.hasPermission(themeDisplay.scopeGroupId, "90", "90", "VIEW_DOCKBAR") />
And here's how to use the Freemarker variable:
<#if viewDockbar>
<@liferay.control_menu />
</#if>
On Liferay 7.4+ you need to add this property to your portal-ext.properties file in order to make it working:
resource.actions.strict.mode.enabled=false
The application adds a new custom permission called VIEW_DOCKBAR inside
the "General Permissions" section of the role configuration
(except for Guest role).
With this new custom permission, frontend developers can leverage the Liferay permission system to show/hide the portal dockbar inside a custom theme.
Here's how to initialize a Freemarker variable inside the init_custom.ftl file of a custom theme:
<#assign viewDockbar = permissionChecker.hasPermission(themeDisplay.scopeGroupId, "90", "90", "VIEW_DOCKBAR") />
And here's how to use the Freemarker variable:
<#if viewDockbar>
<@liferay.control_menu />
</#if>
On Liferay 7.4+ you need to add this property to your portal-ext.properties file in order to make it working:
resource.actions.strict.mode.enabled=false
With this new custom permission, frontend developers can leverage the Liferay permission system to show/hide the portal dockbar inside a custom theme.
Here's how to initialize a Freemarker variable inside the init_custom.ftl file of a custom theme:
<#assign viewDockbar = permissionChecker.hasPermission(themeDisplay.scopeGroupId, "90", "90", "VIEW_DOCKBAR") />
And here's how to use the Freemarker variable:
<#if viewDockbar>
<@liferay.control_menu />
</#if>
On Liferay 7.4+ you need to add this property to your portal-ext.properties file in order to make it working:
resource.actions.strict.mode.enabled=false
var contentEl = document.querySelector('#mpProfile');
var tabPanel = contentEl.closest('.tab-panel-item');
var tabTarget = tabPanel.getAttribute('aria-labelledby');
var tabs = contentEl.closest(".component-tabs");;
var navLink = tabs.querySelector('#' + tabTarget);
var navItem = navLink.parentElement;
if (contentEl.textContent.trim() === '') {
navItem.classList.add('d-none');
}
<script>
var contentEl = document.querySelector('#mpProfile');
var tabPanel = contentEl.closest('.tab-panel-item');
var tabTarget = tabPanel.getAttribute('aria-labelledby');
var tabs = contentEl.closest(".component-tabs");;
var navLink = tabs.querySelector('#' + tabTarget);
var navItem = navLink.parentElement;
if (contentEl.textContent.trim() === '') {
navItem.classList.add('d-none');
}
</script>
DEVELOPER
Desenvolvedor
Publisher Date
January 24, 2024
Deployment Method
Liferay Self-Hosted
Liferay PaaS
App Type
DXP
Versão
1.0.0
Versões compatíveis
7.4
Standard Price
Free
Help and Support
Compartilhar link
DEVELOPER
21/11/24 18:40
Published date
21/11/24 18:40
Published Date
21/11/24 18:40
SUPPORTED OFFERINGS
Liferay PaaS
Supported Versions
7.4
Resource Requirements
Edition
Community
PRICE
Free
help & support
SHARE LINK
Um inesperado erro ocorreu.