>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3585398. --> Reported by: [peximo](https://www.drupal.org/user/209981) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>The navigation_plus module defines its own ToolPluginManager in src/ToolPluginManager.php which uses the cache key tool_plugins and the alter hook tool_info:</p> <pre>&nbsp; $this-&gt;alterInfo('tool_info');<br>&nbsp; $this-&gt;setCacheBackend($cache_backend, 'tool_plugins');&nbsp;&nbsp;&nbsp;&nbsp; </pre><p>The <a href="https://www.drupal.org/project/tool">https://www.drupal.org/project/tool</a> module (drupal/tool) provides a generic framework for defining executable tool plugins and uses the same tool_plugins cache key and tool_info alter hook in its own plugin manager. When both modules are installed together: </p> <p>- Cache collisions &mdash; the two plugin managers share the same cache entry (tool_plugins), so one overwrites the other's cached definitions. This leads to missing or incorrect plugin definitions after a cache clear.<br> - Alter hook conflicts &mdash; implementations of hook_tool_info_alter() intended for one manager's plugins will incorrectly alter the other's definitions as well. </p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <p> 1. Install both navigation_plus and tool (drupal/tool).<br> 2. Clear caches.<br> 3. Observe missing or incorrect tool plugin definitions from one or both modules. </p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p> Prefix the navigation_plus identifiers with the module name to avoid the collision: </p> <pre>&nbsp;&nbsp; <br>&nbsp; $this-&gt;alterInfo('navigation_plus_tool_info');&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&nbsp; $this-&gt;setCacheBackend($cache_backend, 'navigation_plus_tool_plugins');</pre><p> This follows the Drupal convention that plugin managers should use module-namespaced cache keys and alter hook names to prevent conflicts with other modules.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <h3 id="summary-ui-changes">User interface changes</h3> <h3 id="summary-api-changes">API changes</h3> <h3 id="summary-data-model-changes">Data model changes</h3>