Josh Slaughter
going with the flow
Posts:55
 |
| 09-05-2012 06:04 AM |
|
I'm running DNN 6.2.2 Professional and DF 4.10.4. If I add an instance of the module to a page, some of the module menu links don't work anymore. I'm having issues with the HTML module menu links. The Publish link, and all the links that allow me to move the module are no longer working. The error I'm getting is "
Uncaught ReferenceError: dnn is not defined" I'm confident that the skin is not the problem, because even with the default Dark Knight skin, I still have the same issue. I've already disabled jQuery in the DF module, but that doesn't seem to help either. It seems that some of the ajax postbacks on the page aren't firing. For example, when logged in as a Super User, when I change the view from Edit to Layout, nothing happens, I just get the same error as mentioned above. Something in the DF is causing the DNN scripts to break, but I don't know what it is or how to track it down. Any help would be greatly appreciated. |
|
|
|
|
Candace
river guide
Posts:2431
|
| 09-06-2012 06:48 AM |
|
Hi Josh,
Can you please check in Admin, Event Viewer and see if there are related errors logged there? Do you see anything related to "links?"
Thanks!
Candace
|
|
|
|
|
Candace
river guide
Posts:2431
|
| 09-06-2012 06:48 AM |
|
Hi Josh,
Can you please check in Admin, Event Viewer and see if there are related errors logged there? Do you see anything related to "links?"
Thanks!
Candace
|
|
|
|
|
Josh Slaughter
going with the flow
Posts:55
|
| 09-06-2012 07:14 AM |
|
Hi Candace, There are no errors posted in the event log. No module exceptions or anything related to "links". It seems that whatever is happening is on the client side conflict with the module and DNN. -Josh |
|
|
|
|
Candace
river guide
Posts:2431
|
| 09-06-2012 07:31 AM |
|
Thanks, Josh. Looking through other similar reports, I found this comment from Chad:
I believe there is a problem with the latest version of the CKEDITOR. So if you are using the CKEDITOR you might have to change this to be the FCKEditor, Telerik RAD Editor, Cutesoft editor etc...
Does this apply?
|
|
|
|
|
Josh Slaughter
going with the flow
Posts:55
|
| 09-06-2012 08:07 AM |
|
I don't think this applies. I'm using the TelerikEditorProvider that ships out of the box for DNN. I haven't installed any other HTML providers in the site. I did just upgrade to DNN 6.2.3 thinking it could have been a bug in the DNN core, but the problem still exists. Any other ideas? |
|
|
|
|
Chad Nash
Posts:5260
|
| 09-06-2012 12:05 PM |
|
Hi - I have been researching this today Josh and I think the error is related to either a JavaScript file that is missing or not getting rendered or, this specific module code is not conforming to the jQuery.NoConflict() and this is causing the problem. A few quick checks... 1. Do you have the file called dnn.controls.js loaded? 2. Do you have the problem when signed in as an admin or only when in view mode as a user? I did find a few other threads that might also shed some light on this while you are researching... http://www.datasprings.com/dnn-modu...enu-broken http://www.datasprings.com/dnn-modu...-with-skin Thanks, -Chad |
|
|
|
|
Josh Slaughter
going with the flow
Posts:55
|
| 09-06-2012 12:19 PM |
|
Hi Chad,
- I do have the file dnn.controls.js loaded in the dom
- The problem is when signed in as an Admin. When I am not signed in, I don't see the errors and the form seems to work fine
I checked out the first thread and it doesn't exactly seem to describe what I'm experiencing because from what I can tell, I have all jquery turned off that I have the option to turn off.
The second thread isn't quite it either because the custom skin that I'm using doesn't have a menu being rendered at all, just the default standard admin/host menu. The skin that doesn't have the menu is also explicitly set for the page. It's not relying on getting the default skin for the site. I did try to add the module to another skin and I still have the same error. Some of the links that use ajax calls are the ones that seem to be broken mainly from the main DNN menus. |
|
|
|
|
Chad Nash
Posts:5260
|
| 09-06-2012 12:46 PM |
|
Hi Josh - Can you tell me a few other things:
1. Do you have Firebug for FireFox? If so, please enable Console mode and let me know if there are any other JavaScript errors on the page.
2. I still believe the issue is related to jQuery.NoConflict() but I would have to possibly get host rights to your website if this is the case so I can research further.
3. Can you tell me if this website was an upgrade or a fresh DNN installation?
Thanks,
Chad
|
|
|
|
|
Josh Slaughter
going with the flow
Posts:55
|
| 09-06-2012 01:50 PM |
|
Hi Chad, - I do have Firebug and I've attached a screenshot of the errors that I'm seeing when logged in as admin, theres about 25 errors in all.
- I will email you the information you need for host access to the site
- The website was installed at version 6.1.2 and upgraded from there
Thanks, Josh |
 DF-Javascript_Errors.PNG
|
|
|
|
Chad Nash
Posts:5260
|
| 09-06-2012 02:11 PM |
|
Hi Josh - I just signed in and didn't have any problems on that page. Can you tell me if you have this browser on other browsers, if you have this problem after clearing all of your module cache and so forth? Maybe the website is caching some old JavaScript files.
Thanks,
Chad
|
|
|
|
|
Josh Slaughter
going with the flow
Posts:55
|
| 09-06-2012 02:38 PM |
|
Hi Chad, Try bringing up the module menu and add a new HTML module to that page. This is where I'm running into the problem. The link "Add Module" isn't working because of the javascript error. If you open up Firebug and click on the "Add Module" link to add a new HTML module you'll see the error pop up. I have tried clearing the module cache and that didn't seem to resolve it either.
Josh |
|
|
|
|
Josh Slaughter
going with the flow
Posts:55
|
| 09-17-2012 11:29 AM |
|
I figured out what the issue was. There was a conflict with another module that I was using, PageBlaster by Snapsis. This module was causing the errors in the javascript and was breaking some of the ajax functionality. Once I commented out the PageBlaster module from the web.config everything was back to normal. Thanks for the suggestions and the help! -Josh |
|
|
|
|