Submitted by andy.pangus on Fri, 05/18/2012 - 11:47
Handling the multiple copies of Drupal's settings.php file needed for each site, between the development, staging, and live environments, can be a bit of a hassle. Database settings and other configurations almost always vary from environment to environment so having a simple way to manage these differences would be fantastic. Always on the look out for work-flow improvements, I had heard about this gem at DrupalCon Denver in March but had yet to implement it in any of my projects.
Submitted by andy.pangus on Fri, 04/20/2012 - 18:02
Everybody's development environment is unique to them: some use Vim while others may use Dreamweaver or Notepad, some develop on a Mac while others use a PC or Linux box. The tools you use, by and large, should speed up delivery and increase the quality of your finished product. Your technology toolbox should always be growing as you learn about and add new possibilities for making your life easier. So for the lazy out there, using Virtual Hosts on your web server should be a no-brainer. So what is a Virtual Host? The Apache Software Foundation says:
Submitted by andy.pangus on Wed, 03/14/2012 - 17:48
Recently I became a maintainer for the Marketo Munchkin module. We have just released v2 for the 7.x branch of the module and have added a new feature which allows you to submit data about potential Leads to your account at http://www.marketo.com/. There are plans to port v2 back to the 6.x branch as well as for adding more features. See the module page for more info.
Submitted by andy.pangus on Sat, 11/19/2011 - 09:29
I am attending Drupal Camp Austin 2011 this weekend and writing about the sessions and updating throughout the weekend.
9:00am - I've just arrived and am getting settled at Drupal Camp Austin. We're waiting for the welcoming address to start. I plan on following most of the Developer schedule for the day with one or two alterations. Here's the plan:
Submitted by andy.pangus on Sat, 10/22/2011 - 00:05
Creating content types for pleasure and fun sometimes means that you need to have fields populated with data when first presented to the author during node creation. This functionality usually involves two things: someplace to create/modify those default values and injecting that value into your node creation forms. For this example, we're going to create a simple content type with a title, body, and an extra textfield and we'll populate that textfield with a value we specified using a settings form we added to our very own configurations section.
Submitted by andy.pangus on Fri, 08/19/2011 - 21:09
According to the Drupal API:
Tokens are placeholders that can be put into text by using the syntax [type:token], where type is the machine-readable name of a token type, and token is the machine-readable name of a token within this group.
Submitted by andy.pangus on Wed, 08/03/2011 - 11:28
In a couple of the Simple Content Type examples we have done so far there has been a required helper module which creates and adds a vocabulary with some terms using the Taxonomy module. Creating vocabularies and terms through code is a fairly straightforward process. We will use two hooks and several helper functions to handle all the lifting.