Tagging messages on view thread page doesn't work with a %user url prefix

None of it? I assume you mean adding a tag to a newly created message? Ok. what about when I add a tag to the message after it is created? That tag still doesn't show up anywhere. I can't get a tag to show in the tags column nor can I filter by a tag.

1. Added a public tag "giver" in configuration
2. Create mail, open message, add tag in the tag field box, save (screenshot attached)
3. Rebuild tags from configuration
4. Go back and view inbox, not tags are showing under column heading "tags", (Screenshot attached)

I finally noticed the action box at the bottom of the message list, i inserted the tag there and clicked "apply". It now works. I'm not certain why you're not allowing to tag message at creation. (although, i'm not a programmer and do not know what is involved). What I am certain of is....this feature takes a whole lot more work and confusion for the pay off, unless I am missing something?

This may be an obvious "no" but is there any way to automatically assign a tag value to the field on creation...like through the url, prepopulate, default value, etc?

Thanks for your quick responses, I appreciate it.

Ok, I changed the path to "messages" for all mail instead of individual users. The tagging works ok now.(would be interested in knowing the applicable way to use this since cant assign at creation. Also wonder why tabs column isn't sortable?)

After changing to messages as url path, the inbox is not working. Then I ran update, still not working. Now when a message is sent, there's no indicator in messages that a new message has arrived. Also when I click on the message tab from user account page, no sub tabs (inbox, all messages, sent, new, etc) are showing. just a list of all messages from url /messages/list. Once I open the message, then the sub tabs show but when I click on inbox I get a white screen which says access forbidden.

I went to backend to look at the folder "messages", it has the following permissions

drwxr-xr-x

I meant *tags column

Ok, the message folder on backend (which I had created when initially installing this module because I couldn't get it to work (running update solved)) is now gone and everything works fine.

So with tags, when I tag an email it's simply for my personal viewing, just as if I were to receive an email and stick it in some other folder on my computer? Got it. which certainly explains not doing it at creation.

But you're saying with rules I can tag the message as it is sent? Basically here's what I'm trying to do. When a user sends a message to another user, from a node, I want it to be tagged, labeled, taxonomy vocabulary, etc. with a specific admin defined label. The user won't have an option here. It will just show up in their sort list, labeled. These messages will be specific messages identifiable to be separate from others. The reasoning is, these messages will be more urgent and we need to identify them as such. I thought you said I wasn't able to populate any other fields except recipient and subject, but you're saying through rules (which I understand is different than populating) that I can assign some type of label, tag, etc.?

Thanks again for your promptness.

This should work fine. I think I can assign a certain value to the subject field(via url or prepopulate mod) and then fire a rule when that condition is met....kind of what you just said :) And I believe I can hide the subject field through url fill module or autonode title module. This would prevent the user from changing it upon creation. I will look at your documentation from the references above. Alot of this will also be simpler in version 7. Which I plan to upgrade to very soon. I appreciate your quick help.

From comment #6 this is still an issue...no sub tabs and no new message indicator. the path is different now because I fixed the path.

"Now when a message is sent, there's no indicator in messages that a new message has arrived. Also when I click on the message tab from user account page, no sub tabs (inbox, all messages, sent, new, etc) are showing. just a list of all messages from url /messages/list. Once I open the message, then the sub tabs show "

Go ya...so, if I do not hear back from you, I will assume the following. You're saying, there is not a tab on the account page of regular role users. There is simply a menu link showing messages and once the user clicks on that link, then they see the different boxes - inbox, sent messages, etc.

I'm moving this to "needs work" for the initial url issue. Thanks

Since I am only using tagging to apply tags to certain messages which meet certain conditons via rules, I went to permissions and disabled "tag private messages" for all users except admin. This way, the tags would only be applied via rules. And no user would be bale to apply any tag via thread or message...cool. Except, now that I have disabled tagging ability for these users, the tag field no longer appears on their column headings. This is tw completely different options in my opinion. Viewing tags is not creating or assigning tags. Two options, two different uses. How would I allow them to view, but not create tags?

Thanks

I will open the feature request now, but shouldn't this be considered a bug at the moment because it is disabling the ability to "view" tags when I disable their ability to "create" them? Or, is this the typical process? I'm not up to the standard "flow" procedures of updating these status levels on the tickets here....but I'm learning :)

I tested this patch (by the way...putty works excellent and very simple for patching...it makes it very obvious as to how to connect with your website from your computer). The patch works. However, since I switched the messages folder from "messages" to the user's folders my custom link I made for certain node types is not working. (cant use yours because I have panels and I need to autopopulate the subject field. I've been using this url in order to open new window for a new message

../messages/new/1/

that url no longer works after changing the folder name. This makes sense considering I changed the path...but now I do not know which url to use in order to populate a new messages window?

Also...I didn't understand the "test" part of the patch? Where/What do I test?

Per your reference in comment #11 regarding disabling recipient field if it contains default info - instead of creating a module, can I simply use the php code in the same custom block I created, with the link i'm using to insert default values? My concern is, If I create a custom module...it's only good until I upgrade and forget it's in the old module folder.

Disregard question on #22...I now see I can put custom module in folder of its own. Although, when I upgrade to version 7 in core I expect I will need to alter the module file to indicate such.

I can't get your code to work for hiding the recipient field....here's what I am using;

function customsite_form_privatemsg_new_alter(&$form, &$form_state) {
  // Check if a default value is configured for the to field.
  if (!empty($form['recipient']['#default_value'])) {
 
    // Display a visible markup element.
    $form['recipient_display'] = array(
      '#value' => t('To: @recipients', array('@recipients' => $form['recipient']['#default_value'])),
      '#weight' => -10,
    );

    // Convert the recipient field to a value type and force the default value.
    $form['recipient']['#type'] = 'value';
    $form['recipient']['#value'] = $form['recipient']['#default_value'];
  }
}

I removed all the ['privatemsg'] fields like you suggest. I've also played around with the first line and changed it to;

function_customsite
function_customsite()
function(), etc.

Any advice?

I forgot to add....as soon as I add your code to the .module file I get the white screen of death on my site

I will work on these...thank you.

Per #21...why isn't mysite.com/messages/new opening a default new message window? I've seen a lot of documentation that makes me believe that is a standard url for doing so? It worked for me until I changed the url path for default messages to user/%user

I was finally able to get the code above to work. I was inserting the first <? php tag thinking it had to be on the first line of new code...but then figured out you mean first line of entire file....only.

I'm unable to get the code above to work for the subject field because I'm not sure how to change this part

// Display a visible markup element.
$form['recipient_display'] = array(
'#value' => t('To: @recipients', array('@recipients' => $form['recipient']['#default_value'])),
'#weight' => -10,

It's like you have some @ email stuff going on that would not apply to the subject filed? I've gotta think it can't be as simple as replacing the word(s) recipient(s) with subject(s) for this particular area?

I tried removing this section and simply doing an "if there's no default subject, then block it out" but it wouldn't work. I was able to remove the "if" conditoner and block out the subject simply by using the bottom part of the code....but that won't help me when someone tries to write a message where there is no default subject....because it hides the field at creation.

Ok...I will work on this.

Still having an issue with #21 and 27....My url of ../messages/new doesn't work anymore. While i'm at it. What is the real advantage of having it in a user's folder anyway? Will it help on sorting or load speed? If there are millions of private messages being sent back and fourth will it help? If not I will just switch it back and let all of the PM's go to path

I can't get the subject code to work(recipient works fine)....I tried adding the function line in again, above the subject code. Wasn't sure if that particular line needed to be there....still didn't work. I also tried to remove the upper code pertaining to recipient and only leave in subject field code...still didn't work. Here is what I have. I will copy this over to your documentation page when I get it corrected.

<?php
// $Id: customsite.module

/**
* @file
* Custom functions for this site.
*/
function customsite_form_privatemsg_new_alter(&$form, &$form_state) {

// Check if a default value is configured for the to field.
if (!empty($form['recipient']['#default_value'])) {

// Display a visible markup element.
$form['recipient_display'] = array(
'#value' => t('To: @recipients', array('@recipients' => $form['recipient']['#default_value'])),
'#weight' => -10,
);

// Convert the recipient field to a value type and force the default value.
$form['recipient']['#type'] = 'value';
$form['recipient']['#value'] = $form['recipient']['#default_value'];

}

// Check if a default value is configured for the subject field.
if (!empty($form['subject']['#default_value'])) {

// Display a visible markup element.
$form['subject_display'] = array(
'#value' => t('Sub: @subject', array('@subject' => $form['subject']['#default_value'])),
'#weight' => -10,
);

// Convert the subject field to a value type and force the default value.
$form['subject']['#type'] = 'value';
$form['subject']['#value'] = $form['subject']['#default_value'];

}
}

Didn't really understand your htlm comments...I dont mind it being on same line at creation, or even if it shows at all, for that matter.

Evidently, when I attempt to prepopulate your form using prepopulate module's url code;.../?edit[recipient]=user1, it gets in the way of this code....i know this because;
1. it doesn't populate the node author instead it defaults to user1. It does, however, make the to: field uneditable.
2. It does nothing with the subject field

To test, I inserted this url ../messages/new/1/testsubject

the code did work this time, but it gave me this

To:user[user] Sub:testsubject

I went ahead and sent the email....and while it wasn't pretty at creation, it was fine afterwards. Here are a few questions
1. Will this code work with prepopulate? I have php code running to figure out what the title field of the current node is...remember yours doesn't work because im coming from a node panel.
2. If your code wont work with prepopulate...do I need to care about the [user] appended at the end of recipient field? It's ugly but is it effecting me?