Jay P
going with the flow
Posts:38
 |
| 01-29-2008 09:14 PM |
|
How does this module take into account the user profile visibility that the user might have changed on his Manage Profile page.
Let's say the user has set his Country field to Admin only Visibility - the field value for Country should be hidden on the Directory user list and on the Detail page when a regular member is looking at this user's information?
Right? |
|
|
|
|
Miguel Clara
going with the flow
Posts:56
|
| 05-26-2010 09:30 AM |
|
I am amased this question was never replied I actually have the same question.. but not only for DNN core profile, what about DR?
In my case all properties are linked to the core profile, but I think DR should also take this in account, but anyway, back to the issue, how do I work this out?
|
|
|
|
|
Candace
river guide
Posts:2431
|
| 05-26-2010 11:27 AM |
|
Hi Miguel,
Changes made to a user's profile (whether in DR or in the standard DNN profile page) will reflect on your Dynamic User Directory as long as the fields are mapped correctly to the core properties.
However, Dynamic User Directory comes with a 60-minute delay in order to improve performance. This means that if user chnges his profile, the change will not show up in DUD until after 1 hour. The 60-min delay can be reduced if you prefer.
Hope that helps!
Candace |
|
|
|
|
Miguel Clara
going with the flow
Posts:56
|
| 05-26-2010 11:39 AM |
|
I know that lol
I don't think I got to the real point!
We are talking about privacy here.... i mean you choose what you want other people to see on facebook right?
DNN also has this is the core, you can choose what other users can see by setting visibility to "public" or "admin only" or "registered users" but DR does not have such thing so DUD will always show everything! |
|
|
|
|
Candace
river guide
Posts:2431
|
| 05-26-2010 01:00 PM |
|
Ooohhh, I see what you're saying now. No, at this time, we don't have a way to let the user select what properties will be displayed. However, I'll refer this to Chad as an enhancement request. Thanks!
|
|
|
|
|
David To
river guide
Posts:2719
|
| 05-27-2010 03:42 PM |
|
HI, how about having multiple modules/instances of DUD and set that module to be visible for certain roles. Then you can customize each of these DUD instances to have different templates showing different fields so t hat depending on the role that the user belongs to, they can see only certain fields because they can view that particular DUD instance. -- David |
|
|
|
|
Miguel Clara
going with the flow
Posts:56
|
| 05-28-2010 08:28 AM |
|
that would work great if it was me or the admin to select what to be visible, but this must be done by the user... it would be very random!
Anyway I think this would be a great feature to implement in a future release and if possible integrate it with DNN Core, since the core Users Module already has this option!
|
|
|
|
|
Ryan Bakerink
river guide
Posts:1900
|
| 06-01-2010 02:51 PM |
|
Thank you for your input, I will report this to our development team, to take into consideration for the next release of this module.
-Ryan Bakerink |
|
|
|
|
Chad Nash
Posts:5260
|
| 06-03-2010 01:05 PM |
|
Hi guys...
Although we don't have a way (built in) for Dynamic Registration for the user to set their visibility of a profile field I think that this can be added into Dynamic User Directory very easily.... We can post a solution here and then also research either adding this as an option in the module, or forcing it based common visibility flags.
The query and stored procedure used - DataSprings_RetrieveDNNUserProfileData3 is the stored procedure that is used to generate the PIVOT table.
This stored procedure has this in the query:
select U.userid,U.username,U.firstname,U.lastname,U.email,U.Displayname, UP.propertyvalue,P.propertyname, P.PortalID from dbo.[Users] U inner join dbo.[userprofile] UP on U.userid = UP.userid
inner join dbo.[profilepropertydefinition] P on UP.propertydefinitionid = P.propertydefinitionid
All you need to do is as a case statement on that data... In the example below it would be if the visibility was set to 0. You could easily change this to be set to 1, 2 etc...
select U.userid,U.username,U.firstname,U.lastname,U.email,U.Displayname,case UP.Visibility when 0 then UP.propertyvalue ELSE '' END AS PropertyValue,P.propertyname, P.PortalID from dbo.[Users] U inner join dbo.[userprofile] UP on U.userid = UP.userid
inner join dbo.[profilepropertydefinition] P on UP.propertydefinitionid = P.propertydefinitionid
This would fix you up, if you want me to post the full stored procedure/alter statement to handle this let me know and I can do that as well. You could also change the empty data of ' ' to represent something else such as 'Not Visible' depending on how you wanted it to appear in directory.
Does this work for you?
Thanks,
Chad
|
|
|
|
|
Chad Nash
Posts:5260
|
| 06-03-2010 01:07 PM |
|
Also - I should note that it already does look at the Profile Visibility flag and only uses profile fields set to 1. This is a global setting for the profile fields though and not the user profile setting which is separate.
-Chad
|
|
|
|
|
Miguel Clara
going with the flow
Posts:56
|
| 07-01-2010 12:54 PM |
|
Sorry I must have unchecked the mail notification on this one, I only see that you reply now...
But I'm not sure If I get this... this solution would work for the profile it self... not every property one by one ... Am I correct?I got a bit confused by the last post!
Sorry for the inconvenience!
|
|
|
|
|
Chad Nash
Posts:5260
|
| 07-02-2010 12:47 PM |
|
Hi Miguel,
Actually I believe this solution is still user specific. If you look at the table its joining to its the user profile table and not just the property table. The query is executed within the stored procedure to create the pivot table for each and every profile field.
If you look above this is the query that is used to 'generate' the PIVOT table that is then referenced... So I believe the query is executed for each and every profile field for the user. I could be wrong but after reviewing this is what I think is the situation.
-Chad
|
|
|
|
|
Patrick Byrnes
Posts:17
|
| 07-22-2010 01:07 PM |
|
I have installed DL DR, DUD and imported approximately 1000 users who have a role of member. I am even more confused then he is. I am not a programmer, and implementation of a store procedure without explicit guidance is not quite within my grasp.Indications are there is a linking between DR and DUD.
So I went into the DR and put in several checkbox fields to indicate to our members which personal information they would authorize to put into our Member directory.) Then went into DUD to see what DR interactivity is available. Or more specifically how to filter privacy column to not show for the registrants that opted out, by column.
This is mandatory requirement to us, or face procecution by our members. They have the right(just like optin email) to limit the personal information we publish. I thought I could put in all the information and have the columns filter all members by a true/untrue by column from a question event in a DR field indicating this column is authorized or not by the registrant.
Now I already have a directory that can be viewed by role for those authorized to view or access this data. But a member directory to be viewed by other members by the role members right now will allow all users of the role members the right to view whatever columns of data that the module is set to show. What I believe he indicated was a right in the profile of a member to chose to show the private information on a selective basis, if not a total basis not to be included in the directory. I would like to see a way for me to allow the registrants the ability to chose to show selectively which data to allow other members to see, all the information, none, or selectively chose which information can be disclosed publicly or even within the member role. Would be nice if DUD could check a field to ensure the user has authorized the release of this information to a pecticular role.
|
|
|
|
|
David To
river guide
Posts:2719
|
| 07-24-2010 06:27 PM |
|
HI, DUD code (stored procedures) are looking strictly at the DNN user profile. There is no correlation between a DNN user profile and a user's ability to individually pick and choose which profile field they choose to display or hide.
A way to to accomplish what you want would be to use a combination of Dynamic Registration (for creating DNN core profile fields along with a checkbox correlation next to each of this DNN core profile field for the user to choose to display or not). Then saving all the results to a separate SQL table. Then use Dynamic Views (using SQL statement) to generate the results for display instead of using DUD. Or use Open Web Studio. But the simple fact is that you will need to store fields to a separate SQL table and query that SQL table.
I hope this points you in the right direction. -- David |
|
|
|
|