We have a DotNetNuke app with a DNN Menu.
Recently, after updating to FireFox version 17 we found that the whole DNN Navigation Menu is invisible. In other browsers it is fine, and it also works fine in FireFox 16 and earlier versions.
Does this have anything to do with the browser settings?
Firefox changed their user agent string. Here's the fix: http://www.dotnetnuke.com/Community/Community-Exchange/Question/2733/Firefox17-Bug-How-to-change-User-Agent-String.aspx
We found a solution that may help. Our menu was displaying, but expanded the entire thing out as an unordered list. We're on DNN 5.6.0 and using the DNNMenuNavigationProvider.
We installed the DDRMenuNavigationProvider here:
http://dnnddrmenu.codeplex.com/
With detailed instructions here:
http://www.dotnetnuke.com/Resources/Wiki/Page/DDRMenu-user-guide.aspx
We simply then went into the skins and updated the same dnn:NAV controls to use the ProviderName="DDRMenuNavigationProvider" and the menu came back the way it was, with an extra sliding flyout animation.
Hope that helps.
Update
In addition to updating the navigation provider, and the user agent as described above, we also updated the \js\ClientAPICaps.config file based on these instructions:
http://support.dotnetnuke.com/issue/ViewIssue.aspx?ID=13964&PROJID=2
We reverted the update for the dnn:NAV controls back to DNNMenuNavigationProvider and everything went back to the way it was operating before.
Firefox released a patch, 17.0.1, which fixed this (for now) for my situation. This bullet item from the release notes is about this issue:
17.0.1: Reverted user agent change causing some website incompatibilities.
Related
I recently upgraded 8 websites to DNN v. 09.02.02 (178), one of them is the host/main site and has additional menu options. On this site I am unable to edit pages, you can open the Pages list and see the pages but when you click on one all you get is an error (An error has occurred) so you cant get to the page properties. I need to change permissions and delete a page but am unable to do so. The other 7 websites all work fine in this regard. Any ideas?
What happens if you navigate to a page, put it in Edit mode, and click the edit page (gear) icon at the bottom?
I've not encountered any problems editing pages in 9.2.2. I think that they were all upgraded from earlier 9.x or a clean 9.2.2 install. From which version of DNN did you upgrade?
Are there any errors in the Admin Log (Event Log)? Or in the /Portals/a_default/logs directory?
I have tried using it on local site, on hosted sites, even on the Angular sites, and all I get is a listing of the HTML with Angular. No scopes, no models, nothing useful whatsoever. I'm assuming it's supposed to help develop with Angular in Chrome, but, nothing.
Has anyone found a reason for this?
Using
Chrome Version 39.0.2171.71 m
AngularJS v1.2.26
AngularJS Batarang 0.7.4
I found this old version and it works.
https://chrome.google.com/webstore/detail/angularjs-batarang-stable/niopocochgahfkiccpjmmpchncjoapek
I had the same issue, so I rolled back to the previous version. if you follow this link, it will give you the instructions - I will add them here also in case the link moves.
Installing Previous Versions
Download and extract one of the files from the Batarang releases page on GitHub
Navigate to chrome://chrome/extensions/ in Chrome
If you've installed Batarang from the web store, disable or remove that version
On the top right, check the checkbox for "Developer mode"
Click "Load unpacked extension..."
Select the directory where you extracted the extension
Close and re-open any inspected tabs
The above was taken from the same link as I posted.
I am working on a site: greatlakesecho.org When I try to edit a post, the content just disappears from the visual editor. I am running the latest version of Word Press but this happened on the previous version as well. I am using the Project Largo theme with the site.
The site was recently migrated from to a new host and has gone an overhaul into a responsive design. This first started happening when I changed the character encoding to remove odd symbols from the posts. I was successful in that by changing it to utf16. At this point only older posts that were created before the migration would disappear when I clicked edit. I have since updated to the latest version of Word Press and it happens to every post.
I've already made sure the wp-config has the correct encoding.
It happens with all themes.
Tried deactivating all plugins.
I also see this when enabling debuggin:
WordPress database error: [Table 'greatlak_wp776.wp_itsec_lockouts' doesn't exist]
SELECT lockout_host FROM wp_itsec_lockouts WHERE lockout_active=1 AND lockout_expire_gmt > '2014-04-22 19:52:36' AND lockout_host='35.9.132.246';
WordPress database error: [Table 'greatlak_wp776.wp_itsec_lockouts' doesn't exist]
SELECT lockout_user FROM wp_itsec_lockouts WHERE lockout_active=1 AND lockout_expire_gmt > '2014-04-22 19:52:36' AND lockout_user=93;
edit: Extra Info
Wordpress has this documented on their documentation. It can be found here, of course you will be converting to utf16 instead of utf8. http://codex.wordpress.org/Converting_Database_Character_Sets
Check your wp-config file's encoding, make sure it's set to utf-16
Activate a new theme, see if that still happens. If so, it was a theme issue.
Deactivate all plugins, see if it still happens. If so, reactivate 1 by 1 and see when it happens again.
Also, check your browsers console for any errors
I had to remove the Navis Media Credit plugin manually. I searched through the plugins folder using WinSCP and apparently when I was removing all the plugins using the WordPress admin panel, this one wasn't actually getting removed. This plugin was conflicting with the theme I am using and I learned this by deleting all the plugins and using one of the default WP themes.
It may be a Chrome Extension. Here is what I experienced...
In Chrome - a Wordpress site loads the Add New Post screen which appears to get overwritten - this happens after typing a few characters (not immediately) in the title or body. Updated theme, removed plugins, no change. At one stage noticed a bug in html2canvas.js but now cannot reproduce.
Tested in Firefox, works fine.
Traced to a Chrome Extension - Screen Shader - F.lux for Chrome 1.7.720 - one that removes BLUE from Chrome display (for night work). It probably does use use html2canvas. When it is deactivated, Chrome again behaves normally. Tried with another plugin "Blue Light Filter Guard" - not as well featured - but it does not trigger the bug.
May not be the same as your problem, but try in Firefox and check your Chrome Extensions.
I have a website running on dotnetnuke. However, recently I can't do any action (edit content or page setting) on certain pages (the products subpges in www.midoco.com). Does anybody know why this happen?
What version of DotNetNuke are you on? Check the HOST SETTINGS page to see if you are using the HOSTED Jquery option, if so, try disabling that option.
It is probably a javascript issue, try firing up chrome developer tools (hit F12 in chrome) and check if you have a red X in the bottom right corner. If so, click it and check what causes the issue. I had some similar issues caused by single quotes insted of apostrophes in a language pack and spent a lot of time to find the issue. I just went to one of the pages and see you have an error in /engine1/script.js in your skin.
One of my DNN 7 sites has lost its ability to edit any of the pages. It now alway displays the Modules, Edit and Pages menu regardless if admin is logged in or not. When I try to edit a page, a window appears and then quickly goes away. There is nothing of use in the event log and I have tried different skins with no luck. I have another DNN website on the same computer and it works fine.
I have found that I am losing permissions to ToggleUserMode after I recompile a custom module that I'm developing has been installed on a test page and then recompiled in debug mode.
I'm wondering if this can be related to the fact that when I install DNN I blank out the default installation option of creating a dotnetnuke application. I leave that option blank and create the installation in the root of my website.
P.S I tried the amended module tag suggested on SO without any luck.
I finally figured this out. I had originally bound www.example.com to my default website but later created a new site for www.example.com. Apparently most of the requests were going to my new site, but the request for authorization for page editing was going to my old site which resulted in the 401 error. I rebooted my computer and disabled my default website and all is well.