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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...error upgrading from 5.5.1 to 5.6.0error upgrading from 5.5.1 to 5.6.0
Previous
 
Next
New Post
11/19/2010 1:34 PM
 
No, there is only one alias.
 
New Post
11/19/2010 2:01 PM
 
Funny you should bring PNG files up William.

I did an upgrade on a site this morning and the upgrade appeared to go perfectly. However, when returning to the site after install, every PNG file was not rendering, on all pages. Regardless if it was CSS or inline. I did try different browsers and clearing both browser and web cache, but I didn't take the time this morning to trouble-shoot it, I just rolled it back to 5.5.1.

Any thoughts?


 
New Post
11/19/2010 3:08 PM
 
@Chris - The png behavior is very weird since serving those files shouldn't involve any DNN code at all since it is a file request that occurs between the browser and IIS.  The only thing that I could think of is that the file paths were somehow getting messed up...  DotNetNuke.com using png's all over the place and I haven't seen any issues so far with 5.6.0

Joe Brinkman
DNN Corp.
 
New Post
11/19/2010 3:26 PM
 
Agreed Joe! I even switched to the MinimalExtropy skin with the same results. I'll try running the upgrade again tonight/tomorrow, if the issue persists, I troubleshoot it more in depth. I do in some cases use the IsapiModule for some file handling (.jpg, .jpeg, .png, .gif, js, css) in IIS 7.5, but this instance does not.


 
New Post
11/19/2010 6:22 PM
 
I have not been able to reproduce the issue of skin png file paths being added as entries in the PortalAlias table following some upgrades to or new installs of DotNetNuke 5.06.00 and do not believe as one original poster indicated that it was related to whether or not the UsePortNumber node in the section of web.config was comment out or not.  Several posters have indicated that even after deleting all the png paths from the PortalAlias table and forcing an application restart they reappeared the next time the site was hit.

I did note that in both UrlRewrite HttpModule (DotNetNuke.HttpModules.UrlRewriteModule in UrlRewriteModule.vb) and also in the Global_BeginRequest method in App_Code/Global.asax.vb, request with images files ending with the .png extension are NOT excluded from further processing as are .jpg, gif, etc. A quick look at the code in the UrlRewriteModule On_BeginRequest method leads me to believe that that is where the automatic addition of new portal aliases takes place in DotNetNuke 5.06.00. and where .png file paths may be getting added incorrectly.

What triggers this incorrect behavior in some installs is not yet clear to me.

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...error upgrading from 5.5.1 to 5.6.0error upgrading from 5.5.1 to 5.6.0


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