>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3546971. --> Reported by: [istankevych](https://www.drupal.org/user/805946) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>The domain_path module is not compatible with Drupal 11 due to the deprecation of <code>AliasWhitelistInterface</code> in favor of <code>AliasPrefixListInterface</code>. When enabling the domain_path module on Drupal 11, the site breaks with fatal errors because the module is still using the deprecated interface.</p> <p>The core issue is that in Drupal 11, the <code>path_alias.manager</code> service constructor changed from using <code>AliasWhitelistInterface</code> to <code>AliasPrefixListInterface</code>, but the domain_path module's <code>DomainPathAliasManager</code> class still references the old interface.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <p>1. Install Drupal 11.1.8<br> 2. Install the domain_path module (8.x-1.5)<br> 3. Enable the domain_path module<br> 4. Clear cache or access the site<br> 5. Site breaks with fatal error: <code>TypeError: Drupal\domain_path\DomainPathAliasManager::__construct(): Argument #1 ($alias_repository) must be of type Drupal\path_alias\AliasRepositoryInterface, string given</code></p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Update the <code>DomainPathAliasManager</code> class to use the new <code>AliasPrefixListInterface</code> instead of the deprecated `AliasWhitelistInterface`:</p> <p>1. Change the import statement from <code>use Drupal\path_alias\AliasWhitelistInterface;</code> to <code>use Drupal\path_alias\AliasPrefixListInterface;</code><br> 2. Update the constructor parameter from <code>AliasWhitelistInterface $whitelist</code> to <code>AliasPrefixListInterface $prefix_list</code><br> 3. Update the parameter documentation to reflect the new interface<br> 4. Update the parent constructor call to use the new parameter name</p> <p>This change maintains backward compatibility while ensuring the module works with Drupal 11's updated path alias system.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>- [ ] Apply the patch to the domain_path module<br> - [ ] Test the module functionality with Drupal 11<br> - [ ] Verify that domain-specific path aliases work correctly<br> - [ ] Test with various domain configurations<br> - [ ] Update module documentation if needed</p> <h3 id="summary-ui-changes">User interface changes</h3> <p>No user interface changes. This is a backend compatibility fix that maintains all existing functionality.</p> <h3 id="summary-api-changes">API changes</h3> <p><strong>Breaking change</strong>: The <code>DomainPathAliasManager::__construct()</code> method signature changes:<br> - <strong>Before</strong>: <code>__construct(AliasRepositoryInterface $alias_repository, AliasWhitelistInterface $whitelist, LanguageManagerInterface $language_manager, CacheBackendInterface $cache, TimeInterface $time)</code><br> - <strong>After</strong>: <code>__construct(AliasRepositoryInterface $alias_repository, AliasPrefixListInterface $prefix_list, LanguageManagerInterface $language_manager, CacheBackendInterface $cache, TimeInterface $time)</code></p> <p>This change is necessary for Drupal 11 compatibility and follows the core API changes.</p> <h3 id="summary-data-model-changes">Data model changes</h3> <p>No data model changes. The fix only updates the service interface usage without affecting any stored data or database schema.</p>