Today I was looking for a skin to edit but I accidently clicked apply button of a skin. That skin is for displaying videos. Now when I click any item in admin menu I am seeing my video page template and its completely empty. So now I can't do any changes in admin menus. I looked also in database but I can't find anything about it. Now I must to revert it. Any ideas? (Running DNN 6)
The apply command will replace the default skin in the settings of your website.
You could find this setting in PortalSettings table. Its name is "DefaultPortalSkin".
I suggest you to update its value with "[G]Skins/MinimalExtropy/index.ascx" which is the default value for DNN6. You also could update the "DefaultPortalContainer", if you need, with "[G]Containers/MinimalExtropy/Title_Red.ascx" for example.
FYI [G] means that the skin is located in /Portals/_default, [L] means that the skin is located in the portals folder.
In addition, don't forget to restart the corresponding application pool because of cache mechanisms which keep the old settings in memory.
You also could rename the folder of the current selected skins in order to force the website to load the default skin. It will permit you to go to the site settings to select the desired skin.
Related
I have a portal with BackEnd and FrontEnd sides.
I use skin A for BackEnd, skin B for FrontEnd.
I create a page P1 on FrontEnd and then drag a module with two controls:
Control ListItem: Key = black, to show all item
Control Detail: Key = "Display", to show item in detail
When P1 is shown up, the skin B is loaded correctly (Skin of FrontEnd). But when i click on an item, the skin A is loaded (Skin of BackEnd). I don't know why and how to solve this problem.
This is link of all Item: http://dnndev.me/vi-VN/dich-vu/cateid/104
This is link of one item: http://dnndev.me/vi-vn/dich-vu/ctl/Display/mid/544/id/88
Thanks for your help :)
With DNN, when you load a secondary control the site moves into "Isolation Mode". This isolation mode uses the "Edit Skin" as defined in the site settings, rather than the actual skin that is created. (It also removes all other modules from the page.)
To combat this, you might need to handle control switching on your own. (Without using the ctl or mid parameters that trigger Isolation Mode.
I have a DNN 7 site. For new pages that are created in the portals, we want "All Users" to be checked under View Page by default.
How do we do this? I think I've found the right template file:
/Portals/_default/Templates/Default.page.template
But I can't find any documentation about the tags therein.
It does have:
<inheritviewpermissions>true</inheritviewpermissions>
But where are the view permissions inherited from? And how to override them?
Again, we want it so that new pages are viewable to all users by default; no need to go change anything after new page creation. (Yeah, I know, but that's the requirement.)
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 sitting with a situation where I need to check how many pages in my site are using a specific skin. In Sitefinity, you can check which pages are using a certain template and I wanted to know if this is possible in DNN please?
Thanks,
James
If you have access to your database, this code will get you all pages in DNN that override the default skin with the store_limited skin.
select TabID, TabName, TabPath from tabs where SkinSrc like '%store_limited%'
Confirmed working in 5.6.0
To run this code from within DNN
Login as Host
Go to Hosts menu
Click on SQL
Select your DNN connection string
Paste in the above code
Press execute
Can we create a content managed master page in dotnetnuke?
eg. I want the right pane and bottom pane to be content managed, but to show the same thing across all pages.
Thanks
What you are describing is essentially what DNN calls a Skin.
A DNN skin is actually just an ASP.NET user control (ascx) that dictates page-wide or site-wide look and feel, which offers developers the same functionality as a Master page, except that it ties into DNN-specific elements and uses some DNN-specific user controls, such as menu/navigation, logo, breadcrumbs, login/user account links, etc.
Now, in order to add the ability to provide content management capabilities site-wide, you specify an area in your skin to place a module (let's say, a Text/HTML module). This area is called a pane. Once you add a module to this pane, in its settings you can tell it to appear on every page. This way, the module can be edited on any page, and its changes will be reflected on all pages automatically.
Check out DNN's site, as it contains a TON of documentation on how to do many common tasks: http://www.dotnetnuke.com/Support/Documentation/DownloadableFiles/tabid/478/Default.aspx. Under the Technical Documentation section, you'll want to grab the Skinning document (I believe it's a PDF).
DNN Modules can be set to appear on all pages by checking a checkbox in the module settings. However DNN does not use the concept of a Master Page. It injects modules (user controls) in containers on a single aspx page at runtime.
A Master Page would be a great addition to DotNetNuke you cannot replace content in a single area of the page. The whole page refreshes. For example if you have a menu and you only want the content of what you select to appear in a specific content area without refreshing the rest of the page you have to resort to third party modules that attempt to do that but usually fail. There are 'module wrappers' but all the ones I've tested have issues with modules that allow the user to edit content. Edit screens are usualy different user control files (ascx) that are launched when you edit the module content. Since the page refreshes with the new page you have lost your place. Those module wrappers work fine for static content and some other controls but not for all controls.
IFrames can be used (DNN has one) to trade out content but that doesn't get rid of the probelms mentione above. I'm heavily invested in DNN, running the UCanUse.com web site so this isn't a slam on DNN. I just thought I'd try to answer the quesiton with detail.