TYPO3 9.5升级至10.4后404页面触发页面未找到错误咨询
Hey there, let's work through this 404 error problem you're seeing post-upgrade. Based on the config snippet you shared, here are actionable steps to diagnose and fix it:
Verify the 404 page's validity
First, confirm that the page with UID 478 actually exists in your TYPO3 installation. Head to the List module and search for UID 478—make sure it's published (not hidden, deleted, or set to a future start date). TYPO3 10.4 enforces stricter checks for site-associated pages, so even a hidden page will break the error handler.Fix YAML config syntax
Looking at your config, it seems like there's a missing colon aftererrorHandler: Page—this is critical for YAML to parse correctly. Your corrected config should look like this:base: / baseVariants: { } errorHandling: - errorCode: '404' errorHandler: Page errorContentSource: 't3://page?uid=478'Double-check indentation too—YAML relies on it heavily, and TYPO3 10.4 is less forgiving of syntax mistakes than 9.5.
Clear all caches (non-negotiable)
After any TYPO3 upgrade, old cached configs or content can cause weird issues. Go to the TYPO3 backend's "Flush all caches" button (the lightning bolt in the top bar) and clear everything. If your server uses OPcache or APC, restart that service too—stale PHP opcode cache can prevent new configs from loading.Test the 404 page directly
Try accessing the page directly viaindex.php?id=478. If this page throws an error on its own, the problem isn't with the error handler—it's with the page content itself. Check for outdated extensions, incompatible content elements, or broken plugins on UID 478 that broke during the upgrade.Check site configuration association
Make sure your site config is correctly linked to the root page of your site. Go to "Site Management" in the backend, select your site, and confirm the root page UID matches what's expected. A mismatched site root can prevent error handlers from resolving the page correctly.Dig into system logs
If none of the above works, check the TYPO3 system logs (under System → Log). Search for entries related to 404 errors or page UID 478—you might find specific messages like "Page not found" due to permissions, missing records, or extension conflicts that aren't visible on the frontend.
内容的提问来源于stack exchange,提问作者user12414491

