DNNArticle Module and Multi instance in Dotnetnuke - dotnetnuke

one of best module for dnn in news and article is DNNArticle . each module instance that putted in the page has its own category and tags. when using dnnarticle category list module in its options we have to select only one instance . is it possible to show all category from all instance of DNNArticle.

Related

Allow users to add modules to a page using react components

I am trying to build a tool that would essentially work as a "web page builder" where a user can click to add a module, select from a list of options and then have those modules injected/added/appended to the page in a specific order.
Paperbits(https://demo.paperbits.io/) is the best example of what I am trying to accomplish. when the user selects a module it is added where the selected the plus button and can be edited from there.
I am using react.
You can assign an ID to each module. When you select a module(component), you can push that ID to an array. You can then use that array to map and render the module based on the ID.

Joomla custom component query string to SEF URL building

I want am developing a component for joomla 3+.
I am using database to get the categories in the menu and manually creating the link like mentioned below.
// Creating the manual link
$linkThingsToDo = JRoute::_('index.php?option=com_mycom&view=city&layout=thingstodo&cid[]='.$cityID.'&cat_id[]='.$value->catid);
Here I am using the "cid[]" for City ID and cat_id[] for Category ID and I am getting the link in address bar like this:
joomla/index.php/city-guide-3/city/thingstodo?cid[0]=2&cat_id[0]=4
While I want "joomla/index.php/city-guide-3/city_name_here/category_name_here"
"joomla/index.php/city-guide-3/Dubai/Chocolate"
using localhost for the testing.
What should I do to achieve the above SEF URL

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.

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

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.

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