Hey James,

I am not really sure if I understand you here. If the user does not have "Community access", then you don't really need to set any ACL. As long as they don't have community access, they will not be able to access any other sections on the site.

Thanks for the reply Mark.

Regarding the ACL, I want the user to still be able to access the content they have add but not add any additional content. We are using EasySocial inline with JPayPlans to assign memberships based on time. So once the users membership expires they are moved to usergroup "No Membership" which should still allow community access but disables them the ability to create anything new.

The problem with the ACL Rules currently is that if you set them to Limited and = 0 it defaults back to Unlimited as mentioned above.

The other problem with using the No Community Access setting is that you have no defined URL Re-direct for us to use so if the user in fact has No Community Access it auto-redirects to the Profile Settings page.

What are your thoughts for addressing these problems?

Thanks,
James

Hi James,

The problem with the ACL Rules currently is that if you set them to Limited and = 0 it defaults back to Unlimited as mentioned above.

Hm, I just tried to replicate this in my local instance but it seems like the ACL settings did get save correctly when I set all of the rules to limited. May I know is there specific steps that I need to follow in order to replicate this? Can you provide us with your Joomla backend and FTP access as well?

Exrul, I update my original post with my site details.

Thanks,
James

Hi James,

I am sorry but please assign your domain to your EasySocial license to obtain for support. You can do so by accessing your license area at http://stackideas.com/dashboard

Once you are done, update us here and we'll continue checking your issue.

Ok, its updated but the site is in development at this time.

Thanks,
James

Hey James,

Ah okay I get what you mean now. When you set the value as "0", it basically means unlimited. However, this is actually the default behavior of the ACL because assuming that you want to "limit" a specific rule, it would expect you to define a specific value.

If you do not want to allow users to send message for instance, you just turn off the ability to "Start new conversations". This way, regardless of their daily sending limit, they won't be able to start a new message.

But what do you do in the case of things like Events where you only have an option to disallow creation but to disallow the attending it is based on a number limit. This is the same for other areas of the ACL as well.

James

I think rather than specifying the "limit" to 0, there should be an acl that says if the user is allowed to rsvp because it really doesn't make sense to have a limit of 0.

I agree.

Keep in mind this should be applied to all areas of the Users ACL where a limit is currently restricting some access.

- Conversations
- does the start new conversation block ALL conversations even if the user is already conversing through a pre-existing conversation?

- Events
- this should apply to "total events allowed to attend"

- Groups
- this should apply to "total groups allowed to join"

- Photos
- there should be an option to disable photo uploads

I believe that would cover the existing areas where ACL is concerned.

James

Hi James,

does the start new conversation block ALL conversations even if the user is already conversing through a pre-existing conversation?

The rules will only block the user from creating a new conversation with other user. They can still continue any pre-existing conversation before the restriction take place.

- Events
- this should apply to "total events allowed to attend"

- Groups
- this should apply to "total groups allowed to join"

- Photos
- there should be an option to disable photo uploads

Thanks for the input on this. I have already log this into our codebase and hopefully we will able to implement this in the next release of easysocial.