(This falls squarely under the "Well, duh!" category, but remembering how long I used PHP without the benefit of a debugger myself, I figure it bears repeating.)
The flip side of Drupal's elegant and flexible system of hooks is that when you’re building a site that relies on lots of different modules, things can start to get a little bit slippery if you need to troubleshoot which module is hooking into the core and how/where/when.
Being “the web guy” in a FileMaker shop can sometimes be a solitary existence… even when you’re called upon to work on a FileMaker/Web integration point you usually get only a glimpse of the FileMaker solution you’re talking to, and the FileMaker developer gets only a glimpse into whatever it is you’re putting together. Most of the time there is not much discussion about what is going on behind the developers’ respective hoods, and that’s generally OK.
A fairly common question when preparing to integrate your web application’s MySQL database into a FileMaker solution using ESS (External SQL Sources) is, “What information do I need from my hosting provider to connect to MySQL?”
The list is pretty straightforward, and you’ll probably have an easier time asking your hosting company for these MySQL specifics than trying to explain FileMaker ESS:
system_get_module_admin_tasks() function attempts to ferret out any administrator pages that a given module provides, and is used to add them to each module’s section on the
admin/by-module screen. If you provide admin help in your implementation of
hook_help() it will also automatically display links to those administrator pages at the bottom of the
admin/help/mymodule page (where
mymodule is the name of your hypothetical module.)