I've deployed a fresh install of DNN7. Everything looks good while using default config generated automatically by installation regarding view permission for Activity, Profile, Messages and Friends pages pointed by Console Module, but if I try to change view permission for any page it doesn't work.

It also happens if I create new pages under Activity Page (videos and photos for instance). It doesn't matter if I add new Console Module or if I copy it from Activity Page, so I'm unable to control profile pages visibility (using Module's Profile Mode).

I would like to get this view config:

Activity - Profile - Friends - Videos and Photos >> Friends

Messages >> User

I also wonder how the user himself can change this default config, so he can control his profile visivility (similar to how it was done in Active Social).

I've read a lot of docs and forums but obviously I'm misunderstanding something or doing something wrong. Some help will be really appreciated.

---

JR MundoMayor

Hi Erik,

this is my experience:

- When I open module settings I go to the especific module settings tab, then I can see module set on "Profile" mode and under that I see the list of all child pages (under Activity Page) whith a list of options to choose (Public - Friends - User).

What I expect is: if I change for instance "Profile" page setting on the list from 'Public' to 'Friends' I hope that setting changes and so that particular page is not shown to any user except to my friends.
What happens is: setting change is not saved. After saving settings I open module settings again and the old value ('Public' in our example) still remains the same.

- After that happened, I made some tests:

1.- Create a new instance of console module in a different page >> the issue is the same but in this case all settings are set by default to "Public" and any change is not saved either.

2.- Delete console module default instance on "Activity Page" and create a new instance in this same page >> same as prior described.

So it seems only automated default deployment is able to set view permissions for child pages different than "Public" and any later change attempt is not saved into the database.

I hope this helps.
JR.

---

JR MundoMayor

Thanks Rodrigo!

Your solution solved our problem :-)

Chris

---

Chris Wylie
Chief Executive Officer

1775 W. State Street Suite 371, Boise ID 83702 USA