Blair Wadman gives his list of Drupal development tools. In our opinion Drupal developers should use at least half of this list, if not more:
You can build Drupal websites with just a few tools, such as a code editor, browser and dev environment. While it is not necessary to use additional tools, tools do make your life easier and can save you a tonne of time and improve the quality of your work. So let’s take a look at the essential tools to use to develop with Drupal.
... I wanted to provide a more comprehensive look at Drupal's core caching, explaining how some of this stuff is actually working under the hood. ...
Page caching is when Drupal takes the entire rendered output of a page request and stores it in the Database (or another cache store, defaults to DB). Cached pages only apply to anonymous traffic - meaning users that are not logged in and do not have any "session" data (like a product added to a shopping cart). Since the page is rendered once and stored in its entirety in the cache, there is no opportunity to change the content. Dynamic content for logged in users like a simple welcome message, or a list of items in a shopping cart, can't work in tandem with Drupal's built in page caching.
- Drush out-of-box commands
- Drush contrib commands
- Drush Aliases
- Improve your workflow with drush
Try using Drush wherever it’s possible and you will save your time!
Jonathan Jordan of Metal Toad on breakpoints in the Drupal Behat Extension:
Today I learned that the Drupal Behat Extension provides an extremely useful step definition for debugging. Breakpoints!Then I break
It allows you to stop at a certain point in the test scenario so you can take a closer look at what is going on in the browser. When you are ready to move on, you just hit enter in your terminal window.
As we just ran into this issue, we would like to warn all customers not to upgrade to Rules 2.5, or install the patch if you have done so. Else, if you edit or disable rules, they will disappear without a trace.
We recently upgraded our web servers to run Ubuntu 12.04 instead of Ubuntu 10.04. This was done completely transparently, and not many customers would have noticed. So all websites are now running PHP 5.3.10 instead of PHP 5.3.
Xplain Hosting started with Ubuntu 8.04 on Amazon AWS. We went to 9.04, and later to 10.04. Our webservers have been running that version till now basically. Other servers like our database servers were running 12.04 for a long time, but upgrading the web server was postponed for a while.
Unlike previous occassions where we basically built a server image from scratch, this time we used Ansible. Almost our entire infrastructure is now described with Ansible playbooks, and Ansible has become an indispensable tool to manage our infrastructure.
When we upgrade to Ubuntu 14.04, the only thing to do would be to run the playbook, and we have our server installed:
So this really future proves our server infrastructure.
Now the purpose here is to change the default Drupal messages display system ... to this a nice modal message using Bootstrap 3.
Anyone who wants to style Drupal's status messages can learn something from this.
Codi Lechasseur writes on doing a Drupal site audit, for example in case you are taking over an existing site:
A site audit accomplishes a couple things:
- Provides the client with an overview of where their site currently sits in terms of performace, security and general quality of the build.
- It provides us with a good knowledge of the estimated effort needed before "diving in".
He mentions some useful modules to help you do this.