Something that irks me when fighting spam on drupal.org is that there is no visible cue on the user's profile page as to whether an account is active or blocked (contrary to node pages, where the node's status is passed as a class to node.tpl.php).
Attached patch slightly alters the user-profile.tpl.php template and template_preprocess_user_profile() function to introduce an additional class, profile-banned or profile-active, based on account status and similar to how core handles status for nodes.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | user-profile-status.patch | 2.08 KB | mr.baileys |
| #1 | user-profile-status.patch | 985 bytes | mr.baileys |
| user-profile-status.patch | 1019 bytes | mr.baileys |
Comments
Comment #1
mr.baileysAnd one without debug statements....
Comment #3
mr.baileysNew patch that fixes the test failure (RDFa test was checking for a hardcoded "class='profile'") and adds a CSS rule to set the background for blocked users (using the same background-color core uses for unpublished nodes)
Comment #4
bryanhirsch commentedI can't get this patch to apply any changes. I suspect the pass above is a false positive. Git doesn't report errors when applied inside the modules directory. But it doesn't change anything.
The first line of the patch in post #3 looks like this:
diff --git modules/user/user-profile.tpl.php modules/user/user-profile.tpl.php
I think it's missing the "a" and "b" git puts in front of these file paths. When I make a change and do git diff, the beginning of my patch file looks like this:
diff --git a/modules/user/user-profile.tpl.php b/modules/user/user-profile.tpl.php