Have you found yourself needing to programatically clear DotNetNuke (DNN) cache but were dismayed to learn newer DNN versions no longer depend on an easily-cleared cookie? Here's a simple alternative to force the cache to clear

Clearing Cache
So you have a require to clear a DNN user's cache but you're employing a newer version of DNN that no longer retailers factors in an easily-cleared cookie. If this describes you then you're possibly:

• Bypassing DNN's "correct" mechanisms (built-in objects and the Data Access Layer) by directly calling SQL stored procedures.
• Querying straight through to data stored in SQL tables.

As an admin you have DNN's built-in alternatives for clearing cache and even "resetting the application domain". Your finish users, even so, lack these options and, actually, why would you desire customers to possess to accomplish something particular? You desire a solution that's hidden and automatic.

Cut to the chase:
Under is actually a link to a cost-free DNN7 module that does one factor: flush the cache. Drop the module on a web page, set the VIEW permissions for whatever group(s) you need the module to become active for and that's it.

The module itself has no configuration choices. The only genuine point to think about is who you would like the module to fire for. Users that are not logged in have no user-specific data to flush so you'll be able to rule out "Unverified Users" and, by extension, "All Users" (that is the mixture of "Registered Users" and "Unverified Users"). In most situations you will probably want to set the VIEW permission to "Registered Users".

Note that you simply do *not* want to use this module on pages with a lot of site visitors. Continuously flushing cache is definitely an outstanding way to cripple a busy web site. This module is greatest used on infrequently-visited pages (like a custom "user update" web page).

Additional Thoughts: Short and Sweet
The module necessary less than 10 minutes to create using DNN's constructed in "module creator" function (that indicates I designed it from within a DNN site utilizing absolutely nothing but the web browser) and less than 5 minutes to create the deployment package making use of DNN's constructed in "create package" feature but... those are topics for another day.

Best DotNetNuke Hosting Recommendation