I am novice programmer to Dot net nuke.
Login as Admin:
1) I add a page in Home -- Department. Department page have on Text/HTML module which have some lines ie (Welcome to DNN.)
2) Now click on Home page then add this page (Control Panel --> Add existing module) to Home Page.
3) Now as we can modifying data of Department Page, either from Home page or from Home--> Department page, which will be reflecting on both pages.
4) We want that modify option (Edit Text) must be available with Home --> Department page only. There must not be no editing option at Home page to edit Department page.
How to do that?
I am using Sql Server 2008/DotNetNuke_Community_04.09.05_Source / ISS V5.1/ VS2008.
This isn't really possible in DNN, if you have the ability to EDIT a page, then you have the ability to edit any MODULE on that page, including modules that are copied from other pages.
You could remove the ability for the person to EDIT the homepage, and then only give them the ability to edit certain MODULES on the homepage instead.
FYI DotNetNuke is spelled without any spaces, and is actually now just DNN or DNNPlatform
Related
I want to create a 2sxc app that has a listing of items. When a user clicks on an item, it should open the details view in a modal window.
However, I don't want to simply load all items into the page and have a JS open the modal. Ideally, I would want the modal to load the content only when it's called. Also, ideally the URL would still in place similar to how there's a listing and details templates in an app.
Is this possible?
Yes, this can be done :)
It basically needs 3, optionally 5 steps
Open a DNN page without a layout
(optional) make sure only your module will be on the popup using mid=... parameter
Make sure you add the id/name-id/guid of the details in the link such as post=...
Create the razor view which shows the details, ensure it appears when the parameter is added
(optional) Create different urls for google / user so user sees the popup, google indexes a real page with the details view
1. Empty Skin / Layout
The trick is to open the page using the DNN parameter to either switch to the layout-free skin (print), or to another custom skin. This allows you to start with an "empty" page without stuff around it. Either use popUp=true in the url (the Up must have an upper case U) or a skin parameter to choose another skin
2. - 4 MID, url-parameter, name in url to select view
This MID is common - if you have mid=... DNN will not load any other modules on the page.
Same with the named url parameter for the details-id and view switching, so I won't document this in detail.
5. Different details for Google vs. Interactive
In case you want google to index the details view, that would probably want the indexed page to have a layout. So create a link to the details without the special popup, and on-click only change it to open the link with the popup feature.
I have a Joomla website here and when you click on an article from the homepage it stills displays all of the home page modules. I went thru the settings for each module, and it is set to display only on the home menu page. I go to the menu setting that the articles are under and the settings stated the modules are published but not displayed. Any help would be appreciated!
I discovered the issue was due to a category error. The category is supposed to auto create a page for itself, however, it did not happen for whatever reason. So I had to delete the category and then make the category again and everything was fine. The reason the home page modules were appearing on articles is because that's the default behavior of Joomla when it can not find a specific page.
I have an issue with DotNetNuke where only the admin can see a new page I've added in the main navigation (the page appears in sidebar for all users)
After creating a new page with DotNetNuke, I can manually browse to the page, and all links to it work however it is only visible in the navigation menu when I'm logged in as administrator.
Manually going to the page works fine when not logged in. Include in Menu? is checked (and been toggled) and I've tried all variations of permissions I can think of (which apart from the navigation issue work exactly as I would expect).
I hope this is the correct format I'm still relatively new!
Sounds like you have the page settings set to admin only for view... navigate to the page click on pages>page settings. click on the permissions tab and make sure inherit page settings from parent page is unchecked. Then next to All Users, Registered Users, Subscriber,
Translator (en-US), Unauthenticated Users and Unverified Users make sure there is a green check mark in the view section. Then make sure that page is disabled in advanced settings is unchecked and include in menu in page settings is checked.... Hope this helps... If not try making a new page and copy all the modules from the old one and see if that works
I would like to make sub pages under and existing page. Lets say the page is "Success Stories" and under this page the user can enter in other pages and format them any way they want. What I need is a way to make a repeater of all these subpages with stuff like the page title, a little bit of the content, and a button that links to the actual page.
Is this possible out of the box? I am willing to buy a module if it is reasonable;however a Google search returned no results.
Thank you.
The best option I know is Child Links from Ventrian.
You can show all children with title and description & links. (NOTE: description is Page description NOT content from the page.)
what version of dotnetnuke are you using?
Two options:
ONE
There is a copy page function where you can choose what modules and setting to copy to the new page.
Under the pages menu - click copy page
then you can select what page to copy from, and then it will list all modules on that page. You can choose to copy the module with or without content or even reference the module on the source page.
TWO
Other than that you can create a page template that a user can select that is pre-designed by you. Create the base page the way you want it and then click export page under the page / edit page menu depending on your version. A template will be created in your portal template folder that can be used when creating new pages.
If you are looking to automate this process, then you will have to look into a custom module or design a sql script you can run yourself (but this is a lot more maintenance as it can change with every version.)
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.