Will "the Mighty" Strohl

Content Injection Module 01.02.00 for DotNetNuke Released

Content Injection Module for DotNetNuke

Today, I finally dedicated some time to give the Content Injection Module for DotNetNuke some much needed love.  Fortunately, there aren’t too many reported issues or requested features, so the update went quickly and smoothly.

If you are new to the Content Injection Module, this module was built to allow you to inject literally any text, content, scripts, or anything at all into the header or footer of your DNN website.  It can be quite useful to inject things like Open Graph Protocol, JavaScript libraries, CSS, startup scripts, and more. 

There are a total of four (4) updates made to the module for this release.  They are listed below:

  • Feature:  Windows Azure Support
  • Feature:  DotNetNuke Icon API Support
  • Enhancement:  Increase Width of Content Injection Text Field
  • Bug:  Content Injection Truncated

Windows Azure support will only affect a small subset of those using this module.  Up until now, you would not be able to successfully install the Content Injection Module on instances of DotNetNuke running on Azure.  Now you can successfully install and use this module on Azure.

The Icon API support is really only a cosmetic change, and most people won’t notice that this has even changed.  However, if your instance of DNN is more advanced and chooses to use its own icon set, this module will work seamlessly with your instance.

The content injection field in edit view was quite small for some content administrators.  It was too small for larger content injections – especially if they were over 100 characters or so.  Now, you have a much larger view for this module.  This enhancement was done completely client-side too, so you can change the height and width of this field on your own site as you see fit.  Just override the following two CSS selectors in your portal.css.  Your portal.css can be updated in your Admin > Site Settings page.

The final update was an unfortunate bug.  A while back I had increase the number of characters for a content inject to be unlimited.  However, the data access layer (DAL) that did the actual save to the database was still observing the original 2,000 character limit.  This would result in your content injection being trimmed to the first 2,000 characters.  This bug has been fixed.  You can now save content injections of any size safely.

blog comments powered by Disqus