Hello,

The module is wonderful and we use it now on several hundred sites. I'm finding, however, that the description text for the block class field confuses non-developer users.

"You must add print block_class($block); to your theme's block.tpl.php file to make the classes appear" doesn't make much sense to our average site manager who can navigate bits and pieces of Drupal with ease but isn't entirely sure what PHP is.

I realize that there are more than a few ways to override this text if I want to change. I do wonder though if changing the text within the module itself might be of benefit to the majority of the module's users. Clearly you folks need to inform developers that they need to tweak their block.tpl.php files--given that you're doing so already in the install instructions on the project front page, I have to wonder--how necessary is this text on the block configuration page? Could it instead be a message that pops up when the module is first installed?

That's my two cents. May thanks for your hard work on a truly useful module.

Comments

todd nienkerk’s picture

Title: Help text confusing to non-developer users » Move theme configuration instructions to a help page
Category: support » task

I think the best solution is to (1) provide a reminder when the module is first installed to add the PHP to one's theme and (2) provide a link to a help page in that message and below the class field that explains how to add the PHP to the theme.

We'll add this to the list of changes.

mirabuck’s picture

That sounds like a soound solution to me. Many thanks for addressing this.

berenddeboer’s picture

Status: Active » Fixed

Eh, we are using preprocess_block now right? So do we really need this?

And besides, the text in the README.txt looks pretty complete to me now.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.