Enabling Device-Emulator | Community
Skip to main content
H
herbertkb
Level 2
July 30, 2018
Solved

Enabling Device-Emulator

  • July 30, 2018
  • 8 replies
  • 4890 views

Hi, we have a requirement to disable multiple features in AEM for certain Usergroups, but in the process, we also disabled the Device-Emulator in the Editor.

Which permissions does a Group/User need to view the emulated device?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by herbertkb

Hi Arun,

I've done that right now and it seems a usergroup also needs readpermissions on "/etc/mobile" to see the Emulator-Button

Regards,

Herbert

8 replies

V
Adobe Employee
vish.dhaliwalAdobe Employee
Adobe Employee
July 30, 2018

Hello,

Try giving read permission on path "/libs/wcm/mobile/components/emulators/"

Regards,

Vishu

H
herbertkbAuthor
Level 2
July 30, 2018

Hi Vishu,

thanks for the fast reply, problem is the read permissions are set, but the button

is still not visible in the editor

Regards,

Herbert

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
July 30, 2018

Hi,

Emulator is displayed based on com.day.cq.wcm.mobile.core.impl.MobileEmulatorProvider factory config,

Arun Patidar
arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
July 30, 2018

If you want to show/hide this button based on user group or privilages use renderconditions.

1. overlay /apps/wcm/core/content/editor/jcr:content/content/items/content/header/items/headerbar/items/emulator in app

2. create granite:rendercondition child node to emulator node (Render Condition — Granite UI 1.0 documentation )

+ granite:rendercondition

   - sling:resourceType = "granite/ui/components/coral/foundation/renderconditions/privilege"

   - path = "/my/path"

   - privileges = "jcr:addChildNodes"

You can either use privilege or feature, If you need to enabled this based on aem groups rather then jcr privileges use sling feature flag.

Sling Feature Flag in AEM

Thanks

Arun

Arun Patidar
smacdonald2008
smacdonald2008
Level 10
July 30, 2018

Excellent response!

H
herbertkbAuthor
Level 2
July 31, 2018

Hi Arun,

thanks for the response, but it seems it's not working with renderconditions since there seems to be an additional check for the emulator button to be displayed. I've looked into the MobileEmulatorProvider config and our resourcetypes are registered.

With the admin user and "content-authors"-Usergroup the Emulator-Button is visible, but with our custom "author" group it's not.

Thanks in advance,

Herbert

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
July 31, 2018

Hi,

Could you please compare read permission of your custom "group" and "content-authors" ?

Thanks

Arun

Arun Patidar
H
herbertkbAuthorAccepted solution
Level 2
July 31, 2018

Hi Arun,

I've done that right now and it seems a usergroup also needs readpermissions on "/etc/mobile" to see the Emulator-Button

Regards,

Herbert

Terms & ConditionsAccessibility statement

Loading footer...