Hi,

Thanks for your tremendous effort on this incredibly useful module. I'm running into this problem and do not know where to begin to access what's wrong. I've been experiencing this issue since a few release candidates ago. Essentially, almost every third or fourth initial message sent by user shows up blank.

Thanks for your help,

Thomas

CommentFileSizeAuthor
#2 Screen shot 2009-12-01 at 4.51.19 PM.png29.1 KBpribeh

Comments

berdir’s picture

Status: Active » Postponed (maintainer needs more info)

Please provide more information.

- Version of PHP/MySQL

- Which theme are you using? (Try to reproduce this with an official theme like Garland)

- Please provide some screenshots and/or, save the broken page including CSS and Images and upload it as a zip file. (With firefox, choose Save as ... Website, complete)

- Is the message always blank or does it show sometimes and sometimes not?

- Remember the thread_id of a message that is broken (visible in the URL, for example, /messages/view/{thread_id}) and then check in your database, table pm_message if the text is saved (thread id is the same as the mid field of that table, SQL to select it is "SELECT * FROM pm_message WHERE mid = {insert_thread_id}"

- Any special character encoding involved (things like arabic, chinese and so on)?

Provide as much information about the points above (you don't need to provide everything but the more, the better) as you can.

pribeh’s picture

Status: Postponed (maintainer needs more info) » Active
StatusFileSize
new29.1 KB

Hi Berdir,

You can find out the php info by going to http://www.londonfuse.ca/infoya.php

The initial message sent sometimes contains text sometimes not. But the text in the message only ever disappears within the initially sent message. I've never seen this in subsequent messages (responses) within the same thread.

I'm not using any special characters. I've checked this on different themes. The text within the div "message-body" just doesn't seem to load or exist. I've also attached an image.

I will see if I can get help checking at the database.

Thanks for taking the time to help.

berdir’s picture

Status: Active » Postponed (maintainer needs more info)

Can't see any unusual about your php version.

What modules are you using that interact with Privatemsg? If you have any, disable them one be one and try to reproduce the bug.

If the message body is not stored in your database, you can put the following hooks into a module (any module works as long as you change modulename to the actual module name) and update the author uid if necessary. They should display the value of the message body during validation, before and after save. (untested)

function modulename_privatemsg_message_insert($message) {
  if ($message['author']->uid == 1) {
    drupal_set_message('Body after saving: ' . $message['body']); 
  }
}

function modulename_privatemsg_message_presave_alter($message) {
  if ($message['author']->uid == 1) {
    drupal_set_message('Body before saving: ' . $message['body']); 
  }
}

function modulename_privatemsg_message_validate($message) {
  if ($message['author']->uid == 1) {
    drupal_set_message('Body during validation: ' . $message['body']); 
  }
}

It might be best to put this in a module with a high weight (weight column in system table, you can also choose a module name that starts with z or another character at the end of the alphabet) so that those hooks are executed after all other modules.

Then post messages until the bug happens and if he does, post the output of those messages here. That should help to detect at which point the body gets lost.

berdir’s picture

Status: Postponed (maintainer needs more info) » Closed (won't fix)

Sorry, without further information this issue can only be marked as won't fix.

Feel free to re-open this issue if you want to provide further information. Thanks.

This message is automatically generated. If you feel it could be improved, feel free to comment on http://drupal.org/node/467548

pribeh’s picture

Sorry for not updating this. You can mark this as fixed. I just discovered a couple days ago that this was somehow being caused by using the yui editor. I've since switched to using tinymce with the wysiwyg module and have yet to exerience the bug.