DotNetNuke allowprint/minimize&maximize - dotnetnuke

Does anyone know of a DB setting in DotNetNuke, where you can configure ALL modules to disable print or maximize&minimize? Just so I don't have to configure every module individually.
How can I make it a default?

You'll probably want to avoid setting configuration options in the database directly, especially as in this case the configuration options are built into the administrative interfaces in DotNetNuke.
Containers & "Skin Objects"
These two features are elements called Skin Objects that live in a skin or, in this case, a module container. Here they are featured in the core DotNetNuke Minimal Extropy skin (found at /Portals/_default/Containers/Title_Blue.ascx in the website's file system.)
<dnn:ACTIONBUTTON runat="server" id="dnnACTIONBUTTON3" CommandName="PrintModule.Action" DisplayIcon="True" DisplayLink="false" />
<dnn:VISIBILITY runat="server" id="dnnVISIBILITY" minicon="images/DNN-minus.gif" maxicon="images/DNN-plus.gif" />
If the container you wish to use features these elements, you can easily remove them.
Skin & Container Hierarchy
As for setting the default so you don't have to configure each module individually - the way the skin/container system works is as follows:
You can set the skin/container at the following levels:
Host - default setting for all portals
Host -> Host Settings -> Appearance -> Host Skin / Host Container
Portal - default setting for all pages within a portal
Admin -> Site Settings -> Appearance -> Site Skin / Site Container
Page - default setting for all modules on a page
Page -> Settings -> Advanced Settings -> Appearance -> Page Skin / Page Container
Module - setting specifically for a single module
Module -> Settings -> Page Settings -> Basic Settings -> Module Container
I'd suggest for your case you find the container that you like and set it at the Portal level so that every module uses that container, and then you can override that container at the module/page level as necessary.

Even easier is you can make it the default
Go to settings for a module
Mark Collapse/Expand as you would like
Mark Allow Print as you woud like
Under advanced settings mark Apply As Default Settings
Update
Should be golden for any modules added after this -
NOTE: Some versions of DNN in the 4.X range this was a little buggy so had to do it a few times but I have had real good luck with this.

Related

How to enable wp_wcm_async theme module in WebSphere Portal 8.5 CF 06 theme?

Recently, I have applied Fix Pack CF06 to my WebSphere Portal 8.5.
This fix pack provide new feature of asynchronously loading the content in Web Content Manager Portlet. For information Click Here
I have successfully completed step 1, skip step 2 because I don't want to change the loading mask. But I am not able to complete step 3, because I don't know how to enable wp_wcm_theme module in my customized theme. The wp_wcm_theme javascript object is always undefined for my Page.
I have also tried with applying Portal 8.5 Theme, but that also don't work. Any help would be highly appreciated.
To enable wp_wcm_async module in your theme. Open the themelist using WebDav or other client. Move into your theme folder -> profiles. In each and every profile or in the necessary profile add the "wp_wcm_async" inside "moduleIDs" json.
For example :
modeleIDs : {
"wp_theme_portal_85",
"wp_toolbar_host",
"some other modules",
"wp_wcm_async"
}
Save the file and restart the portal server, now you can access the wp_wcm_async theme module inside your theme which gives you access to wp_wcm_async global java script object.

DotNetNuke Popups for login and registration not working

Have 3 sites on same DotNetNuke installation, but for the oldest site the popups don't work on registration and login pages. Instead, the forms are presented in a separated page as if the popup option was not set on site settings.
Already tried many things, some desperate, as:
Use custom pages
Enable skin widgets
Check event log, no errors
Even change skin and container. Gravity Skin has one special skin for popus but that also didn't work
Documentation doesn't point to any dependency, so i'm blind here.
I guess you tried the "Enable-Popups" checkbox. You can find it in Site settings -> Advanced Settings -> Usability Settings.

How to enforce the appearance of a Tab in Salesforce

I am trying to configure a Salesforce application that requires the Case standard object. I have:
Edited the profiles that need to see this object so that they have object permissions to read the Case object.
Set Tab Visibility to Default On
Ensured that the Case object has been included in the application.
My issue is that when I log in as one of the target users, I still can't see the Cases tab. The users could just configure their tab layout via the Customize Tab Layout button, but I would like to enforce the appearance of the Cases tab as it is essential to the application.
Is there any way I can achieve this?
Thanks
Check the settings of your App (Setup - Create - App - Edit Your app):
App: Selected Tabs -> your tab is there
App: Assign to Profiles -> target user profile is there
Check the settings of the target user profile:
Tab Settings: Cases -> Default On
Standard Object Permissions: Cases -> Read
Custom App Settings: your app -> Visible

DotNetNuke - Module settings disapear on new user control

I have a DNN module which renders a user control (view.ascx)
All is ok ( I am logged in ) and I get the DNN settings menu.
however when I add another control and load it like so:
string url = Globals.NavigateURL(PortalSettings.ActiveTab.TabID, "View_Details", "mid=" + ModuleId.ToString());
Response.Redirect(url);
I lose the settings link when the new control loads.
Any ideas? Is there a property somewhere to turn on settings for the loaded user control?
When you have "mid" in the querystring, you're going to be using module isolation (i.e. that module control will show up in the edit skin's ContentPane and will be the only module on the page). When in module isolation, the action menu doesn't include settings. This is just a fact of DNN.
You have a couple of options. First, you could choose another navigation method (see Michael Washington's old (but still good) Module Navigation Options for your DotNetNuke® Module article).
Second, you could put your own link to the Settings on that control. You may be able to implement IActionable and just add it back to the action menu (I'm not sure if that would work), or you can add some sort of button or navigation bar to your module (potentially on all of the controls for consistency).
Are you designing this module for the general DNN community, or for a client that isn't familiar with DNN? People with DNN experience won't expect to be able to get to the settings one they're "inside" a module.

dotnetnuke: can we create a master page?

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.

Resources