Agaric

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

This will be a copy-paste of http://mclear.co.uk/2011/08/01/install-etherpad-lite-on-ubuntu/ except for a few things taken from https://github.com/Pita/etherpad-lite#readme and workarounds when things do not go as planned.

• Better breadcrumbs — http://drupal.org/project/hansel
• Views infinite scroll (there are two, one is better it looks)

When developing a site it is well known you need to log in as different users to properly test functionality, or you will always be surprised by incorrectly-configured permissions.

However, it should be much easier to test out working as a given user role by anyone with these privileges.

As long as gem and rvm are already set up (see RubyGems and RVM on Ubuntu), all you need to do is:

Most recently on Ubuntu: This worked with sudo.

Background

Main Gotcha:
compass-susy-plugin does not show on gem list

In brief: The code at the bottom of this post deletes the named fields. If you are changing the field type for one or more fields, put it in an update hook for a feature module and run update.php before running features revert, your feature will happily rebuild the fields with their new settings. This destroys data.

FieldException: Cannot change an existing field's type. in field_update_field() (line 230 of /home/ben/code/sdl/web/modules/field/field.crud.inc).

CS would like a module that lets you set in which places you want to be required to confirm delete and which places should just let you delete.

• Menu items-- don't make me confirm
• Content-- make sure

I don't think the confirm form is necessary to present cross-site scripting-- that's in the token with the form (or delete link— that might be an easy way to do this, change one or the other to links so you can visually see if you're getting a confirmation or not, and maybe think twice faster).

If you hate downloading and unzipping the initial feature you create as much as i do, because you haven't bothered with that foolishness since Drush, this post is for you.

This is the minimal information needed (from my experimentation) for Features to recognize your module as a Features module. Then you can add variables and other features through the UI (or Drush), and drush fu feature_example to update your module code (where feature_example is the name of your feature) and fu stands for features-update.

In feature_example.info:

Thanks in part to
http://sachachua.com/blog/2008/07/eclipse-to-emacs-navigating-your-source-tree/

Set-up:

(If not already installed: sudo apt-get install exuberant-ctags)

ctags -R -f ctagstags --languages=php --langmap=php:.module.php.inc.engine.profile .

In .vimrc,

set tags=ctagstags;/

In .bashrc

All, not just most, but all the content on a particular site was set to be posted without showing the by-line or submitted by text. Given this requirement, it makes no sense to have search results show the user that submitted the content, every time. This can be themed away in search-result.tpl.php or it can be removed with a pre-process function as shown below.

You can do this from a module or a theme, where 'example' is the system name of that module or theme:

Created a feature that would be easily shareable among Drupal sites except for a big failing of Drupal to allow for module-provided sensible default permissions.