User login

Definitive Guide to Drupal 7

See Drupal 7 permissions internal system names

Asked in IRC #drupal

has anyone made a Drupal 7 module for seeing the system names for all permissions? (now the Permissions UI uses human-friendly names and descriptions)

No response.

Update: This has been incorporated into Xray.

Xray module visualization notes

Visualize plugin will be great for graphs (like what percentage of nodes on a site are each node type)

Drupal as a Relationship with a Happy Ending

Notes from the presentation by Julia KM:

Great security
core very lightweight
used by lots of smart, helpful people

The Rough Period
not all modules are created equal - must evaluate quality
CRM + E-commerce = Pain

Hacking core until
i decided to write my own menu system - not a good idea
always a good idea to work within the constraints of Drupal


In searching for the perfect name for my dreamed-for annotation module, i found Marginalia. And through the name, i found a JavaScript tool already built to do it!

The search is over:

Must use ->fields() method in select statements in Drupal 7 database layer (DBTNG)

An error like this one:

PDOException: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'FROM block block WHERE (theme = 'bartik')' at line 1: SELECT FROM {block} block WHERE (theme = :db_condition_placeholder_0) ; Array ( [:db_condition_placeholder_0] => bartik ) in xray_block_statistics() (line 80 of /home/ben/workspace/dgd7all/sites/default/modules/xray/xray.module).

Render in Drupal 7 notes

Drupal 7 Render Arrays (and the new Render Example) by rfay

Using the theme function: drupal 7 theme() should always take an array, a string is not officially supported. See Handing theme() function an empty string or NULL as its second parameter triggers a fatal error.

Sadly, some brilliant text had to be jettisoned from the Definitive Guide. Some of it lives here.

Castaways from the writing process:

Of course we should have an API or three. We know Jeff Eaton would stick APIs in a novelty module called Eldorado Superfly. No, actually, he didn't. From this we can learn that if our module is simple enough and uses enough of Drupal's APIs, it doesn't need to create its own.

[Eaton] drawing on his experience with VotingAPI, which, we might note, puts API right in the name of the module, and if that doesn't mean something, what does?

Cloning git locally to test a Drupal module in development on multiple sites

Working on a site ( which is in its own big Git repository. But when working on a module that's custom to the site but probably will become generalized and contributed back, we simply git init in that module's directory to make it a repository too. No git submodules or other voodoo. In addition to getting us an independent commit history for that module, it gives us the ability to throw that module into other situations and work on it there.

Syndicate content