This is something I use now on every site that has sidebars. This code removes the related styles Drupal core erroneously includes when using a custom theme and then adds new classes based on the existence of content in the sidebar region.
Since making the new Drupal-powered Tesla Universe live, I've been fighting comment spam. I've tested all the common methods such as Mollum and Honeypot and while these have made a significant impact, I still received several spam comment submissions per day. All these spam comments have one thing in common in that they are full of links.
A common need for a lot of small e-commerce shop owners is the ability to update their product's pricing from a vendor-provided spreadsheet. One way of doing this is with a VBO. The code below will add a new VBO for the commerce_product entity. Once you have this code in your custom module, you'll need to edit the Commerce Products view (admin/structure/views/view/commerce_products) to add the "Bulk operations: Commerce Product" field.
I've recently been working to migrate a website into Drupal for a well-known food supplier and I was sharing this experience with my friend and mentor, Amitai Burstein, at Drupalcon in LA. Amitai encouraged me to write this post as he didn't recall of ever hearing of anyone taking this approach. So without further ado...
Here's a pretty critical need for Drupal 7 SEO. This code alters the document title and page title for pages in paginated sets such as taxonomy terms and search results. Both titles beyond the first page will be modified to include the page number.
This gives these pages unique titles and allows maximum SEO equity in the first page.
Note: This code assumes that page.tpl.php file has logic to display $title as the h1, which isn't default.
The Automatic Entity Label module is a standard module in my toolkit. I use it in conjunction with the Serial Field module to automatically create titles like "My Content 1", "My Content 2", etc. using a pattern like "My Content [node:field_increment]". One less field for an editor to populate makes for happy editors.
The Field Permissions module allows you to restrict access to fields for specific roles. This is nice for having all fields in one entity while being able to limit some fields for admin-only use. When a user saves an entity which contains a field he doesn't have permissions for the value for the field is empty. This is regardless of whether or not the field is required at the node level. This makes sense for most occasions, but there are others where a default value is needed.
I first learned about Leaflet at Drupalcon Portland and have been using it regularly now for mapping-related needs. Recently, a client wanted to display employee photos on a map instead of markers. One way to do this is by using the IP Geolocation Views & Maps module. I believe the intention for this module's custom marker support is geared more toward using a group of markers rather than having a one-to-one relationship. Think colors instead of photos...
This week I started a project to integrate the popular AJAX Chat open-source, PHP-based web chat software with Drupal 7. This was after reviewing the two existing Drupal chat modules in contrib. The first I reviewed is DrupalChat, which is a very nice module. It works a lot like Facebook's chat. The reason I ruled DrupalChat out is because its focus seems more toward one-on-one chat.