Thanks to all who took the time to take the poll. The participation was great! Over 350 respondents, which is a number in excess of 10% of the DrupalCon attendance. There were couple comments that I'd like to address:
DON'T HACK CORE! It's THE cardinal rule of Drupal. Like another rule, Don't eat yellow snow, it's inviolate...immutable...or is it?
There is one circumstance when hacking core is a good thing. "Really?" you ask. Yes, definitely. Hacking core is a great way to find out how a particular part of Drupal is working, particularly if you can't use something like xdebug. In that case, if you want to see what the world looks like when you get to a certain place in the code, there's nothing better than sticking in some debug code. There are, however, some precautions you should take:
I was listening to Webchick's presentation on Upgrading YOUR Module to Drupal 8 (https://www.youtube.com/watch?v=wKdU2Q1NIZQ), following along with my own contributed module (https://drupal.org/project/node_theme) and when she reached a seemingly innocuous step
- drush dl drupalmoduleupgrader
- cd drupalmoduleupgrader
- composer install
I received the following response in my Mac terminal window
It took far too long, but I've finally posted a 7.x update for project Node Theme at https://drupal.org/project/node_theme.
Node Theme is used to control which theme a given path will use. "Node Theme" is a bit of a misnomer, a holdover from 6.x. It can be used to record the theme choice for any path on the site, and will seamlessly switch the rendering to that theme when the page is requested.