User login

Drupal

Agaric's policy on releasing code

[We wrote this to a potential new client in 2007.]

I do want to address one item in the request for information early on:

"All business plan, content and code are confidential and are to be owned by
the client and released at their sole discretion."

The only issue here is with "code".

Features cannot update the names of roles

Features stores Drupal roles as their string name, not their ID. This is so that they are in theory exportable (like Views, variables, and - when enhanced by features_extra - blocks and vocabularies). Naming something by a machine name rather than an autoincremented numeric database ID allows

However, the only information carried with a role is its name! Therefore, trying to take a role name change from one site to another results in the following:

Installing Cygwin for Drupal patch testing and development

Update: See Randy Fay's Cygwin quickstart tutorial, http://randyfay.com/node/70

Many Drupal things are best done in a UNIX-like environment. One solution is to run a Linux distribution like Ubuntu in a virtual machine, as is provided by http://drupal.org/project/quickstart. Another solution (on Microsoft Windows) is Cygwin, to bring the power of the UNIX command line to Windows.

Browsing the Drupal database

Moshe on browsing the database at the Boston

He uses the Mac program SequelPro (completely free and open source). http://www.sequelpro.com/

PHPmyadmin: http://www.phpmyadmin.net

Find $db_url in settings.php

username, password, host, and database name.

Can put this data into Sequel Pro.

Bottom line: as long as you have a backup, do not be afraid to fiddle with your database!

Syndicate content