note

In Drupal it is quite easy to set breadcrumbs with the function drupal_set_breadcrumb(), which takes an array of links (as you would make with the l() function). It's a bit of a blunt instrument but it works (and wins out over hook_menu_breadcrumb_alter()).

This cheatsheet presumes you're already set up with VirtualBox and Vagrant, configured for Drupal. (Agaric has our own base box to have a head start on setting up for this purpose, but some of the magic is in the Vagrantfile stored with our projects.)

In a terminal, go to the directory holding your Vagrantfile and your project code. Then the fun begins.

vagrant up

to start the virtual machine.

You've upgraded migrate module from 7.x-2.5-rc2 or such to 7.x-2.6. Your migrations may run, or not run, with this complaining error: "Passing a group object to a migration constructor is now deprecated pass through the arguments array passed to the leaf class instead."

Replace this:

Wanted to be able to install selected things from Trisquel, such as IceCat, without changing everything over to Trisquel (yet).

To get access to Trisquel packages, add them to your sources list, add their keyring, and update:

https://trisquel.info/en/wiki/packages-repository

vi /etc/apt/sources.list

sudo apt-get install trisquel-keyring

A lot of this will apply for any small business (and won't apply to huge worker cooperatives, although technically our three-member collective is a multinational).

What we're looking for is a way to automatically display links on a Drupal site to people's profiles on known social media sites in the way they expect, e.g. @mlncn for Twitter, +ben.agaric for Google Plus, and whatever the heck for Facebook. Icons a plus.

Evaluated https://www.drupal.org/project/social_profile_field and was not impressed at all; both the inputter's user interface and the display are sorely lacking.

Vagrant box check update configuration error

The following settings don't exist: box_check_update

Commenting out this made it work fine:

# config.vm.box_check_update = true

But the better solution is to upgrade Vagrant.

The reason for the error is that Vagrant version 1.2.2, rather than 1.5 or 1.6, simply didn't know about that configuration setting, and complained, and quit.

DropLabs, in Los Angeles, offers coworking in a learning- and working-conducive space. A key feature is people supportive of their fellow coworkers' technical growth.

Krash "is an immersive co-living experience for entrepreneurs, hackers and doers." BOS/CHI/LA/NYC/DC

The error is pretty straightforward but the sheer confusion of where to place class files in your module (first off, yes, they do go in your module) might make this a pretty commonly googled error.

Drupal may give an error like this:

Error
The website has encountered an error. Please try again later.

Look in your logs for more detail:

tail -f -n100 /var/log/apache2/error.log

Here's the key problem:

I'm very interested in non-corporate ways of getting things done, and DrupalCon North America 2014 (held in Austin June 2-4) provided a surprising amount of information applicable to what could be called non-capitalist production.

Two sessions worth watching:

• https://austin2014.drupal.org/keynote-erynn-petersen

Among other things, look for the part where she talks about asymmetric warfare...