TYPO3 RealURL扩展配置后URL冲突及页面无法访问求助

Let’s tackle this URL conflict issue step by step—you’re clearly hitting a duplicate slug problem between your parent Blog page (865) and child Blog page (722), which is confusing RealURL’s URL routing. Here’s how to resolve it:

1. Resolve Duplicate Page Slugs #

The core issue is that both /Home/Blog (page 865) and /Home/Blog/Blog (page 722) are using the same blog slug for their speaking URL. RealURL can’t distinguish between them, hence the conflict.

• Go to the TYPO3 backend and navigate to page 865 (/Home/Blog)
• Open its page properties, go to the SEO/RealURL tab, and confirm its slug is set to blog
• Now navigate to page 722 (/Home/Blog/Blog)
• Change its slug to something unique (e.g., blog-posts, blog-detail—anything that doesn’t match the parent page’s slug)
• Save the page properties

2. Adjust RealURL Configuration (If Needed) #

Double-check your RealURL config to ensure it’s handling page paths correctly for nested pages:

• In your pagePath section, confirm rootpage_id is set correctly for your domain (you already have this mapped via the $domains array, which looks good)
• If you’re using TYPO3 8 or later, make sure the userFunc (EXT:realurl/class.tx_realurl_advanced.php:&tx_realurl_advanced->main) is compatible with your TYPO3 version—this is standard for RealURL, but worth verifying

3. Clear All Relevant Caches #

You mentioned clearing three caches, but RealURL has its own dedicated caches that need to be wiped too:

• In the TYPO3 backend, go to System > Maintenance
• Look for the option to Clear RealURL URL Cache (this clears the tx_realurl_urldecodecache and tx_realurl_urlencodecache tables)
• If that option isn’t available, you can manually truncate those two tables in your database (always back up first!)
• Finally, clear your browser cache to avoid cached old URLs

4. Verify Redirect Rules #

Temporarily comment out your redirects in the RealURL config to rule out any interference:

// 'redirects' => array (
//  'support.html' => 'go/support-active'
// ),

Test if /en/blog loads after this—if it does, you can adjust the redirect rules to avoid conflicting with your blog paths.

5. Check News Plugin Configuration #

Since you have the News extension integrated, confirm its URL routing isn’t clashing with your page slugs:

• In your postVarSets section, the news route uses news as the segment, which shouldn’t conflict with blog, but double-check that your news list page isn’t assigned to a path that overlaps with your blog pages.

Once you’ve made these changes, test both /en/blog and /en/blog/article/ again—they should load without the conflict error.

内容的提问来源于stack exchange，提问作者Oday Banihani