Module periodically doesn't load into page

Overview

Certain modules on your page may be intermittently failing to load. On examination, you may find that:

  • The page source shows that the module code isn't being injected into the page.
  • The problem resolves on its own over time but will re-occur.
  • The problem can be temporarily resolved by clearing the server cache.
  • The module disappears for both authenticated and unauthenticated visitors.

Solution

Individual modules on a page normally inherit their cache settings from the Page Output Cache Provider (see Configuring Caching). If page output caching is disabled, the module has its own settings that it will use. This periodic problem usually shows up when page output caching is disabled and the module cache settings are misconfigured.

  1. Browse to the page and module experiencing the problem and click [Gear Icon] > Settings for that module.
    ModuleSettings.png
  2. Go to the Page Settings tab
  3. Click on Cache Settings to expand it
  4. Change the Output Cache Provider to Memory
    • If you proceed through the steps of this solution and the problem doesn't resolve, you can return to this screen and set the Cache Duration to zero if it isn't already. This disables the module's output cache.
      CacheSettings.png
  5. Click Update
  6. Clear Output Cache
  7. Clear Server Cache

Testing

Because the problem is intermittent, it may take time for it to resurface. Testing involves normal use of the site, with special attention to the module. In normal use, the module should consistently appear in the installed location.

Caching occurs at several levels, including module, page, provider, and server. If the steps in this article do not resolve the problem, you can read more about troubleshooting caching issues in the following articles:

If the problem persists despite correct caching settings, you can contact DNN Support for further troubleshooting. Be sure to include a summary of troubleshooting steps taken so far, the relevant logs from <site root>\Portals\_default\Logs, and when the issue was reproduced so we know what section of the logs to examine.

Comments

0 comments

Please sign in to leave a comment.