Find the culprit! - a module debugging helper

Latest version1.4.6
Minimum Core9
Compatible Core10
Last updated8 months ago
Created2 years ago
Systems All systems
Project source Project URL
Report bugs Bug tracker URL
Read-me Readme URL
Changelog Changelog URL
License License URL

This module helps you debug compatibility issues of modules, by finding the module that is responsible for the issue, without having to manually activate and deactivate all your modules yourself. Just click the Find the culprit button in Module Management to start the process.

  • You will be asked to select a module to keep active at all times. Choose the module that you want to debug.
  • Your page will refresh, deactivating all modules, except the chosen one and this.
  • Check whether your issue still persists.
  • If the issue persists, the module will start a binary search by only reactivating half of your previous modules, refreshing the page, going on like this until the culprit is found.
    • Just follow the prompts appearing after each refresh.
    • Depending on the amount of modules you have installed this process could take a while, but at most log(n) + 2 iterations, where n is the amount of modules you have activated.
  • If you accidently close one of the prompts, just refresh the page manually and it will reappear.
Notify of
1 Comment
Inline Feedbacks
View all comments
1 year ago

This is not usually a module that you need to have active all the time. Usually it’s just lying around and you don’t need to use it—that is, until some other module rung amok and you need to find out which one it is. And then, this module is a god send. It makes finding problematic modules so much easier.
While it’s definitely not necessary to have it active at all times, everybody should have this at hand for the time when it’s needed—and that time will come.

Would love your thoughts, please comment.x