Cache & back-office display
If the module interface displays incorrectly in your back-office, the cause is almost always related to a caching layer.
CDN / Cloudflare cache
A CDN such as Cloudflare may cache the interface assets and break its display. The solution is to exclude from the cache the interface directory (/modules/kixelltag/views/backoffice/), then purge the cache. The detailed procedure is described in Cloudflare.
PrestaShop cache
After a module update, clear the PrestaShop cache (Advanced Parameters → Performance → Clear cache) to reload the most recent assets and templates.
Memcache / object cache
With an object cache (Memcached, APCu, Redis…), a corrupted or expired entry can cause a deserialization error when reading the settings. If you encounter this:
- Clear the object cache to force a clean regeneration.
- If needed, use Force update from the module's Settings menu to cleanly reinitialize the module's data.
After any purge operation, reload the module interface to check that the display is back to normal.