>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3521410. --> Reported by: [jrockowitz](https://www.drupal.org/user/371407) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Similar to Views, Metatags, and Webform, there are many plugins that help power the ECA module. The <a href="https://ecaguide.org/">ECA Guide</a> provides documentation for all available ECA plugins. Still, it would be beneficial for site builders and developers to see all installed ECA plugins in one report on a website.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Provides an overview of plugins used by the ECA module.</p> <p>Here is a <a href="https://www.drupal.org/sandbox/jrockowitz/3521245">sandbox module</a> for the ECA Report. </p> <p>Below is an animated GIF showing the ECA plugins reports.</p> <p><a href="https://www.drupal.org/files/project-images/eca_report.gif"><img src="https://www.drupal.org/files/project-images/eca_report.gif" width="600" alt="ECA Report demo"></a></p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li>Determine if the ECA Report module should be included in the core ECA module. (I am fine if it is not)<br><br> Options for inclusion in ECA <ul> <li>Add to eca.module</li> <li>Add to eca_ui.module (similar to Views plugin report)</li> <li>Add new eca_report.module</li> </ul> </li> <li>Determine what information should be included in the reports</li> <li>Determine if and what test coverage is needed</li> <li>Finalized code to meet ECA's coding standards.</li> <li>Merge into ECA core or promote to a maintained contributed ECA Report module</li> </ul> <h3 id="summary-ui-changes">User interface changes</h3> <p>New 'ECA plugins' report (/admin/reports/eca-plugins/events) </p> <h3 id="summary-api-changes">API changes</h3> <p>N/A</p> <h3 id="summary-data-model-changes">Data model changes</h3> <p>N/A</p>