Tagged Posts

I've had too many clients come to me and ask how they can search through all of their Text/HTML modules on a portal to look for links that point to their development URL rather than their production URL. Instead of telling them they had to manually look at every page to find all instances of these invalid links I created a new module, available from www.engagemodules.comEngage: F3 allows you to quickly and easily search through all Text/HTML modules installed on a site, generate a report of links found, and directly links to the edit control for each of those modules to allow you to correct the invalid links.Above and beyond the use case where you are searching for a URL, you can use Engage: F3 to search for any string within any Text/HTML module on your site.Future enhancements will include the ability to search through content of other modules, such as our Engage: Publish module, as well as the ability to search and replace all instances of a string without having to manually edit each entry.Best of all Engage: F3 is free! You can get it now from www.engagemodules.com, you can also download the C# Source Code for the module. Posted from...
DotNetNuke Tip #17, Disable Inline Editing in Text/HTMLWith the latest releases of DNN, 3.3.* and 4.3.*, you may notice that when logged in to a page you have edit rights to that you can "edit" content in the text/html modules simply by clicking on them in the browser window and typing. Convenient, yes? Sometimes! Othertimes it can really be a pain in the rear, I'm a click happy person, I click places so I can get my scroll started, so that last thing I want is to begin editing content on my pages.I figured I'd post a solution to disable this option in DNN. Currently this requires a recompile, though I know the core team is looking at how to make this an option for the Text/HTML module.So here's what you need to do.Download the Source Version of the Text/HTML project from DotNetNuke.comOpen the Project in VS 2003, I opened it in an existing DNN solution I had setup already.Open the HtmlModule.ascx.vb fileAround line 196 you'll find the following codelblContent.EditEnabled = Me.IsEditableComment that line out and add the following line'lblContent.EditEnabled = Me.IsEditablelblContent.EditEnabled = FalseRecompile the module in release mode and use the newly created DLL in your environments. Always Test new code/dlls on a test instance before moving them into production. The above code worked fine for me, but please test for yourself first.Stay tuned for more DotNetNuke tips, brought to you by Chris Hammond from Engage Software. Posted from...
RSS URL

Chris Hammond

Chris Hammond is a father, husband, leader, software developer, photographer and car guy. Chris focuses on the latest in technology including artificial intelligence (AI) and has spent decades becoming an expert in ASP.NET and DotNetNuke (DNN) development. You will find a variety of posts relating to those topics here on the website. For more information check out the about Chris Hammond page.

Find me on Twitter, GitHub and LinkedIn.