Thread

I have what I think is a bug with my EE 1.6.7 installation.  I hope I can elaborate clearly on what I think the bug is so that it makes sense.  If more clarification is required, just say so.

Ok, so we have member groups that we create for each new customer.  Within each member group, a new user is added.  From there, we create a new template and set the access to that template, such that the newly created member group can access the template.  We also enable password protection on the template.

So here’s where I think the bug comes into play:  Every time a new member group is created and a single user account is assigned to that group, access to previously created templates is granted to the newly created user group.  After all is said and done, I have to go back to each previously created template and update the access to exclude the newly created member group.  Is this a bug or is this the way the creation of new member groups is designed to work?

If there’s a fix to this, I would really like to know about it as it is becoming more difficult to manage as new member groups are added fairly frequently.

Thanks in advance!!!!

SCS,

That would be the way it is designed to work.

Can I ask why you need to create a new template and member group each time?

You could have one template and one member group with multiple members and just set the permissions inside the template with conditionals

{if member_id == "2" || member_id =="3"}

Show content

{/if}

Or in fact just by the group to save you having to add a member id each time to the template

{if group_id == "2"}

Show content

{/if}

The reason is that the content is proprietary on a per member group basis.  I do realize that conditionals could be used, but it’s an entire body of content, where multiple users within one company will login and view content and perform actions.

It’s just not very efficient that every time I create a new member group, that I have to go update the access in all the existing member groups to omit the newly created group.

No worries though.  I’ll just keep doing what I do now as there isn’t a clear and better solution.

Thanks for the insight!

In that case, closing the thread. Feel free to start a new thread if you have any more questions.