User login


Theming with Display Suite and Preprocess Functions

Display Suite does not use node-*.tpl.php. This would is be by design. There are three ways i see to bring in custom elements.

Custom fields

Typical usage for custom elements would seem to be creating entire custom 'fields' (as opposed to small variables) which can then be placed by Display Suite-- as shown in the first part of this post:

Procedure for resolving a a left-behind branch that has merge conflicts

DRAFT. Better methods from better minds invited!

Situation: Someone has been working away wonderfully on a git branch on your project. You do some crazy stuff with it over the weekend, and when they, on their continnum branch, go git pull --rebase origin continuum and get conflicts they don't know how to deal with, or when they go git fetch origin and git rebase master and have conflicts.

You want to take this off their hands.

Settings for sets of sites: Putting Drush configuration into your project repository

Inherit local-only options with 'parent'

Parent is not working across files. Filed support request:

In an aliases file that lives with your project, so for our SDL project, sdl.aliases.drushrc.php, put in all settings that are true no matter who is using Drush and from where. This is the settings for an externally hosted development collaboration site.

Organic Groups in Drupal 7 does not use entity IDs as group IDs

Update: Here is the code we currently use, abstracted into a helper function with lots of comments but it's really just two lines:

Installing Etherpad Light on Debian

It's actually called Etherpad Lite but i hate that spelling.

This will be a copy-paste of except for a few things taken from and workarounds when things do not go as planned.

Modules in consideration for the SDL project

Syndicate content