Above is the ribbonbar after I have logged in as a super user. The Admin option next to Host is completely gone
The site is running DNN6, the skin is only in the site portal folder, and it seems that all admin modules and options have gone away. Even the header, which I set in Site Settings (under Admin), went away!
Has anyone else had their admin options completely disappear on them? Is it possible that the skin is messing it up (all other sites use the same _default menu files and they work fine)?
Thanks for any replies.
We've recently had this exact situation occur in one of our DNN sites. It turn out that one of the site's administrators had accidentally renamed the Admin page from within the "Page Management" section (it's easy to see how that could happen). The fix was to go directly to /Admin/Pages.aspx and change the "Page Name" back to "Admin" ... and it will show up in the ribbon bar again.
As a suggestion to DNN developers, I would recommend making the Admin page and its subpages impossible to rename....
Can you check the database to see if those pages exist? What if you try to navigate to http://website/admin.aspx do you see the admin page and all the child pages there?
Related
We recently upgraded one of our client sites to 09.01.01 to address a Telerik vulnerability, and then had to migrate the site from managed.com to Azure due to manage.com's outage. After the upgrade, a couple of pages on the site have been uneditable using the pencil icon in the persona bar, although the rest work fine. We're aware of the workaround of going into content > pages and clicking the pencil icon there, but even then not all of the areas on the page are editable. For example, there's one instance of the HTML module on the homepage where when you click on its pencil and then click "Edit Content," it just displays a pop-up with the text but no WYSIWYG or way to actually edit. Other instances of the HTML module work fine, on other pages and even other areas of the homepage.
What's more bizarre is that we just spun up another Azure VM and created a dev site from a clone of the live site so we could troubleshoot further, and this problem does NOT occur on that site even though it's an exact copy of the live site files and database and both sites are hosted in Azure.
Does anyone have advice on what might be causing this or how to troubleshoot? My original though was to clone the page and start removing modules one by one to see if anything made a difference, but it doesn't actually remove the module when I click delete. I've read about ways to do this directly in the database, but I'd prefer to avoid that if possible, especially since we're not seeing the same problem on the cloned site.
Thank you!
Could you please see if any error appearing on the logs folder? You can see the logs here. /Portals/_default/logs/2021.02.01.log.resources? The log file name may differ based on website's logging configuration.
A similar thing can be seen from the Personal bar as well using Admin Logs.
I'm a beginner with DotNetNuke and am having trouble debugging this problem. We are using DNN version 5.
On our local development machines our DNN site renders just fine. But we recently deployed to our test server and on there the site only renders fine when logged in as the Host. When viewing the site as just a normal visitor, all the styles are messed up -- it is just a white page with images gone and menus stacked vertically.
Clues / Notes:
We recently added a new .ascx and module
There are javascript errors, but it hard to tell what is causing them
You may ask about the Log Viewer screen. I looked there and I see exceptions, but I think the exceptions there are unrelated ( will look into this)
Works fine in our local dev environment
In server, only renders fine when logged on as Host
What are some steps I can take to try to debug this? Where else can I look besides the Event Viewer to see what is going on here?
Thanks!
What is the "new .ascx" that you deployed? Is that a skin page?
If something is wrong in the skin page and it is the default site page (under Admin > Site Settings), that would explain why non-admin users have issues, but Admin/Host users (where the site's Edit skin is working) don't have issues.
This solved it:
https://stackoverflow.com/a/3831419/614263
Due to permission settings it looks like IIS was blocking requests from the root to javascripts and css files. When looking at the Network traffic in FireFox I noticed that 404 errors were coming from "login.aspx?ReturnURL=../../blahblah.css"
Thanks for all your help and suggestions.
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.
I've just started using dotnet nuke (v6.2) today. I've uploaded a new skin and applied it. I've also added a new page to the website. When I'm logged in as admin I can see thenew page and it's all styled with the new skin. However, when I browse the site without login it's styled using the default dark knight skin and I can't see my new page.
Can anyone please tell me what step I've missed?
Although I'd changed the skin for the site under the appearance menu - the skin for the individual pages was still set to Dark Knight. I changed this to be site default and now all is good :)
I can see two possibilities for why you'd see a different skin when you're logged in. First, if you're using DotNetNuke professional, you could have page caching turned on, and need to wait for the cache to clear (though changing the skin should clear it automatically). Secondly, it could be that there's an error in the skin when you're logged out (if there's some custom code in the skin which determines whether you have an account or not). Check the log viewer to see if there are any errors being logged when you visit the site logged out.
I am new to DotNetNuke and Mistakenly have disabled the landing page of the my site built in DotNetNuke and now i am neither allowed to access my site nor am i able to login to my site.
How can i re-enable the disabled landing page.
Any suggestion will be highly appreciated.
Thanking you in advance
http://www.yoursite.com?ctl=login
This will allow you to login aa then you can update the settings.
You will likely need to get into the database and edit the PortalSettings table's content.
What setting did you actually change on your website? One of the "pages" drop downs from the Admin/Site Settings?
Look in the portalsettings table and find the columns for Login Home Splash page, etc, and set those to Null.
Though if you didn't change that, perhaps you mean you changed the "default" page in IIS? IF that is the case try going to www.yourwebsite.com/default.aspx?ctl=login to login