Hi,

I have a number of users in the portal that have not been authorised but they still are being displayed even though I have set the "Authorized Users Only" setting to true.

Is there something else I must do to stop these users from displaying?

Regards,
Mark.

Hi Mark,

Can you please check in Host, Module Definitions and tell me the exact module version you have?  Also, what DNN version are you running.  Thanks!

Candace

 Hi Candace,

DNN Version: 05.04.02
Dynamic User Directory Version: 3.0.30

Regards,

Mark.

Hi Mark,

Thanks for the info.  I'm not able to duplicate this on my DUD but then, I have an older DNN version.  Let me ask you a few questions: 

1.  Did this work properly before?  Did it stop working when you got DNN 5.4.02?

2.  Does this occur on initial display or when you're searching?

3.  If you uncheck the setting for Authorized Users only, then go back and check it again, does it behave differently?

Thanks!

Candace

Candace,

To answer your questions.

1.  I only used the module after upgrading to 5.4.2 (so I could not tell you if it was working before)

2.  This is occuring on initial display (I have disabled searching)

3.  Unchecking (and saving) then rechecking (and saving) has no effect.

Regards,

Mark.

Thanks for the details, Mark.  We've received some issues reported on DUD with DNN 5.4.  As a first step, can you please run this in Host / SQL and see if it makes a difference for you:

execute AddSchedule 'DataSprings.DNN.Modules.DynamicUserDirectory.DUDSchedulerClient, DataSprings.DNN.Modules.DynamicUserDirectory',60,'m',30,'m',25,'',1,1,'', NULL,0, 'Dynamic User Directory'

It should, at the very least, eliminate any issues that may be related to the scheduler.  Please let me know what happens after this.  Thanks!

Candace

Candace,

I remember running this script after installing DUD.  I executed the script again, it added another scheduled job so I removed the old one.  After running the new scheduled item, the issue still exists, unauthorised users are still being displayed.

Regards,
Mark.

Thanks for trying it.  We may have to look under the hood for you to see what's going on.  Please use the Contact Us Support form and provide us with  1) a host login  2) the URL to your DUD page  3) your invoice ID and 4) the URL to this thread for reference.   Please include the module version and DNN version, again, too.

Thanks!

Candace

Hello Mark,

Ok. I have this fixed up for you… Basically earlier versions of DNN would look at the authorization flag under aspnet_membership table, but in the latest release DNN doesn’t unauthorized them there, it unauthorizes them at the ‘UserPortals’ table. This is so a user can be locked out of one portal but kept in another portal.

I updated the query to check for the authorization in both places and have also made note of this for the upcoming 3.1 release (will include some fun features such as a users online/offline image and integration with DNN User Profile Image tokens along with some more SEO tools as well.

Please see the SQL that was prepared for you: