We've all done it. When we needed to find something in a log, we just did a cat or a tail and piped it to grep. Maybe we told grep to also show us X lines before and after what it found. That works fine and dandy when you've got just one or two servers. But what about 30, or 300, or 3000?
About a year and a half ago, I came across a post by Miguel Jacq about deploying Drupal automatically with Jenkins. I had grown tired of the manual backup->upload->test->crossFingers->pray->yellExpletives approach to developing or upgrading a Drupal site.
Every Drupal developer knows that there many configuration settings that are similar between the sites that they build, whether it's a personal preference or a trend among clients. And every developer that has been around Drupal more than a few minutes knows about the Features module.
A some already know, I have chosen to start hosting Drupal installs for clients. At some point (hopefully soon), I'd like to open this service up to the public. But that's not what you came here to read about.
I recently worked on a project where the main menu items were to be displayed as images. Of course, stylish menu items are usually displayed using text that's been styled with Cufón (or a similar solution) and using CSS sprites for the background. But in this case, there wasn't text.
Now, I could have worked on updating the Imagemenu module to work with Drupal 7, but there just wasn't enough time in the budget. So instead, I decided to use a hook in template.php to get the job done for me.
Yeah, this type of post is so over done. I know. But after doing a couple of Drupal 7 sites (and working on a couple of SaaS solutions that I may be offering later this year), I feel like I need to offer my opinion on what D7 modules you absolutely must have on your website.
First up, we've got the absolute essential contributed modules that you must install. While you can build a Drupal website without these modules, you're really hindering yourself without using these.
If there is a shortcoming in Drupal, its the way the menu system is handled. In this particular case, its that custom ID's for links added via the Menu Attributes module are added to the anchor tag and not the list item tag. While this is great for theming that particular link, it can cause difficulties when using most jQuery scripts to modify the display of your menus since the <li> tags won't have any identification.
You've finally gotten your Drupal website to the point where you feel like it is ready to go, but during final testing it seems painfully slow. With page loading speed a factor in customer retention (as well as search engine rankings), you need your pages to load as swiftly as possible.