We recently upgraded an old DNN site to the latest version (9.8.00). Everything has been running fine for the most part, but today I have ran into an issue I can't figure out how to resolve. Once of my users dropped an HTML module on the page but we can not get it to display outside of edit mode. I have tried adding an HTML module to other pages as well to see if it was isolated to an individual page, but it's doing the same thing across the entire site. I have tried all of the following things to no avail.
Debugged the page to make sure no errors where being thrown and none are.
Stopped inheriting permissions and made the module visible to all users.
Changed the Cache settings for the module to 0.
Verified the site was running on .Net 4.5.1 (I'm actually on 4.7.1).
Tested two other modules (link and event), both of these modules display outside of edit mode.
I am at a loss at this point. The HTML module is showing as version 9.8.0, but has an upgrade version as 10.0.3. So I'm not sure if that means it needs to be upgraded or it has already been upgraded.
Any help would be greatly appreciated.
Recents versions of the HTML module have this behaviour: they doesn't appear when they haven't any content. After you add some content, they keep displayed.
I think this feature is related to the default template which is containing an empty HTML module.
Related
A recent problem has arisen with a Drupal 7 site. When I attempt use the aggregate CSS/JS functionality in the performance page it doesn't work, the styling has gone and the JS elements do not work.
The strange thing is that clones of the site work fine, both locally and also on another of my web spaces.
The links to the aggregated items seem to be there, and contain data, but they do not appear to be available when I view them in another tab (nothing is shown).
I have checked the folder permissions and they seem OK. The site is fully up to date.
One thing I just noticed was that upon changing the CSS, a new file was created in sites/default/files/CSS but a link to this did not appear in the HTML.
I've got a really weird bug in a create-react-app application. Onsenui is used as a css framework. But when I try to run the app, either in production or on localhost on a chromium based browser, the framework doesn't get loaded. Both css and js aren't loaded. (Only the OnsenUI ones, other css and js is loaded correclty) I then have to refresh the page multiple times to make it work. It loads correctly on Firefox and Safari.
The problem persists on both my MacBook and my Windows PC. I'm not the original creator of the repo and it's already a few years old. I have however updated onsenui, react-onsenui, react to the newest version.
Unfortunately, I can't share the link to the page.
So, in the end, it's been all because of a pop-up blocking extension I had installed. I can't believe I haven't thought of it and I've been refreshing the page multiple times/had to use other browsers just because of this.
So if anyone ever sees this is the future with a similar problem, double check all your active extensions.
I have an application that I build using VB.NET and angularJS in DNN with the Christoc.Module module. There seems to be 2 issues. When I build my project and refresh the page on my site, I will receive an error 500. The same result happens on the site unexpectedly after being idle for about 30 minutes. I have tried to change settings on the website web.config to see if it was a session expiry timeout, but that doesn't seem to be the case since all pages that where access before the error are fine, and can access server functions.
I was wondering if anyone has ever seen something similar.
I use ng-include to show the current "active page". I have tried using the AngularJS $route and the same behaviour occured.
<div class="animate-repeat" ng-repeat="path in PathLinks| filter:{'path_name':variable}:true" ng-include="'/DesktopModules/module/path/' + path.path_name + '.aspx></div>
CLick here for image of the issue
I ended up simply recreating the whole module with a newer version of the visual Studio DotNetNuke Compiled Module. The original module was created using an older version of that extension. This seemed to have completely fixed the issue for me.
I recently started to learn about AngularJS and came across WebStorm and the AngularJS plugin by John Lindquist. Started by creating a new project using the angular-seed project and imported to WebStorm using File -> Open Directory. My directory structure looks like this
Now when I try to Debug it I get a 404 error. If I move the file app/index.html to the root folder and adjust all URL's to begin with app then it works fine. Is there a way to keep the default folder structure without moving the index.html to the root folder and also make it work with WebStorm?
I am using WebStorm 6.0.2.
I use WebStorm 7, so there might be some discrepancy in comparison with version 6 that you're using, but the over-all functionality is the same.
Quick solution:
Open the file in the editor and right click in the code to access the context menu. Choose the "Debug" option, which should start a debug session pointing to the current page.
Configuration solution:
WebStorm supports configurations for setting up different debugging scenarios. From the "Run" menu, choose the "Configurations" option. Add a JavaScript debug configuration, and add the URL you want in the designated field within the dialog presented.
Then, when you initialize a debugging session (a general one, not one for a specific page), you're presented a small dialog that allows you to choose a debug configuration.
Maybe there are more options or ways to accomplish the same thing as well, but I've never really given it more thought. I hope this is a working solution for you, but if not there's alway the documentation. If you need further clarification with regard to my answer, just give me a comment.
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.