What this solution does
The ecl.conflictdetector module identifies modules and init.php files subscribed to the same Bitrix events.
The tool analyzes data from the database registry (b_module_to_module table), where handler order is determined by the SORT field, and performs static code analysis. The analysis covers /local/php_interface/init.php and /bitrix/php_interface/init.php files, as well as optionally include.php files from installed modules and additional paths specified in settings.
The interface displays a table with columns for event, number of handlers and modules, minimum SORT value, conflict flag, and a numbered list of handlers. Filters are available for event substring, module name, and showing only conflicting records. The "Rescan" button clears the cache and triggers a new scan.
Static analysis has limitations: it recognizes module and event arguments only as string literals. The execution order between different files cannot be guaranteed. require chains within init.php are not automatically traversed; paths must be explicitly specified in settings for their analysis.
General iT can install and configure this module and check how it works on your website.