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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DotNetNuke Version 4.9.0DotNetNuke Version 4.9.0
Previous
 
Next
New Post
7/3/2009 4:40 AM
 

Hello everyone,

We developed a website using dotnetnuke version 4.9.0, we did some changes to the code (not the first time we did this in a dotnet nuke project).
We discovered that this version 4.9.0 has a BIG CACHE PROBLEM.

How to solve it without upgrading to a newer version?, we can't upgrade, we already modified the dotnetnuke code and we can't do everything again in the newer version.
Please advise.

 

 
New Post
7/3/2009 6:00 AM
 

If you can't upgrade to DNN 4.9.4 you'll have to download the source package and compare the change to DNN 4.9.0 and do a custom build...


Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

 
New Post
7/3/2009 6:04 AM
 

I would use a diff utility like Beyond Compare and compare the 4.9.0 source with what you have now. Then Document it!!! maybe even add comments you can easily search for your changes by. Then consider merging your changes into a newer version like 4.9.4.

Please be aware that this is not a recommended practice for reasons you describe! Sounds like your finding that out the hard way. May I ask what your changing that can't be done through other extension points?

 
New Post
7/3/2009 6:26 AM
 
Hello Fady,
 
Please try these steps if it will works for you.
 
Add the following piece of code in the code behind page, I mean aspx.cs page
In the page_load add

Response.Cache.SetNoServerCaching();
                Response.Cache.SetCacheability(System.Web.HttpCacheability.NoCache);
                Response.Cache.SetNoStore();
                Response.Cache.SetExpires(new DateTime(1900, 01, 01, 00, 00, 00, 00));

This is one way.Else try below one
 
In the aspx page you can add
with in the <head> tag add
 <meta name="prevent_caching1" http-equiv="Pragma" content="no-cache" />
    <meta name="prevent_caching2" http-equiv="Cache-Control" content="no-cache" />
    <meta name="prevent_caching3" http-equiv="Expires" content="0" />
 
Thanks,
 
Debendra Nandi
Mindfire Solutions
 
New Post
7/3/2009 7:14 AM
 

I think Fady is talking about a totally seperate cache issue. Maybe DNN-9038?

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DotNetNuke Version 4.9.0DotNetNuke Version 4.9.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