June 2006 - Posts

DotNetNuke Daily Tip #7 6/30/06 Making Skin File Changes
Friday, June 30, 2006 4:07 PM

DotNetNuke Daily Tip for 6/30/2006

Ever need to make skin file changes and you don't want to go through the process of repackaging your ZIP file and uploading the file to your site? Here's a quick way to make skin file changes without having to go through the package and upload process.

If you develop your skins with the HTML files you can edit the HTML files on the server, they should be located in the /portals/##PORTALID##/skins/##SKINNAME##/ folder. You can directly edit the HTML files. Once you've made these changes go to the admin/skins menu and reparse your skin package.

If you develop your skins using the ASCX file method any changes you make to the ASCX files will be made immediately to the skins on your site so you don't have to reparse the skin package.

Stay tuned for another DotNetNuke Daily Tip coming next week!

Autocross FAQ
Thursday, June 29, 2006 9:59 AM
If you're interested in the sport of Autocross be sure to check out the Autocross FAQ provided by SCCAForums.com!
DotNetNuke Daily Tip #5 6/28/06 Cannot access a closed file
Wednesday, June 28, 2006 2:18 PM
Check out all of the DotNetNuke Daily Tips from Chris Hammond.

DotNetNuke Daily Tip for 6/28/2006

If you've ever received the following error while trying to upload a DotNetNuke module here's a quick fix.

ExceptionSystem.ObjectDisposedException: Cannot access a closed file. at System.IO.__Error.FileNotOpen() at System.IO.FileStream.Seek(Int64 offset, SeekOrigin origin) at System.Web.HttpRawUploadedContent.TempFile.GetBytes(Int32 offset, Int32 length, Byte[] buffer, Int32 bufferOffset) at System.Web.HttpRawUploadedContent.CopyBytes(Int32 offset, Byte[] buffer, Int32 bufferOffset, Int32 length) at System.Web.HttpInputStream.Read(Byte[] buffer, Int32 offset, Int32 count) at ICSharpCode.SharpZipLib.Zip.ZipInputStream.FillBuf(Int32 size) at ICSharpCode.SharpZipLib.Zip.ZipInputStream.GetNextEntry() at DotNetNuke.Modules.Admin.ResourceInstaller.PaInstaller.ReadZipStream() at DotNetNuke.Modules.Admin.ResourceInstaller.PaInstaller.Install()

What version of DNN are you running? Is it 3.*? What version of the .Net framework is your site running on? If it's 2.0 that's most likely your case. We ran into this problem earlier today in our testing environment. To fix it, in IIS on the ASP.NET tab for your site be sure to set it to 1.1!

Thanks to Jianxiong for sending me the error message.

Stay tuned for another DotNetNuke Daily Tip coming tomorrow!

DotNetNuke Daily Tip #4 6/27/06 Inline Content Editing
Tuesday, June 27, 2006 11:45 PM

 Check out all of the DotNetNuke Daily Tips from Chris Hammond.

DotNetNuke Daily Tip for 6/27/2006

This is a quick tip as I was out of town for a while and haven't had a chance to catch back up yet.

Did you know with DotNetNuke 4.3 you can now edit content in place on your website? What's that you say? You didn't know this?

Well that's right, you can change module titles within your DotNetNuke pages, and have been able to do that for a few versions with DNN4. BUT, something new to DotNetNuke 4.3, the Text/HTML module includes this functionality as well. You can edit text within the Text/HTML modules without having to go to the edit screen, and also save these changes by clicking elsewhere on the site.

Stay tuned for another DotNetNuke Daily Tip coming tomorrow!

DotNetNuke Daily Tip #3 6/26/06 Clear Search Tables
Monday, June 26, 2006 10:47 AM

Check out all of the DotNetNuke Daily Tips from Chris Hammond.

DotNetNuke Daily Tip for 6/26/2006

During your development you may run across a time when you need to clear out the search tables for DotNetNuke's searching engine. Here's the SQL to do so.

delete SearchItemWordPosition where SearchItemWordId in (select SearchItemWordId from SearchItemWord where SearchItemID in (select SearchItemId from SearchItem)) 
delete SearchWord where SearchWordsId in (select SearchWordsId from SearchItemWord where SearchItemID in (select SearchItemId from SearchItem)) 
delete SearchItemWord where SearchItemId in (select SearchItemId from SearchItem) delete SearchItem 

Thanks to Mark Gorla from Engage Software for providing this tip.

Do you have a question about DotNetNuke? Perhaps I can answer it here as a Daily DotNetNuke Tip! Email chris.hammond at dotnetnuke.com  with your question! Be sure to put Daily Tips in the subject line.

 

UPDATE:

here's objectQualifier included code

delete {objectQualifier}SearchItemWordPosition where SearchItemWordId in (select SearchItemWordId from {objectQualifier}SearchItemWord where SearchItemID in (select SearchItemId from {objectQualifier}SearchItem)) 
delete {objectQualifier}SearchWord where SearchWordsId in (select SearchWordsId from {objectQualifier}SearchItemWord where SearchItemID in (select SearchItemId from {objectQualifier}SearchItem)) 
delete {objectQualifier}SearchItemWord where SearchItemId in (select SearchItemId from {objectQualifier}SearchItem) delete {objectQualifier}SearchItem 

DotNetNuke Daily Tip #2 Mail.SendMail
Friday, June 23, 2006 10:32 AM

Check out all of the DotNetNuke Daily Tips from Chris Hammond.

DotNetNuke Daily Tip for 6/23/2006

Have you ever needed to send mail from one of your DotNetNuke modules? Here's the DotNetNuke method for sending off a message.

