You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently check for availability of the backend, e.g. if if a compatible PHP extension is available for external object caches or permalink structure is active for HDD caching. If this is not the case, we silently fall back to Database Caching which is always available.
We should at least add an admin notification to attract attention, because the plugin configuration does not fit the server environment which leads to potentially unintended behavior.
The text was updated successfully, but these errors were encountered:
We should not silently ignore misconfiguration and fall back to
DB caching. We now check for availability and disable caching
via a "no operation" backend. We can also add a notice for APC
now which is no longer supported.
We should not silently ignore misconfiguration and fall back to
DB caching. We now check for availability and disable caching
via a "no operation" backend. We can also add a notice for APC
now which is no longer supported.
We should not silently ignore misconfiguration and fall back to
DB caching. We now check for availability and disable caching
via a "no operation" backend. We can also add a notice for APC
now which is no longer supported.
We should not silently ignore misconfiguration and fall back to
DB caching. We now check for availability and disable caching
via a "no operation" backend. We can also add a notice for APC
now which is no longer supported.
We currently check for availability of the backend, e.g. if if a compatible PHP extension is available for external object caches or permalink structure is active for HDD caching. If this is not the case, we silently fall back to Database Caching which is always available.
We should at least add an admin notification to attract attention, because the plugin configuration does not fit the server environment which leads to potentially unintended behavior.
The text was updated successfully, but these errors were encountered: