I have the community edition of DNN. I created it with the default Awesome Cycle's store. When I edit Products list on footer of the home page, it does not persist to other pages. Where can I make a change to make that persist across the site?
You'll want to check the "Display Module on All Pages" checkbox in the Module Settings if you want the content to be duplicated across all pages.
Go into the settings of that footer module in page settings under Advanced settings you can check Apply To All Modules checkbox and your footer will display on all pages.
Related
I am using DevExtreme react template in my react js project from below link.The router page navigation is working fine as per my requirement.I would like to know how to use router page navigation as in "Tab" instead of single page.For example if we take from below link,there are two pages in sidebar (profile and display data pages).If I click "Profile and display page" ,both the pages should display in Tab but currently its shows only current page.hope its clear.
https://devexpress.github.io/devextreme-react-template/#/home
I also want to note that you can contact DevExpress support team directly at Submit a Support Ticket. They answer questions in 24 hours, so you will be able to resolve the issue faster.
Is it possible to add custom pages in the admin sidebar and remove the "Pages" link. I want to have different links such as:
Blog Posts
Pages
Events
Games
Shown in the sidebar and each listing page only shows items based on the custom page. I have been looking in the documentation and the only thing that I found was to add custom URLs to the sidebar but I need to also add custom pages to show listings.
The ModelAdmin module allows you to register page models to appear as new items in the admin menu.
You can add exclude_from_explorer = True to your ModelAdmin definition to hide a page type from the main page explorer, although that won't hide the Pages menu item itself - for that, you would need to define a construct_main_menu hook to run after the menu has been built, and remove it from the list.
I'm creating 100% custom theme for a DNN website. Whenever I apply it, the admin pages also get the theme. I don't want that nor need it. The admin should stay with the default theme it came with.
I'm on Admin > Themes and when I select my theme, I don't get any options to only apply to the Site and not the Admin.
How can I fix this? I'm I doing it the wrong place?
Go to the "ADMIN" page (click on Admin). Go to the PAGE SETTINGS on that page.
Choose the skin for that page. Choose the apply to children option as well so that it propagates to all the "child" pages of the Admin page.
You likely will want to do the same on the HOST page.
Chris
I have a Drupal website with 3 menus (a top menu, a main menu and a footer menu), and any content I publish belongs to one of those 3. My clients wants me to show the correct menu as an accordion on the sidebar, as a navigational support. I've looked all over drupal modules and can't find anything similar. Any thoughts?
I found it. it's called Menu Block
I'm running a dotnetnuke project (v7.0) with 2 portals.
I need to remove the default DDR menu from one page only.
The menu works great now with multiple pages and sub-pages, however on 1 specific page , ie landing page, I don't want to show the menu.
Right now I can think of 2 methods for achieving this:
Create a new skin template, remove menu, apply template to that one page
Use jquery to detect URL, for that page hide menu.
I'd rather just code the logic inside the template file, but I'm not strong in .net/c# and I'm new to DNN.
It's just one page today.
However, if you are using it for a landing page design I would recommend you just create another skin and exclude it from that and tailor that skin for that need.
That way when your non-technical editors need to work on the site and make a page that might only be used when linking from Google Adwords or whatever they can pick a template without that navigation and you as the developer/designer don't need to edit the skin to put in another exception based on the URL.