Using DR 4.2.1 on DNN 6.1.5 - Any page containing the DR module will break the modals that popup for basic functionality.
Say you want to login. The modal pops up and once you enter your credentials the modal (which should disappear) flashes to contain a mirror of the current page. The user then has to manually close the window down.
Using Tabs and Panes: As soon as a field with validation is modified the panes and tabs breaks and disappear leaving some but not all fields on the page.
I have had a mass of complaints from our clients. As this is a registration module, it is fair to say that people will be logging in, using modals and want to use the tab/panel and validation functionality.
Default DarkKnight skin: admin control panel is broken when using the "standard" group of skins. The "mega menu" group seems to work.
I should note that this is tested on a CLEAN install off DNN 6.1.3 and 6.1.5 with the default skin and no other module on the page.
This happens with all modals on all browsers. This version was released without proper testing, we have upgraded all our sites and cant just revert now. We are having to hack patch our sites just to get them to work. Turning off most of the functionality.
There is obviously many issues with jQuery and JavaScript clashes with the standard DNN instance and default skin. We were promised a patch a week ago and are yet to hear anything about it.
We operate income generating sites for clients. We cannot have a vendor release products, untested, that can potentially jeopardize our business.
|
Data | Hi Marc - thanks for your comments. These have already been logged within our Zendesk and Jira systems and we are working towards a resolution. Right now we plan to have the JavaScript and Password validation issues fixed by EOD tomorrow with a patch. These issues came about because of new enhancements within the latest version related to how Panels/Tabs/Groups of questions work and also some enhancements within the ASP.NET validation controls which are conflicting with DotNetNuke framework.
So.. These are high on our list to fix and then we can review any other major issues.
I will follow up tomorrow with a patch.
Thanks,
Chad |
|
|
Data | Hi Marc - I apologize for the delay, this is something I am still working on and I am hoping to have the patch ready by this evening. We have two other related cases but those updates are through the http://support.datasprings.com and unfortunately can't transfer all of your case details there.
The only specific issues we have logged and duplicated though are specifically related to some JavaScript problems with some updated ASP.NET validation routines. So any of these other issues are separate from the patch that is coming out. |
|