Jon DiPietro
going with the flow Posts:35
|
03-13-2011 02:33 AM |
|
I'm using Dynamic Registration v4.0.60 and Dynamic User Directory 3.0.0.
I created a bunch of custom registration fields using DR and clicked the "Quick Create Property" link. I verified that they were created in the Manage Profile Properties page.
However, when I added the Dynamic User Directory module to a page, only the base, required fields are available to choose from. |
|
|
|
|
Ryan Bakerink
river guide Posts:1900
|
03-14-2011 09:53 AM |
|
Hello Jon,
Please go back to the Manage Profile Properties page and verify that your newly created profile properties visibility checkbox is checked. Otherwise they won't be included in the creation of tempDUDPivot table. So if you end up having to update the visibility for some profile properties be sure to go to Host -> Schedule and restart the DUDSchedulerClient scheduler. Then all changes should be reflected. If this still doesn't work. Can you please go to Host -> SQL and see if this query brings in your new profile preoperties:
select * from tempdudpivot
Please let me know
Thanks,
Ryan
|
|
|
|
|
Jon DiPietro
going with the flow Posts:35
|
03-14-2011 12:27 PM |
|
Hi Ryan, Thanks for the response. All of the properties were set to visible, but when I looked at the schedule and DUDSchedulerClient doesn't exist. When I tried to upgrade to Dynamic Registration 4.0.6 (from version 3.0) it displayed a SQL error message when it tried to create this schedule. However, I removed the module, deleted the files, and then reinstalled and didn't see an error message. |
|
|
|
|
Ryan Bakerink
river guide Posts:1900
|
03-14-2011 01:54 PM |
|
So do you have the DUDSchedulerClient schedule?? If not I would recommend reading this blog post to help you set it up: http://www.datasprings.com/news/blog/postid/12You will need this in order for Dynamic User Directory to work. Let me know if you can get it configured correctly. Also perform a Host -> Restart Application after creating this scheduler. Thanks, Ryan |
|
|
|
|
Jon DiPietro
going with the flow Posts:35
|
03-14-2011 02:13 PM |
|
I did not have the DUDSchedulerClient set up. I followed the directions from the other post and everything is working now. Thanks for your help! |
|
|
|
|
Ryan Bakerink
river guide Posts:1900
|
03-15-2011 07:36 AM |
|
Hello Jon,
No problem, if you ever have any questions please let me know.
Thanks,
Ryan
|
|
|
|
|
Antony (WEBPC)
river guide Posts:158
|
03-31-2011 06:31 AM |
|
IMO it would be a nice feature to either include all profile field properties by default or have an option to switch between the ones that are marked visible or ignore the visible setting. When using DR its my experience that you add fields that you don't want visible but would want to use them in the Directory module. Antony |
|
|
|
|
Ryan Bakerink
river guide Posts:1900
|
03-31-2011 12:55 PM |
|
Hello Antony,
Thank you for your input. We will make note of this. But you can create a SQL completion event to do this for you, if that would be more convenient for you then the current DNN settings of profile properties.
If you have any questions please let me know.
Thanks,
Ryan
|
|
|
|
|
Antony (WEBPC)
river guide Posts:158
|
03-31-2011 01:02 PM |
|
Hello Ryan Sorry I have missed something how can you use SQL completion events in the User Directory Module? Antony |
|
|
|
|
Ryan Bakerink
river guide Posts:1900
|
04-04-2011 08:51 AM |
|
Hello Antony,
My previous response was relevant to Dynamic Registration completion events. Basically upon submission you can change the visibility of profile fields.
I must have misinterpreted your question.
In DUD this isn't a feature where you can run SQL to alter visibility settings.
-Ryan
|
|
|
|
|
Aaron Shapiro
new to the springs Posts:1
|
03-21-2012 06:47 AM |
|
I am having similar issues here and I have restarted DUD and it fixed some of my issues but not all of them. I am still missing some properties in the template configuration screen, on the left side where it lists the tokens. I have the same issue with these fields not showing up in the sort / filtering area when configuring the list and what to pull and not to pull. They are properties that are visible and all users can see. I am using 4.0.10
|
|
|
|
|
Chad Nash Posts:5260
|
03-21-2012 09:26 AM |
|
Hi Aaron - Can you let me know some of the names of the fields that are missing? There are a few profile fields (by name) that could cause conflicts... that is one possibility, otherwise it is generally: 1. At least one user needs to have data stored for that property 2. The property must be set as visible. Thanks, Chad
|
|
|
|
|