Is it possible to set the module category in a DNN manifest file so a package containing lots of related modules can be categorised? It doesn't have to add the the taxonomy, an existing entry is fine.
The DNN Wiki seems to suggest not?
This is not possible currently with DNN. You can only set the Category by editing the module via the extensions page AFTER installing a module.
Related
I am trying to start a Drupal 7 website. I was provided with a folder containing a Drupal installation, and was to move it to a server with a database supposedly for that installation.
Upon me doing so, Drupal gave me several errors regarding missing modules. After manually installing most of the missing modules, I am left with a single error, which is
User warning: The following module is missing from the file system: post_articles. For information about how to fix this, see the documentation page.
I am unable to find the post_articles module on the Drupal website or anywhere else, and am at loss how to proceed.
It's not a contrib module so you cannot get it from drupal forge, otherwise to unlock your situation you can disable module by query into your database :
UPDATE system SET status=0 WHERE name='post_articles';
But it can be a dependency of another module so be careful when you're disabling module with this way.
I have already published dnn website. So Can I add my custom module in it?
I have purchased DNNGoxNews the module with source code from dnn store.
Now I want to modify some of the fields from some user control So How Can I achieve this.
I have already installed the module in my dnn website.But How can I modify the module.
Please point me the right direction.
Thank You
You will want to install this module in a development environment, which typically means a local copy of DNN
Follow this tutorial for how to setup your development environment.
Once that environment is setup, go to the HOST/EXTENSIONS page
Install the SOURCE package of the module you purchased
Open up the Project file, or Solution, in Visual Studio 2015
Make your changes, compile the module/changes
Repackage the module for deployment, if the source code doesn't do it for you automatically you can follow this tutorial.
I was reading a DNN manual called 'DotNetNuke Module Developers Guide' for developing new modules from scratch.
The manual says to create a class library project and add reference to DotNetNuke project.
I do not find any such project in Community version source code for version 7.00.04. However, I can see DotNetNuke.Web and DotNetNuke.Web.WebClient projects but none that is called DotNetNuke.
There isn't a DNN project, but there is a DotNetNuke.dll, add a reference to that (the project I believe is DotNetNuke.Library)
I would also suggest taking a look at my Templates for DNN, they make doing module development easy http://christoctemplate.codeplex.com/
Hi DotNetNuke experts :)
I want to make some changes in dnnfeedback source and I want to add module definition to site
in previous release of this module I used to go to "host-->extensions" and from action menu choose "create new module" and simply add the manifest and use it
But in latest module release the manifest extension was changed to .dnn6 and my DotNetNuke (version:6.1.3) doesn't show me anything to choose from.
I think this section of DotNetNuke Doesn't understand .dnn6 extension.
so how can I add definition of this module?
Thanks
if you wanna to change a source code just install the package and replace the DLL file with that one you've changed
You can simply use "Install Extension Wizard" instead of "Create new module" option and select the downloaded source package .zip of the Feedback module. It will install source files into DestkopModules/Feedback folder and you can make your changes there.
A little about .dnn6 manifest files can be found here.
I'm developing a DotNetNuke Module using the nonIIS method of module development. Is there any way to include a 3rd-party assembly in your module (when setting it up for deployment)?
I thought about adding it as a reference to the dotnetnuke_nonIIS website project as a whole, but that doesn't seem right considering it's a dependency of the module.
Whatever your local development environment may look like, you will most likely want to be able to deploy the module to a DNN site on its own.
To do that, you can create an installable module zip package - which consists of all of your module assets and a manifest file describing them so that DNN may process them and perform the appropriate actions (run scripts, deploy assemblies to the bin) upon installation.
Check out the DNN wiki for more information about packaging.