whoami
Lucas Jenß
cat /etc/motd
The Coding Journal ツ — Notes taken on an epic coding journey. Technical solutions, debugging notes, and practical guides from the trenches of software development.
ls -la ~/languages/
- drwxr-xr-x
- ▶ PHP
- ▶ Ruby
- ▶ Scala
- ▶ C#
- ▶ JavaScript
- ▶ Objective-C
- ▶ Shell Scripting
ls -la ~/toolchain/
- drwxr-xr-x
- ▶ Typo3
- ▶ Akka
- ▶ Capistrano
- ▶ Git
- ▶ MAMP
- ▶ Adobe Illustrator
- ▶ NSTrackingArea (Cocoa)
uname -a
- drwxr-xr-x
- ▶ Mac OS X
- ▶ Unix
Customising the TYPO3 Login Page With a Fluid Template Override
The TYPO3 backend login screen is often the first part of an installation that editors see, yet it is easy to leave it looking like an untouched core interface. A carefully tailored login page can add a client logo, explain the purpose of the system, provide support details and make a multi-site installation feel like a finished product.
A Fluid template override is useful when configuration options alone are too limited. It gives you control over markup, labels, layout areas and additional visual elements while keeping the change inside a custom extension rather than editing files in vendor/typo3. That distinction matters because core changes disappear during updates.
The exact override mechanism depends on the TYPO3 version and the backend package in use. TYPO3 has progressively moved towards events, service configuration and dedicated backend APIs, so the safest implementation begins by checking the template and controller shipped with the installed release. The general workflow, however, remains consistent: inspect the core view, register a higher-priority template path, add your Fluid file, then test the result after clearing caches.
Find The Template Used By Your TYPO3 Version
Start by locating the login templates in the installed backend system extension. With a Composer installation, inspect the relevant files under vendor/typo3/cms-backend/Resources/Private/. A non-Composer installation usually keeps the same resources below typo3/sysext/backend/Resources/Private/. Search for files containing names such as Login, Index or Form, and then check the associated controller or view factory.
Do not assume that a template path from TYPO3 8 or TYPO3 9 still applies to TYPO3 11, 12 or 13. Namespaces, template directories and registration APIs can change between major releases. The controller may render a complete page, a form partial, or a layout that includes several partials. Knowing which file owns the markup prevents a common mistake: overriding a partial while expecting to replace the whole page.
Create a custom extension for the change, even if the project is small. A site package or an extension such as acme_backendbranding is a suitable home. This keeps the override in version control and makes it possible to apply the same branding to staging and production environments without manually copying files between servers.
Register A Higher-Priority Fluid View Path
TYPO3 Fluid rendering uses ordered template, layout and partial paths. Your custom path must be placed before the core path, otherwise TYPO3 will continue to load the original file. The registration method varies by release, so use the backend extension documentation for the installed version and follow its supported configuration pattern rather than relying on an old blog snippet.
Conceptually, the configuration points the backend login view towards a directory like:
EXT:acme_backendbranding/Resources/Private/Backend/Templates/
EXT:acme_backendbranding/Resources/Private/Backend/Layouts/
EXT:acme_backendbranding/Resources/Private/Backend/Partials/
Your copied file should retain the path and filename expected by the controller. Copy the original template into the matching directory and change only the markup you need. This allows the existing Fluid variables, form action, hidden fields, CSRF token and error handling to remain available. Rebuilding the form from scratch is risky because authentication depends on details that are easy to omit.
If your TYPO3 release does not expose a public template path configuration for the login controller, check for a supported event or view-factory hook before using an XCLASS. An XCLASS can work as a last resort, but it couples the extension to internal core classes and may require maintenance after every update. The official extension API is a better long-term option for an Australian agency managing several client installations.
Preserve Authentication And Accessibility
The visual layer can be changed freely, but the authentication flow must remain intact. Keep the original form fields, names, action URL and security-related hidden inputs. Preserve the existing error messages and the conditional rendering used for locked accounts, invalid credentials or required password changes. A login page that looks polished but silently removes an important field is a production defect.
Use semantic HTML and make the form usable without a mouse. Associate every label with its input, keep a visible focus state, and ensure that the submit button has a clear purpose. A client team working from a laptop in Brisbane, Adelaide or regional New South Wales should not need to depend on a particular browser or touch device. Keyboard navigation is also valuable for support staff who process many content updates each day.
Follow WCAG principles for colour contrast and readable text. Avoid placing white text over a background image merely because it matches the brand guide. If the login screen uses a photograph or illustration, provide a solid fallback colour and test the page at different zoom levels. An SVG logo can be a practical choice when it remains accessible and does not include unnecessary editor data; these SVG export options are useful when preparing a clean asset for the template.
Add Branding Without Creating A Maintenance Trap
A Fluid override is a good place for a logo, a short welcome message, a support contact and a link to a privacy statement. It is less suitable for storing an entire marketing page. Keep the login experience focused: editors should understand where they are, how to sign in and where to get help if access fails.
Use TYPO3 configuration for values that may differ between installations. For example, a site-specific logo path, support email address or environment label should not be hard-coded into a shared template. TypoScript, extension configuration or a custom backend view variable can supply those values, depending on the API available in your TYPO3 version. This is especially helpful when the same code serves a Melbourne retail client and a Perth not-for-profit organisation.
The built-in backend configuration may already cover simple branding requirements such as the login logo, background image, highlight colour and footer text. Use those settings first. A Fluid override should handle structural changes that configuration cannot provide, such as a custom two-column arrangement, a help panel or a clearly displayed staging warning.
Be careful with external assets. Loading fonts, tracking scripts or images from third-party services can create privacy, performance and availability issues. Australian organisations may also need to consider the Privacy Act and their own client security policies. Self-host the assets where practical, and do not add analytics to an authentication screen unless there is a strong, documented reason.
Test The Override Across Real Login States
Clear TYPO3 caches after registering the new path. Depending on the release and deployment method, this may involve the Install Tool, the CLI cache flush command or the backend maintenance tools. Browser caching can also hide changes, so use a private window or clear the relevant cached resources before deciding that the override has failed.
Test more than the successful login state. Check invalid credentials, an expired password, a disabled user, a missing logo, a long username, a narrow mobile viewport and a browser with JavaScript disabled. Verify that translated labels still fit, especially if the installation serves German, Mandarin or other languages alongside English. A heading that looks balanced in a Sydney design review can wrap awkwardly on a smaller screen.
Review the result after each TYPO3 update. A core template may add a new security field, change a Fluid variable or remove a partial that your copy still references. Compare your override with the new core template before deploying. Automated smoke tests can request the login route and check for the form, expected labels and a successful response without attempting to authenticate a real user.
Keep deployment records clear enough for another developer to follow. A short README should identify the TYPO3 version, the registration method, the overridden files and the reason for each custom change. If you work with an external developer, a portfolio such as Oscar David Sanchez can also illustrate how a restrained interface and consistent visual language support a professional digital product.
Practical Checks For A Safer Custom Login
- Copy core templates into a custom extension instead of editing
vendor/typo3ortypo3/sysext. - Confirm the override mechanism against the exact TYPO3 major and minor version in use.
- Preserve the original form action, field names, hidden security fields and error handling.
- Use configuration for logos, colours, support details and environment-specific text where possible.
- Test keyboard access, contrast, responsive layouts, translations and long validation messages.
- Keep third-party scripts off the login page unless privacy and security requirements have been reviewed.
- Compare the custom template with the core version after every TYPO3 security or feature update.
A well-implemented Fluid override should feel like a small, controlled extension of TYPO3 rather than a replacement for its authentication system. Begin by copying the version-matched template, register the custom path through a supported API, make the smallest useful markup changes and test every login state before release. Then commit the extension and its documentation so future updates remain predictable.
cat ~/interests.json
| Key | Value |
|---|---|
| editor | Terminal-first workflow |
| os | Mac OS X / Unix |
| vcs | Git, distributed version control |
| deploy | Capistrano, cron automation |
| graphics | SVG, Adobe Illustrator troubleshooting |
| networking | IP validation, SSH, VPN |
git log --oneline --reverse
Solving SVG import issues in Adobe Illustrator CS6 and CC
When importing an SVG into Illustrator, the operation fails with an unknown error [CANT]. A workaround for this Adobe-side bug.
Solving NDK build issues on OS X
Troubleshooting native development kit compilation problems on Mac OS X.
Programmatically adding PHP generated TypoScript to the backend configuration
Integrating dynamically generated TypoScript into Typo3 backend setups using PHP.
ArgumentError: Could not parse PKey: no start line
Debugging an SSH key parsing error encountered during deployment.
Validating IP-Addresses in PHP
Using PHP filter functions with flags like FILTER_FLAG_IPV4 and FILTER_FLAG_IPV6, and understanding how filter_var handles reserved IP addresses.
Cocoa: Using NSTrackingArea
A short tutorial on using Cocoa's NSTrackingArea to capture mouseEntered and mouseExited events.
cat ~/contact.txt