Hi Girolamo Toscano,

I am really sorry for the delay of this reply as it is a weekend for us here.
I have tried to access in your Joomla backend, but i hitting this :

Warning

Username and password do not match or you do not have an account yet.

By the way, if you would like to changed all the user privacy to `Who can view my stories = My friends`, you have to tick this option, check my screenshot below. After that click save it, so that it will applied to all of your current user this privacy. Hope this help.

Hi Arlex,

Thanks for the reply. Unfortunately it still doesn't work.
Normally you could access to to backend with the admin account, I checked the password and it is correct ?

Hello Girolamo,

I am sorry for the delay of this reply.

To change the default story privacy, you can go to your backend > easysocial > privacy > who can view my story. Refer my screenshot here, http://screen.stackideas.com/2015-06-01_1031.png . I've change the setting for you and it should be working fine now. Please have a look.

Sorry I insist on this issue because your solution modify the privacy of all users of the website and I thought it was possible to change the privacy of each profile type...
Because in fact I have 3 profiles types : 2 of them (Talents and talents pro) are allowed to post their stories in order that all users can see them; and one profile type ("others") is allowed to post stories viewed only by his friends.

When I modify the parameter on a single profile type (profile type "others"), nothing change. The users of this profile type have always the same parameters than others users... So changing the parameter "who can view my stories" seems not working in this profile type?

Hello Girolamo,

I am sorry for the delay of this reply.

I am sorry for the confusion here. By right the privacy parameter in the profile types should be working fine when you follow the steps that my colleague mentioned in his first reply. I've tested in your site by going changing the parameter "who can view my stories" in "others" profile types and its working fine on your site. Can you verify it for me as well?

By the way I've reverted back the change that I made under the global privacy settings.

Hello Ezrul,

Thanks for your help. Unfortunately the problem is still there, it's weird

So with the super users account it works well but with all others account no. See on the attached images.
Which account did you use to verify that it works ? Try with Carolina account please (on frontend) (you can find the email and password in "optional informations" from the first post here).

Hi Girolamo Toscano,

Sorry for late reply to this,

I still can't access in your Joomla backend, can you help us double check with you provided that login credential is it correct?
please advise.

Hello Arlex,

Can you try now please ? ("admin" account for backend and "carolina" account for frontend)

Hi Girolamo Toscano,

I'm really sorry that missed up this post thread, can you test again it should work fine now.

Hello,

I really regret to say that the problem is always here...

I will explain well what I noticed :

1) The user register on the website. He choses one of the three profile type.

2) As soon as the user is registered, the privacy parameters applied are wrong, they don't math with the privacy parameters of the profile type he has chosen.
(see picture 1)

3) If the administrator go in the backend, in the user profile and (WITHOUT any modification of the profile privacy of the user) click on save, then the profile privacy of the user is OK.
(see pictures 2, 3, 4).

I really think there is a bug here, because I noticed the same thing in my test site...

Hope this issue could be resolved.
Good luck guys

Hello Girolamo,

I am sorry for the delay of this reply.

I am able to replicate the issue in my local instance. We are still investigating on the issue and will get back to you as soon as possible once the fix is available. Thank you for your kind understanding.

Hello Ezrul,

Do you have some news about this issue?
Thanks

Hello Girolamo,

I am sorry for the delay of this reply.

It took us quite some time to resolve it but we manage to found the solution for this. Kindly download the attachment below and place it inside your /administrator/components/com_easysocial/models/ folder and see how it goes.

Wonderful

It works as it as to. Thank you !!

Hello Girolamo,

You are most welcome. The fix will be included in the next release of easysocial. Glad that your issue has been resolved now.