I'm developing a module for DNN 6.0. I need to add a menu to the module, each item in the menu will load a usercontrol into a placeholder.
I'm missing the menu stuff any1???
10x
Module level menus are not supported by default in dotnetnuke module development.
There are many ways to implement it, which is similar to normal asp.net development.
You can use query string, you can use asp.net menu and handle it's click event and there is an endless list of ideas.
Please add some more specific requirements to get exact tip on how to handle that smartly in dotnetnuke.
Thanks for the reply.
I ended using "asp:LinkButton". I had problem with the asp.net menu.
10x
Related
I was installing some modules in Drupal 7. Suddenly, the helpful buttons across the top for admin mode disappeared. Can anyone tell me what happened and what I have to do?
I am able to go to {website}/admin and essentially see the same buttons on the page that, I guess, I would see across the top of the page, but I wonder if I am missing out on some functionality.
But even if I still have the functionality, I still can not find the place where I can install new modules, and the system is telling me I need the "views" module to view some content I need to manage.
What do I heed to have enabled in the modules to view these buttons across the top? Is it called "dashboard"?
Also, if I never find a way to see these buttons, where is the page that will let me add a new module?
I do not understand what exactly do you mean. Which buttons? The black admin toolbar?
Dashboard is a module for creating a special page with different admin view blocks.
Anyway, the page for modules administration is available on /admin/modules in Drupal 7.
I think your administrative toolbar is not visible.
Check whether the module named Toolbar is deactivated in admin/modules. If Yes, Turn it on. It will solve your problem.
If not solved, kindly explain your issue.
"Welcome to your new website" popup in DNN 7.2 and above shows some dynamic content. Its visible only to host users and doesn't reappears if "don't show this again" checkbox is checked once.
I need to develop something on similar lines where a popup should appear every-time a user of specific role(and some business logic) logs in. I think about creating a custom module and add it to all pages which could this for me but it seems welcome to your new site popup already tackles this.
Now I need to know if its somehow feasible to alter or extend this popup as per my need. I googled for some time and went through quick search in DNN code but haven't found anything convincing on this. Please suggest if what I think with this popup is feasible or I am searching in wrong path and creating custom module is my only way.
Thanks,
Ravi
I would think the best way to handle this would be with a custom skin object, and a custom module to manage the announcements.
I have create a DNN Module using the Visual Studio DotNetNuke 7 C# Compiled Module template. When my module is installed, I would like to create a page for View.ascx. How can I do this? Can this be done when I upload the module in Host > Extensions?
From the Control Panel you should use the Add new page functionality, then place your Module on that newly created page.
Check out this video for how to Add a page in DNN7.
http://www.dotnetnuke.com/Resources/Video-Library/Viewer/Video/549/View/Details/How-to-add-a-page-in-DotNetNuke-7.aspx
And this one for how to adda module to a page
http://www.dotnetnuke.com/Resources/Video-Library/Viewer/Video/537/View/Details/How-to-add-a-module-to-a-page-in-DotNetNuke-7.aspx
To answer the question specifically about having this done automatically with the module, yes, you can, BUT you have to write code to do this and I only recommend it for special circumstances.
I've seen this done using an implementation of the IUpgradable interface in DNN to detect an initial installation and create the page using DNN API calls.
There is some detail in the Wiki about how IUpgradable works
I am new to DOT NET NUKE 6.0 and facing a problem. The scene is that I have created a very simple user control in Visual Studio(by using ASP.NET/C#). Now I just want to add it as module in my DNN portal. Task is simple but I don not know how to do. Any help, video link, site is appreciated. I am working in DNN 6.0
Thanks
There are a bunch of resources on the DotNetNuke.com site. Take a look at the wiki entry at http://www.dotnetnuke.com/Resources/Wiki/Page/module-development.aspx. It has links to a video series that should be helpful to get started.
If you already have a control, you should make sure that it inherits from PortalModuleBase, and use the Extensions module (under Host) to create a new module from the control. DNN will create the record for it, and even create a test page with the module on it for you.
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.