• Cache

  • The following questions concern functions exclusively available for clients having chosen to host their website with Nexus.

    If the cache of a certain url has expired, it will mean the next time a user requests that same url, the theme will rebuild the cache first, before serving the page (so it will re-render it, and store the re-rendered result in the cache, such that the next time it will serve that new updated version, assuming it won't have expired then, else it will repeat the same process). If you change the cache setting to another value, that itself will not invalidate existing cached items. If you want to clear the cache, use the clear cache button to wipe it.

    The biggest downside is that the information send to the user _could_ be "old". Imagine you have a blog widgets on a page that shows the latest news items. If that page is cached, and afterwards you insert new news items, the cached page will not be updated (it will only update if the cache has expires. Another downside is that the system will store the cached output on the file system, although nowadays diskspace is not likely to be a limitation.

    Please watch the video by clicking the icon on the right.

    Please watch the video by clicking the icon on the right.

    Please watch the video by clicking the icon on the right.

    In our framework there's a series of conditions that should be met before the cache is actually stored on disk. One of those conditions is that a session should NOT have been active. This condition makes sense, as you would only want to cache output belonging to anonymous users (otherwise private information from other users would potentially be cached).

    ​ If you open the following URL when you are NOT logged in to the system;​ http://{replacethiswithyourdomain}?nxs=debugcache​. ​You will see the reason why the cache is not stored.

    ​ ​NOTE: if you access that URL if you _are_ logged in, you will just see the regular content (as then the debug lines is not executed).

    ​ If the system says the "session was started", likely one or more plugins are active that start the session. You could try to disable the plugins, and re-check the URL to see if that solves the problem.