By Altitudes on Friday, 13 March 2015
Posted in Technical Issues
Likes 0
Views 409
Votes 0
Hello,

When a user registers with a Profile Type, he doesn't get the Privacy as defined in the Profile Type. This is for profile field only, for other privacy settings (such as "Who can view my stories" etc.), it seems to be working fine.

Thanks
Hi,

Sorry for late reply to this,

It seems like I can't reproduce this issues in your dev site, check my screenshot -> http://screen.stackideas.com/2015-03-19_1422.png

When I tried to using JFBConnect register in your site, my user account custom field is followed what you configured in this profile type "Adhérent". Am i missing something here? Please advise.
·
Thursday, 19 March 2015 14:25
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Altitudes,

Sorry for late reply to this,

We are still investigate on this and get back to you as soon as possible.
·
Friday, 13 March 2015 17:40
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Altitudes,

Thanks for reporting, that was a bug actually, but we will fix this in next release version.

You really need this temporary fix, you can go to your backend > Easysocial > privacy > select the custom field > set the privacy value.
·
Friday, 13 March 2015 20:26
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello,

From ES 1.3.21 Release Notes this has been fixed ("Fixed new user the custom field's privacy not respecting the value from profile type the u ...").

And indeed it seems to be working when you create an account in the "normal" way.

But when you create the account using JFBConnect, then it does not work (fields privacy is set to "Everyone", regardless of what is defined in the Profile Type).
Can you please investigate? I you want to reproduce the issue on my site, use the Profile Type Adhérent at registration...

Thanks
·
Wednesday, 18 March 2015 19:37
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello

Well, so strange... I tried again and it was OK. I can't figure out what I did before that may have made it not work.

Thank you anyway
·
Thursday, 19 March 2015 17:07
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi,

Thanks for getting back to us this issues resolved.
·
Thursday, 19 March 2015 17:22
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post