ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #contao
Learn how to create a custom rotating banner in Contao using frontend modules and template overrides without modifying core files.
A guide to diagnosing and fixing the White Screen of Death (WSOD) in Contao CMS, covering cache corruption, PHP version mismatches, and permission errors.
After upgrading to Contao 6, input encoding is disabled and double encoding is enabled by default, which can cause unexpected output if templates are not adjusted. What specific steps should be taken to verify that output is properly encoded when using Twig templates or raw output from hooks, and how can the double‑encoding behavior be controlled during the
The goal is to understand whether Contao can return a distinct, user‑friendly message when a backend user’s LDAP credentials are marked as expired, rather than the generic "Invalid username or password" response it currently provides. Contao does not implement native password expiration for backend accounts and relies on external authentication sources to en
Goal: Determine how Contao should treat date values entered in back‑end forms when no explicit time‑zone offset is supplied, so that stored timestamps remain accurate for users in different regions. Constraint: Contao persists all date/time fields as UTC timestamps and relies on the PHP DateTimeZone conversion based on the configured default time zone (globa
Goal Ensure that dates rendered in a Contao CMS site appear in the correct regional time zone for each language, while keeping the core configuration stable. Constraints & Uncertainty Contao uses the PHP date.timezone setting for its default system offset. Dates are formatted in Twig via the date filter, which relies on PHP’s DateTime objects. There is n