www.fuchsfelge.com

Bugsink: https://bugsink.cytrus.de/issues/issue/2706bf55-672d-48a1-a978-0b4b242915d3/event/last/

Typ: NEW issue

Projekt: www-fuchsfelge-com

Bugsink Alert

Exception: Call to a member function getTitle() on null

Automatisch erstellt durch n8n

KI-Analyse:

1. Root Cause Identified¶

The error Call to a member function getTitle() on null indicates that a null object is being dereferenced. In the context of TYPO3's HTTP kernel stack, this occurs during the frontend bootstrap in AbstractApplication::run() (around line 106). The site resolution mechanism (TYPO3\CMS\Core\Site\Resolver\SiteResolver) fails to find a matching site configuration for the incoming request. Consequently, the site object remains null, and any subsequent call to getTitle() on it triggers the fatal error.

Typical triggers:

• The request host/domain is not mapped in the "Sites" module configuration.
• Corrupted or outdated cache (siteConfiguration cache pages).
• Misconfiguration of the VerifyHostHeader middleware (listed in your stack at frame -/vendor/typo3/cms-core/Classes/Middleware/VerifyHostHeader.php:55), which may block or alter the host matching process.
• Missing base, rootPageId, or languages in the site configuration.

2. Concrete Fix Description¶

1. Clear all TYPO3 caches immediately:

   typo3cms cache:flush
   # or via Install Tool: "Flush all caches"
   

2. Verify site configuration in the TYPO3 Backend:
   • Navigate to Tools > Sites (or siteadmin module).
   • Confirm that the requesting host/domain is listed under Root permissions or has a matching Configuration.
   • Ensure each site record has a valid base URL, rootPageId, and configured languages.
3. Inspect VerifyHostHeader middleware:
   • Check your Configuration/Backend/HostHeaderConfiguration.php (or AdditionalConfiguration.php).
   • Ensure ALLOWED_HOSTS or the middleware's matching logic includes the actual request host. If misconfigured, either adjust the whitelist or temporarily disable the middleware to verify if the error persists.
4. Check for custom code invoking getTitle():
   • If you have extensions or custom frontend code that calls getTitle() on a site/page object, wrap it with a null guard:

     if ($site = $this->getSite()) {
         $title = $site->getTitle();
     }
     

   • However, the primary fix remains correct site configuration.

3. Affected TYPO3 Extension¶

The issue originates from TYPO3 Core (TYPO3\CMS\Core), specifically the Site Resolution and Http Kernel components. The stack traces point to:

• AbstractApplication::run / handle
• MiddlewareDispatcher (including VerifyHostHeader, NormalizedParamsAttribute, ResponsePropagation)

There is no single "extension" to blame; rather, the project's site configuration (managed in the backend "Sites" module) is the responsible entity. If an extension alters site configuration loading or host handling, it could contribute, but the root is core site handling.

4. Confidence Score¶

85%
High confidence that the site object is null due to missing/mismatched host mapping or cache issues. The exact line number (106 in AbstractApplication) may vary slightly between TYPO3 11/12/13, but the pattern is consistent. Alternative causes (e.g., custom code calling getTitle() on a null object) are possible but less likely given the pure core middleware stack.