public static System.String SendMail ( System.String MailFrom , System.String MailTo , System.String Cc , System.String Bcc , DotNetNuke.Services.Mail.MailPriority Priority , System.String Subject , DotNetNuke.Services.Mail.MailFormat BodyFormat , System.Text.Encoding BodyEncoding , System.String Body , System.String Attachment , System.String SMTPServer , System.String SMTPAuthentication , System.String SMTPUsername , System.String SMTPPassword )

But what does that really mean? Here's a simple call to the mail function from a module.

Mail.SendMail("FROM@ADDRESS.COM", "TO@ADDRESS.COM", "", "THIS IS THE SUBJECT", "THIS IS THE MESSAGE BODY", "", "HTML", "", "", "", "" );

Could it get any simpler than that?

Actually it could! Here's another signature for sendmail

public static System.String SendMail ( System.String MailFrom , System.String MailTo , System.String Bcc , System.String Subject , System.String Body , System.String Attachment , System.String BodyType , System.String SMTPServer , System.String SMTPAuthentication , System.String SMTPUsername , System.String SMTPPassword )

 

Do you have a question about DotNetNuke? Perhaps I can answer it here as a Daily DotNetNuke Tip! Email chris.hammond at dotnetnuke.com  with your question! Be sure to put Daily Tips in the subject line.

DotNetNuke Daily Tip #1
Thursday, June 22, 2006 10:19 AM

Here's the beginning of what will become the daily DNN tip. Check back here for more daily tips, each day of course (5 days a week)!

DotNetNuke Daily Tip for 6/22/2006

Verticle menu using the SolPartMenu skinobject. In order to get a verticle menu using the SolPartMenu skin object, when creating your XML attribute file for your skin, be sure to include the following.

<Token>[SOLPARTMENU]</Token>
<Settings>
 <Setting>
  <Name>display</Name>
  <Value>vertical</Value>
 </Setting>
</Settings>

the default value for Solpart is Horizontal.

This DotNetNuke tip is brought to you by the letter P!

DotNetNuke 4.3.1 Released!
Wednesday, June 21, 2006 10:48 AM

Last week 4.3 was released. This week 4.3.1 was released.

What's 4.3.1? It's a minor point release to fix some of the issues that made their way into 4.3. How's that for some quick turn around for a release cycle? I know some other .Net "open source" packages don't get releases that quickly! ;)

Download the latest version from www.dotnetnuke.com

 

by Chris Hammond | with no comments
Filed under: , ,
Quick and dirty menu in CS
Thursday, June 15, 2006 11:52 PM

I saw this post from J-O this evening. Content parts are pretty useful within CS as J-O states. Here's another great use for them. On SCCAForums.com I needed an easy way to put some common navigation on a majority of the pages. I ended up creating a common contentpart on the SCCAForums.com pages that allows me to easily manage this navigation from within the browser.

DotNetNuke 3.3 and 4.3 Release Candidates Released!
Tuesday, June 13, 2006 8:10 PM

Check out the press release here. http://www.dotnetnuke.com/Default.aspx?tabid=958

Time for some upgrades! Here's some of the new features!

"The following is a handful of the new features and improvements in DotNetNuke® 3.3/4.3:

Membership, Roles, Profile Providers – Based on a variety of serious limitations in the default Microsoft ASP.NET 2.0 Providers, DotNetNuke® has been enhanced with an evolutionary set of equivalent abstract APIs and concrete implementations which provide greater extensibility, a richer feature set, and simpler administration.

Extensible Profile Management – Consolidating a wide range of community enhancement requests, the Profile service has been completely overhauled. Run-time extensibility enables site administrators to create and manage profile properties through a highly intuitive user interface. Profile properties are fortified with a broad range of attributes to help facilitate advanced business processes. Profile information is stored in a database format which allows for simple accessibility, searching, and extraction. Developers have the ability to create custom property editor controls as well as profile items which are specific to their modules.

Secure Folders – Building on the existing document management capabilities, a number of new storage options have been introduced at the folder level. Administrators can now create secure folders which can be locked down by role to prevent unauthorized access. In addition, folders can be designated for database storage if you wish to utilize the database rather than the file system for storage of specific documents.

Usability – Minor improvements to the content management capabilities have the potential for major productivity gains. Enhancements include AJAX-style “in-line” content editing, custom page templates, an improved interface for copying existing pages, and the ability to use the URL selection control from within the rich text editor.

Performance – Module settings are now cached to significantly reduce the number of database hits, caching logic was optimized throughout the application to eliminate threading issues, and a variety of modules were enhanced with improved module output caching techniques.

Activity on the DotNetNuke® Projects has been strong in recent months and as a result, the out-of-the-box capabilities of the DotNetNuke® application have been significantly improved in this release. New versions of almost every DNN® Module have been packaged with the core framework including  substantial revisions to DNN® Documents, DNN® Events, DNN® Feedback, DNN® Forums, DNN® IFrame, DNN® Repository, DNN® Store, DNN® Survey, and DNN® User Defined Table. Modules provide the functionality for advanced web site features; allowing you to directly engage your customers, collaborate on ideas, and allow interaction among visitors.

Pricing and Availability

DotNetNuke® is available for free download. The complete application source code is distributed under an enterprise-friendly open source license ( BSD ); providing the maximum freedom in both non-commercial and commercial environments. More information about DotNetNuke® can be found by visiting http://www.dotnetnuke.com.

"

by Chris Hammond | with no comments
Filed under: , ,
More Posts Next page »

This Blog

Syndication