Hi Aikaterini,

Thanks for reporting. I have tested this locally and am able to replicate this issue.

This is indeed a bug where the access setting for core apps are not being respected. I will log this in our internal tracker so the devs can address it.

Thank you for logging this in your internal tracker!

On our case... what do we have to do now? Is there a fix for this issue? This one is a must have for our application!

Thank you

Hey Aikaterini,

Actually the devs are still working on this so there's no proper fix yet. Furthermore, there are quite a few files involved so there is no simple fix.

But if you urgently need a temporary fix to hide restricted apps from the profile header dropdown(http://take.ms/oCLwP), you can try using the temporary fix that I have attached below.

You would have to upgrade EasySocial to the latest version and backup the original file first before applying the fix below.

JoomlaFolder/administrator/components/com_easysocial/includes/template/helpers/cover.php

Thank you for the reply. Will i have a notification when the proper fix is created, or i have to ask again sometime later?

Hey Aikaterini,

The fix would be added into 2.1.11 when it is ready as we have just pushed out 2.1.10 last week. We'll post them on the blog when there are new updates

Hi Aikaterini,

I am really sorry for the confusion.

If you are attempt to control whether a user can access a page within EasySocial by using the app's access control? I am sorry but this is not possible at the moment.

The app's access control only restricted content generated by the app itself. E.g. stream items, app's widget or app view. From your original request, you are trying to restrict the access to followers page by using follower app's access. This is actually not supported in EasySocial.

Hope the above clarifies the usage of the app's access control.
Let me know if you still having doubts regarding the app's access control.

Have a nice day