Today I got an email from Google because I use their Google Apps, and I was surprised, but kind of happy to read the email they sent.  Below is it's contents in entirety. 

NOTE: I have highlighted the interesting parts, or at least some.

Dear Google Apps admin,​

In order to continue to improve our products and deliver more sophisticated features and performance, we are harnessing some of the latest improvements in web browser technology.  This includes faster JavaScript processing and new standards like HTML5.  As a result, over the course of 2010, we will be phasing out support for Microsoft Internet Explorer 6.0 as well as other older browsers that are not supported by their own manufacturers.

We plan to begin phasing out support of these older browsers on the Google Docs suite and the Google Sites editor on March 1, 2010.  After that point, certain functionality within these applications may have higher latency and may not work correctly in these older browsers. Later in 2010, we will start to phase out support for these browsers for Google Mail and Google Calendar.

Google Apps will continue to support Internet Explorer 7.0 and above, Firefox 3.0 and above, Google Chrome 4.0 and above, and Safari 3.0 and above.

Starting next week, users on these older browsers will see a message in Google Docs and the Google Sites editor explaining this change and asking them to upgrade their browser.  We will also alert you again closer to March 1 to remind you of this change.

In 2009, the Google Apps team delivered more than 100 improvements to enhance your product experience.  We are aiming to beat that in 2010 and continue to deliver the best and most innovative collaboration products for businesses.

Thank you for your continued support!

Sincerely,

The Google Apps team

Email preferences: You have received this mandatory email service announcement to update you about important changes to your Google Apps product or account.

Google Inc.
1600 Amphitheatre Parkway
Mountain View, CA 94043

I hope someone else finds this interesting.  If not, no worries, but if you did and have comments, please feel free to post.

Okay I have a customer who has a .deb file that he wants to link to in his blog, which I have created for him in DotNetNuke.  DotNetNuke is an ASP.NET CMS. (content management system)

When he links to it, the user gets a 404 error, which is not what was wanted, so I needed to figure this out.

My assumption is that I need to add a MIME Type to IIS.  I found the following MIME Type, and it worked.

application/x-deb  

I first looked through several “Common MIME Type” web pages and couldn’t find the .deb extension.  Then I went to Wikipedia just because I wanted to find out more about the debian extension.  Once there I was happy to notice that it gave the “internet Media Type” (MIME Type) on the right hand side of the web page.

So make a note.  If you want to find an uncommon MIME Type, look for the extension on Wikipedia.

I have been designing a site for a customer that is going to rely on having a good looking and functional DNN Core Repository.

I found that creating a template for the repository was pretty simple after I found some online documentation on the DNN Repository.

I found that in the /wwwroot/DesktopModules/Repository/Templates/ directory I could add my own template which will show up under the Repository Skin drop down box.  As shown below.

As you notice the bottom one is the one I added.

Now the Issue

I was very excited to make my own repository template, but soon found I was getting pesky borders around the tables of the repository in the Safari and Opera browser. 

I tried editing the repository.aspx file, but was uncomfortable doing that because that is going beyond a simple template.

So then I did some experiments with the two browsers having the issues.  (Safari and Opera)  You can see my demo page and how I ended up fixing the issue.  (NOTE: for the demo page to make sense you need to view it in either Safari or Opera)

Basically to fix the issue I ended up using CSS to tell the tables inside the div I use for Content to have no borders.  Below is the CSS. (in the example below the DIV that the tables are in has the class bordernone)

.bordernone table,
.bordernone td,
.bordernone tr,
.bordernone tbody
{
    border: none !important
}

I hope that all makes sense.  Please feel free to email me if you have questions.  You can also make a comment here with a question, or heck, a better way to fix this issue.

Today I tried to install the Repository Module on a DotNetNuke website and was very frustrated to find I kept getting runtime ASP errors.

I was trying to install the Repository Module by going to Host > Module Definition and clicking on the “Install Module” link at the bottom of the page.  Then I was browsing to the zip file I had on my PC.

This was not working and I was beginning to think I was going to have to give up.

I started to look around my folder structure, thinking there might already be repository files somewhere that might be causing the error.  I came upon the install/module directory and inside there was a resource file for the Repository.

I was confused at first but then I found the page Host > Extensions and noticed at the bottom of the page there was an “Install Available Extensions” link and it went to a page that had all sorts of modules to install, to include the Repository.  YAY!

As you can see above there are a bunch of modules.  You won’t see Repository because I installed it already.

This is a very nice feature, but it is tucked away and not the easiest to find unless you already know about it.  So for those interested in installing any of the following modules, please go to the Host > Extensions page and make sure you are on or in Edit mode.

• Adsense
• Documents
• Feedback
• Help
• Map
• NewsFeeds
• Survey
• XML
• Announcements
• Events
• FormAndList
• IFrame
• MarketShare
• Reports
• UsersOnline
• Blog
• FAQs
• Forum
• Links
• Media
• Store
• Wiki

I hope this helps all you DNN people out there.  My only other question and I will have to repost on this as part two, or comment below.  Is this the only way to add Core modules for the first time? 

I am also hoping that when I go to update this module, or any Core modules, I won’t have any issues.  I don’t think I will, but I still can’t help but worry.