Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesUnable to Add Custom Module to a Public PageUnable to Add Custom Module to a Public Page
Previous
 
Next
New Post
7/14/2018 7:45 PM
 
I can't speak for Chris Hammond, but AFAIK he is still supporting his templates. Did you try contacting him directly on his GitHub project?

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/14/2018 8:17 PM
 
I think the template Sebastian mentioned cannot be relevant to your problem.

Modules built using Chris Hammond's templates continue to work just fine. Whatever you problem is it will not be fixed by changing the underlying Chris Hammond template.

I think you need a normal debugging process. Does it work with other modules? Standard DNN modules? Third party ones? Are you using a standard skin? If not does it work with the standard default skin? If the site you are testing with is purely for testing then try things with a fresh copy of DNN.

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
7/22/2018 2:26 PM
 

Hi Richard,

Other modules, such as HTML, load without issue.  I'm using the plain vanilla DNN 9.2 installation and the generic skin.  This morning, I uninstalled the extension and reinstalled a fresh build.  The error in Admin logs shows:

AbsoluteURL:/API/PersonaBar/Extensions/GetInstalledPackages

DefaultDataProvider:DotNetNuke.Data.SqlDataProvider, DotNetNuke

ExceptionGUID:2305a549-359a-4a52-b024-698ed728d6d6

AssemblyVersion:

PortalId:-1

UserId:-1

TabId:-1

RawUrl:

Referrer:

UserAgent:

ExceptionHash:e9ob+zbiS7o2Agr24mZj889tR8c=

Message:Value cannot be null. Parameter name: type

StackTrace:

at System.Activator.CreateInstance(Type type, Boolean nonPublic) at System.Activator.CreateInstance(Type type) at DotNetNuke.Entities.Modules.EventMessageProcessor.UpgradeModule(EventMessage message)

 

InnerMessage:

InnerStackTrace:


 

Source:mscorlib

FileName:

FileLineNumber:0

FileColumnNumber:0

Method:

 

The SQL Server EventLog has an entry as follows:


<LogProperties>

  <LogProperty>

    <PropertyName>AbsoluteURL</PropertyName>

    <PropertyValue>/API/PersonaBar/Extensions/GetInstalledPackages</PropertyValue>

  </LogProperty>

  <LogProperty>

    <PropertyName>DefaultDataProvider</PropertyName>

    <PropertyValue>DotNetNuke.Data.SqlDataProvider, DotNetNuke</PropertyValue>

  </LogProperty>

  <LogProperty>

    <PropertyName>ExceptionGUID</PropertyName>

    <PropertyValue>2305a549-359a-4a52-b024-698ed728d6d6</PropertyValue>

  </LogProperty>

</LogProperties>


My next step would be a fresh install of DNN but wanted to find out if there are any issues I can easily remedy without having to do so?  Thanks so much for your help and guidance.

 
New Post
7/26/2018 4:54 PM
 

So, I've installed a fresh copy of DNN and am still receiving this error when I attempt to add my custom module to a new page.  What is the suggested approach to determine the root cause?

 
New Post
8/11/2018 8:51 PM
 
Sid Childers wrote:

So, I've installed a fresh copy of DNN and am still receiving this error when I attempt to add my custom module to a new page.  What is the suggested approach to determine the root cause?

This is still an issue for me.  I think it's because I was implementing IUpgradeable in my FeatureController class.  I've tried commenting out this implementation and removed Upgradeable as a supported feature.  However, when I try to comment out the following lines from my manifest, the module won't even install:

<eventMessage>

            <processorType>DotNetNuke.Entities.Modules.EventMessageProcessor, DotNetNuke</processorType>

            <processorCommand>UpgradeModule</processorCommand>

            <attributes>

              <businessControllerClass>CrossClassifiedCrossClassified.Components.FeatureController</businessControllerClass>

              <desktopModuleID>[DESKTOPMODULEID]</desktopModuleID>

              <upgradeVersionsList>00.00.01,00.00.02</upgradeVersionsList>

            </attributes>

          </eventMessage>

So, if I comment this section out of the manifest, the module won't install.  If I leave it in the manifest, the module installs but does not allow me to place it on a page within my site.  Can anyone weigh in on a suggested remedy?  Much appreciated!!
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesUnable to Add Custom Module to a Public PageUnable to Add Custom Module to a Public Page


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out