Search Results

Current constraints include: History constraint (checks hashed password against a collection of users previous hashed passwords looking for recent duplicates) Now, all you need is to take this constrain …

Anywhere in code, you can use code like that: if ( arg(0) == 'user' // test if you are on user page and is_numeric(arg(1)) // and if user ID was provided and is possibly valid (a number) a …

First kind of flag is trivial for logged in users, too. The point is - I need to make first kind of flag available for anonymous users, too. … For logged in users it defaults to their email, and if they decide to change it, so be it, I have a way to reach them anyway. …

If you can use SSH, or other shell, it's easy: Install Drush. On Ubuntu, follow this document. Or simply unpack it and add it's directory to system's PATH variable (OS dependant). Enter your Drupal' …

First thing first, you need a way to communicate with your users. Drupal sends quite a lot of data to users, like password restoration mails. …

Never put any business logic into tpl files. They can be cached. So unless it's the "if odd, add class odd" type of logic, it may fail you miserably. If you need more elaborate rules than Field Permis …

Omit UIDs lower than 1, or select only users with name, etc. …

User Relationships module seems to be the answer: User Relationship Node Access lets users control access to their content based on relationships …

You can control it using hook_node_access($node, $operation, $account) for Drupal 7. For Drupal 6 one can use hook_nodeapi() for similar result. When $operation is view, first update usage index for …

Username needs to be unique - Drupal needs to know who to log in. Having that said, you can separate login user name from display user name. Simply add non-unique "display name" text field, and in tem …

Of course it can! Was covered in docs and in even more docs and is supported by Wysiwyg, with helpful modules like Insert to make it even easier.

Then both guests and logged in users will see identical menu, but they will actually get different set of menu items. …

Use hook_menu_alter() to remove default registration page from menu system. Simply unset($items['user/register']); and clear menu cache.

Go to edit screen of your view. In right column, Advanced section, click Query settings. Check Disable Query Rewritting. Now Drupal permissions will not affect views results.

Simply go to Home > Administration > Configuration > People > Account settings and add fields you need. Use Conditional Fields module to conditionally show a text box. Now you need to use Rules. See …