Skip to main content

Error: Module cannot be displayed or rendered

This article covers two related error messages you may see in place of a configured module on the front-end of your site:

  • "The module cannot be displayed"
  • "Module cannot be rendered as the requested content is no longer accessible"

Both errors point to the same underlying situation: the plugin can no longer reach the cloud folder the module is configured for.

Causes and solutions

  1. Cause: The cloud account is no longer linked or authorized
    The cloud account the module points to has been disconnected, or its authorization has expired.

    Solution: Open the plugin's settings page and re-link the cloud account. See also The plugin keeps losing connection with my cloud accounts.
     

  2. Cause: The target folder has been moved, renamed, or deleted
    The module is configured to display a specific folder, but that folder no longer exists at the original location.

    Solution: Add a new module on the page with the correct folder selected. If the new module loads, you can compare the raw shortcode of the old and new module to spot the difference, then fix the original.
     

  3. Cause: The plugin cannot reach the site's AJAX endpoint
    If the plugin can't connect to /wp-admin/admin-ajax.php, it can't load module content. A security plugin, firewall, or server configuration may be blocking access.

    Solution: Verify that /wp-admin/admin-ajax.php is reachable. See also Error: No content received, which covers AJAX-related issues in more detail.
     

  4. Cause: License issue
    When the plugin's license has a problem, front-end modules stop rendering as a safeguard.

    Solution: Open the plugin's settings page and check the license status. If needed, deactivate and reactivate the license from the plugin's license screen.