CiviCRM Sanity Checker

[JonGold]

I've been thinking a lot lately about the sorts of common problems we see in CiviCRM configuration, and how we could automate finding those problems.  For instance - I've seen instances where cron stopped running, file permissions changed, Directory Settings were pointing to non-existent directories, or directory paths didn't match up with the path set on the URLs screen.

Done correctly, we could create a tool that could detect these problems, and give a first step to non-technical users to try when they post their problems to the forum.

My questions are:
* What do we think is the best mechanism for fixing these problems?  I like a Scheduled Job, but that won't detect broken cron, and doesn't answer a question of UI.  Drupal has an error report that covers some of these issues - that's another route.
* What other common problems do we see that could be easily addressed with this?

[Coleman Watts]

@JonGold sounds like you are wanting to start work on https://issues.civicrm.org/jira/browse/CRM-13823
That would be awesome! Let me know if there's anything I can do to help you get started.

[JonGold]

Hey Coleman,

Glad to see that ticket!  I just updated it with suggestions from this thread - and I'll definitely keep it in mind for when I have some bandwidth to do pro bono Civi work.