If you write PHP on a Windows computer then setting up a reliable method for debugging your scripts will at some point be something you will want if not need to do for when simply writing out variables to the page will not do.
Type: Media Group Website
Date: April 2010
Halldale are the leading suppliers of news and news publications to the flight simulation and training market publishing a number of magazines, hosting conferences and attending trade shows as well as engaging their audience through through electronic news and online industry directories.
Type: Airline News Website
Date: October 2010
Type: Corporate Website
Date: July 2010
Tigerfish Interactive was asked by the CMS Group to renew their current website design and develop the new website in Drupal to allow better SEO & Google rankings. Tigerfish was then asked to give the company a social media makeover allowing feeds from twitter to appear on the website and allow links to websites such as LinkedIn.
Drupal 6's menu API can be a bit confusing, there are many functions with not a lot of explanation as to what each one does.
It may seem like a simple function, but it is something that I seem to come across fairly regularly. What happens when you want to pass a custom menu to the theme. Drupal usefully provides variables to the theme for Primary Links and Secondary Links, but how do you go about setting your own custom ones?
You may have read Otto's article, “Creating vocabularies and terms when installing a Drupal module” that covers the basics of creating a Vocabulary and adding a term as part of the module install file.
Coming from a .NET background, I love the Visual Studio debugger. I can stop code execution at any time and look at the values of any of the variables. There's none of this dumping huge arrays to the web page and examining the output. I've wanted to set up a debugger for Drupal with Eclipse for a long time now, and setup instructions vary wildly. Here's my take on it.
You will need:
UPDATE: After overwhelming interest, and an action-packed recruitment process, we have filled our vacancies with great new team members. Keep an eye out for further vacancies in the future!
Here's a great chance to work with a passionate bunch of Drupal-istas in Cheltenham. We love making Drupal sites, but there aren't enough of us to get everything done, so we need someone like you!
Having just left DrupalCon's BoF session on the proposed DrupalCRM project, I thought I would take the opportunity to reflect on the progress we made and where the project will be going from here.
A great turnout saw around 20 people show up to discuss the current state of the project and its goals. To skip directly to the conclusions, the DrupalCRM project is aiming to produce a native Drupal CRM in Drupal 7 (which can then be backported to Drupal 6) which is flexible, robust and does not suck to use.