How can i add new ascx page to the dotnetnuke module? - dotnetnuke

I want to create a webservice to my module . Mainly there are three pages in dot netnuke module . 1)edit 2) setting 3)view pages . how can i add one more page to the dotnenuke module saying webservice . i wan to get this page in manage button as edit and setting page comes .

You can add additional ASCX files to your project, but you then need to "Register" them with DotNetNuke, you can do this manually via the module definition on the HOST EXTENSIONS page, or you can update the .DNN manifest file to include the new ASCX registration.
To link to them using the MANAGE button (actions menu) you need to add a new ACTION item calling the URL to that ASCX file.

Related

How to edit Default.Page.Template Content in DotNetNuke?

How to change home page content in DNN while creating a site itself.
I need to change different page. I created a new page and created Template. And I replaced inside Templates folder named (Default. page. template). But it is not working out. Provide me a better solution.
Probably the easiest way to do this is to create a site using the default template, edit that site to create your own site, and then save that as a site template (suitable named). You can then use that site template to create sites with the page structure that you want.
The default page template (I believe) is used when you create new pages using the the Pages UI. I don't believe that the default page template is used by the default site template.
If you have created a page and would like to apply a specific page template to the new page retroactively. To do this, go to the page that you want to change and append ?ctl=ImportTab to the url. That will bring up a dialog that allows you to change the emplate for a page with lots of options. It

Module Repeat on selected pages

How to repeat HTML module with content on selected pages?
Not on all pages
I know there is an option to display module on all pages under module setting.
Use the "Add Existing Module" function to handle this.
For this First of all add HTML module on page.
To add that HTML module on another page use Add Existing Module instead of Add New Module.
You can choose page from drop down on which you added HTML module.
Then add to new page. Content will also be placed.

Installed DNN Module - Not showing in dropdown to give link

I had an link in my DNN site Menu - pointing to aspx page of my installed module.
I replaced this link with an external link.
And now i wish to change back to old one - aspx from module. BUT am not getting that listed in the dropdown
How to get that back or I missed anything ? I could found the module still in that EXTENSIONS.
Please suggest
Rigin
I think you may be a little confused,
Modules are placed on pages, (One or mor module generally makes up a page.
Menu links refer to pages,
To add a module to a menu it must be on a page.
Once you have placed you module on a page you can select it from the select a web page drop down
A dnn module got 2 pages a view page and a settings page. So you must be sure that your module start's with the correct page.
So what you want is not possible the way you want it.
Best way for you is to control the page in your module. You can control this with for example a user controls(ascx). See image for a default module view.

Remove Default Modules to ContentPane

I have limited knowledge on DNN, I designed new skin,container for pages and I can able to create pages with new skin.
But While create new page, there are few modules are automatically added to "contentPane" place holder.
Do you have any information about how to remove these automatically added modules to contentpane? (FYI, I am using latest DNN version)
There are two ways that modules are automatically added:
By default, the HTML module is added to every page. When you create the page, there is an option that shows the HTML modules selected. Before you create the page, just delete that module from the list.
There is a module option in DNN that says, "Add this module to EVERY page". You need to find out which modules are getting added and change that setting in that module.

dotnetnuke clicking left bar opening page on the content pane(BEST PRACTISE)

ok i have created a picture gallery module in the left bar , there is a page viewpicturegallery.ascs . on clicking any image i want it details to open in the content pane in the middle . how would i do it.
can some tell me the process? i would made a new page or new module or what? for the details in the middle
here are some steps you can achive it:
create two controls in a single module for showing images and showing details for a single image and create two different definitions, each having a default view control as the one you want to show.
when you install the module in the page, it will show both definition controls in content page, you can re-arrange them in whatever panes you want.
search for inter module communication in dotnetnuke and grab a sample from net
you will find that there are two module definitions participating in the communication. Your list control will be the IModuleCommunication and your details view will be your IModuleListner
That's how you can achieve the things you want.
Please tell me if you have any other questions.
Short answer: use multiple DNN modules and communicate between them via querystring parameters, postbacks or IModuleCommunicator. Depending on your requirements, the details view may be possible to implement using a Text/HTML module and client-side tools like jQuery and plugins only?
More details on using multiple interconnected DNN modules:
You can define multiple modules in the .dnn manifest section.
This way, each interconnected submodule is part of the same install package, but you'll only have one visible module in the in the control panel's "Modules" dropdownlist. Adding this composite module to a page will add all the submodules, but you can remove any one of them independently of the others.
You should be aware that each submodule that directly inherits PortalModuleBase will have its own Settings object. If you want to share settings, you'll have to inherit from a shared parent ascx that inherits PortalModuleBase or write a function to read settings from another module in the same page (having the same ModuleID helps here).
Communication between modules can be based on querystring parameters, which is recommendable for opening a details view so that you can open it even if the gallery module weren't present. PostBacks let you use UpdatePanel, though. Modules in the same page can also use IModuleCommunicator interface for event-based communication. For example, I use an event calendar module with a "month view datepicker" module and a "list view of events" module. List view module communicates active days to the monthview via IModuleCommunicator. This way I can emphasize the active days with a boldface font in the datepicker. For more details on IModuleCommunicator, see Rafe Kemmis's blog post.

Resources