Hello Alexandre,

The toolbar module is actually riding on the same codes as the toolbar within the template. You probably had those options disabled and it can be re-enabled when you access the Themes area at the back end of EasySocial.

In the backend-theme-wireframe-toolbar

There shall be an option with: Show friend
Which doesn't exist.
However, it does it the module version however. I would like the same feature for the missing options that aren't present in both.
I don't want them to have access to it. Therefore, no need to see it.

Ah okay got it. Will see if we can add this in the next version but temporarily you can remove it by editing the theme file /components/com_easysocial/themes/wireframe/toolbar/default.php and at line 34 remove the codes below,

				<?php if( $friends ){ ?>

					<?php echo $this->loadTemplate( 'site/toolbar/default.friends' , array( 'requests' => $newRequests ) ); ?>

				<?php } ?>

Thanks, works like a charm.
Which file I need to check to do the same for the dropdown login (right of the toolbar) with the account, preference, logout section ? I don't want them to have to privacy and notification setting, as an example.
Removing the option is providing a good start while waiting for a proper ACL...

Hello Alexandre,

Take a look at the file /components/com_easysocial/themes/toolbar/default.profile.php

Honestly, one of the best support ever seen !
You should add to 1.3 template option for all of the icons, this is not a long implementation and my code hack won't be needed in next version hehehe.

Now that I have taken up the Friends option from the toolbar, how could I really forbid one to go there, manually or by a menu from another page or option (same for other option).

I don't want the user to change it's privacy settings or notification setting... removing the menu is step one but i don't want to leave any door open

Thanks again for great support

Hello Alexandre,

Hm, that would be a little tricky because you need to modify the view files and when you upgrade in the future, it would get overwritten What you could do is to add some hacks in your system plugins to detect if the user manually type the url to access these pages and redirect them accordingly.

Hey Mark,
Didn't even know it was possible to do that actually. Is there a general extension that can forbid that all the way... cause in the end, except for debugging, manual url shall not be possible.

Otherwise, a Front-end ACL is definetly needed if no toggle On/Off variable can be set in the administrator so I can restrict some of these to manager/admin. I would be willing to throw some penny into this to step up the process. I know, from the Voice section, that I am not alone ! and thanks btw to correct the voice section!

Let me know,

Alex

Hello Alexandre,

Yeah, unfortunately right now this is not possible as we don't actually have the ability to turn on / off for some of these features

Mark,

Any roadmap and timeline for either
a) a Front-End ACl
b) On/Off Back-end option to view each element

Since some information of my clients would be very sensitive, this would end up very important...

Thanks

Alex

Hello Alexandre,

Hm, sorry but what's a "front end ACI" ? But the on/ off options for views, I am not really sure if this is advisable because it's like placing a suicidal button for site owner There are times where having too many settings would lead to more confusions

Hey Mark,

Any kind of Access control publication. How can I setup that any register user (standard profile) can't access certain menu option.
I have to restrict certain page, menu, application etc for my default user.
Any suggestion to that ?

Alex

Btw Mark,

Check the Post i'm having with Mohd with deviate to the same subject:
Front-end permission

Which relate to the voice submission: http://stackideas.com/voices/easysocial/item/28