I'm a Drupal Architect and developer. I've been a software developer since all mice had fur, "front-end" and "back-end" primarily related to horses, and blue tooth was something you got from eating raspberry Italian ice. There's a line in the ether between undiscovered wisdom and uncorrected folly. Feel free to have a poke around and note you might find either.
An example of programmatically creating a term reference entity field.
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.
Drupal 7 Views Cookbook has been fully revised and painstakingly tested.
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 received the following response in my Mac terminal window: composer: command not found. What to do?
There are times when the connection to your Drupal DB will need to be via ssl, such as when using an external DB service like clearDB. How do you accomplish this with regards to the settings.php file?
There are times when you create an array based on a stream of incoming data, and in doing so, are blissfully (or not) ignorant of the keys.
To be, or not to be, that is the question. Shakespeare never quite gets around to answering it, though. In Drupal 7, a similar existential question arises regarding entity references: Is it, or is it empty?