Hi everyone!

We have had several clients integrating the latest DropDown Login module with the Dynamic Login module integration and I wanted to follow up with some of these posts and feedback we received from some clients.

First... These two issues are only problems when integrating DropDown Login w/ Dynamic Login. So you are implementing just Dynamic Login or just DropDown login then this post does not apply to you.

Issue #1:
There appears to be a problem with localization resource files not displaying the labels correctly in Dynamic Login. We have checked and not really sure why this is happening because we tried adding the localization to both the DropDown login skin object and also the Dynamic Login module directory but the problem still exists.

So you can either:
1: Don't use the built in [labels] but just use Text/HTML for the label text within the Dynamic Login template
or
2:  Follow the instructions listed in this thread to add the resource items to the shared/global resource files in DNN.
http://www.datasprings.com/products/product-forums/aft/23375


Issue #2:
Several customers have started complaining that the module doesn't function properly when its on a page that also has Dynamic Login on it. At first we thought that this would be something we could fix but its a little more complicated then that. The module already checks to see its own ModuleID throughout areas such as the stylesheet, checking username/password, etc... BUT the problem I believe happens when you  are using the exact same moduleID as the module instance on the page. In theory its really loading the exact module twice with the same ID and I think that is causing a problem .

So option #1:
1. Try creating another module instance/module ID that is 'specific' to what you are wanting to use DropDown login for and keep this module instance separate from your main portal login.  I have not tested this yet but after reviewing the code it should work.
OR
2. Modify your skin to use DropDown login for most pages but not specifically for the main login page. This way if the user is on the main login page they won't see DropDown login.

As far as some other items...
There is also an issue we are researching where the [RegisterURL] isn't functioning right with Dynamic Login 3.5 and the latest versions of DNN 5.6. This is something that is on our fix list and we are researching for the next release. For now you can just hard code an image or URL to the register page and you really don't need to really use that token since you have full HTML access to the template.

The Dynamic Login 4.0 release is right around the corner! I think everyone will be very excited to see the latest enhancements including Facebook Connect. You can test it out now by clicking 'Login' on our site and clicking on the Facebook connect button.


Thanks,

Chad