Search Results

Have a look at the following issue: http://drupal.org/node/850932

There are two ways to do this. The pm_block_user module has settings that allow for role-based configurations for who is allowed to write whom. However, it is only possible to add positive rules. Me …

From the page that you linked to: // Replace 'inbox' with 'sent' to display sent messages or 'list' to display all messages. $query = _privatemsg_assemble_query('list', $user, 'inbox'); Note that t …

It's part of the Messages modules; it has nothing to do with Private messages. It's not a glitch, it's what this module does: a simple example of a way to deliver messages (notifications) to users.

Privatemsg views is currently only compatible with 6.x-1.x and looks rather unmaintained at this point. You can configure the displayed columns and their order in the Privatemsg settings. … Privatemsg adds tons of classes to that table, including a seperate class for every column and classes for rows with new messages and soon for unreplied messages too. …

The Privatemsg pages reside below /messages, a link to that page should have been added to the Navigation menu. … Privatemsg 6.x-2.x does allow to move it to the user profile by setting the url prefix in the settings to "user/%user/something". …

> Note: This requires Privatemsg 6.x-2.x …

This is currently working as designed. The message listings do not show your own username as you obviously are a recipient as it is displayed for you. It is however a limitation of the current system …

Yeah, Privatemsg doesn't really integrate with the world of Views and Panels. However, we do have enough hooks and templates to implement this. … And you can override the privatemsg-view.tpl.php template file to customize the whole thing. …

The normal user interface is at /messages, user/uid/messages is only meant to read messages of other users and is not a full replacement. 6.x-2.x has a feature that allows to move it around but it's …

Privatemsg 6.x-2.x has a Limits submodule built in, either use that version or use try out the separate project for 6.x-1.x, you will have to find out yourself it is working well enough for you. …

The entity_type of privatemsg is privatemg_message. Note that you are not required to specify this property as the purpose of it is to limit the field for certain entity types. …

Privatemsg and it's group of submodules rely heavily on dynamic queries and being able to alter them. That and the rather complex queries which can't be replaced by Views easily. …

Multi-site is just a way to share code. Different sites are completely separated and know nothing of each other*. There might be ways to theoretically do this using special recipient types, it would …

What I would do is define your own token. Start off with copying login_one_time_token_info() and login_one_time_tokens() into a custom module, change the hook names and rename the token to something …