While trying to "Send private message" to Trusted contacts getting the error messages.

Error private message

CommentFileSizeAuthor
private_message_error.png69.16 KBneerajskydiver

Comments

ezra-g’s picture

ezra-g commented
Priority: Normal » Major
Issue tags: +Commons 7.x-3.4 radar

Sorry to hear that you're having trouble here. Adding to our 3.4 radar for triage.

ezra-g’s picture

ezra-g commented
Status: Active » Postponed (maintainer needs more info)

I'm not able to reproduce this on a fresh install of Commons 3.3, even using the same demo user accounts shown in your screenshots.

Can you share specific steps to reproduce the problem?

neerajskydiver’s picture

neerajskydiver commented

Tried again with latest copy of Commons 3.3

After installing changed the username and password of two demo account. Did this to login to both account for approving contact request. After approving trusted contact request (list of invitation) tried "Send private message" from "Private Messages & Invitations > Trusted Contacts" tab. Got the same error.

After receiving your comments, i thought this error is coming because username (real name remains same) has been changed. In fact if you change the username, user is removed from trusted contact list also.

Created two new set of users. Added one user as trusted contact for other user. Tried sending private message again. Reached same error page. Both user is receiving notification emails from system about "trusted-contact request pending" as well as about new post created.

Tries the same steps with latest dev copy also. No luck.

garyconroy’s picture

garyconroy commented

I'm seeing the same issue on a clean install of 3.3 and a newly set up user.

ezra-g’s picture

ezra-g commented

Can someone who can reproduce this please post detailed, numbered steps to reproduce?

garyconroy’s picture

garyconroy commented
  1. New install of 3.3 (Acquia Cloud)
  2. Disable un-needed modules: Commons Social Sharing, ShareThis
  3. Install/enable required modules: Commons Documents, Media, File Entity, CK Editor Link, CK Editor Link Users, User Import, User Import Delete, Countries, Countries Configuration, Calendar
  4. Set private file system path
  5. Set Mollom protection for forms
  6. Set Authenticated user permissions for Private messaging to allow 'Read private messages', 'Write new private messages', 'Delete private messages'
  7. Create test accounts: Octavius Frederick and Finbarr Taylor
  8. Log in as Finbarr, find Octavius' profile and add him as a trusted contact
  9. Log in as Octavius, click the approval notification option in the heading and approve Finbarr.
  10. Click the 'Trusted Contacts' tab and click 'Send private message' next to Finbarr
  11. Enter a message and click send
  12. Error message displayed "The following users will not receive this private message: Finbarr Taylor [user]. You must include at least one valid recipient."
  13. Message is not sent.
ezra-g’s picture

ezra-g commented
Status: Postponed (maintainer needs more info) » Active

Thanks for those steps, garyconroy! Setting back to "active".

japerry’s picture

japerry
Location KOMK
commented
Assigned: Unassigned » japerry

I've been taking a look at this, and can also reproduce.

jmesweeney’s picture

jmesweeney commented

Try enabling the "Privatemsg Realname Integration module". https://drupal.org/node/1292874

garyconroy’s picture

garyconroy commented

This fixed the issue for me.

japerry’s picture

japerry
Location KOMK
commented
Status: Active » Fixed

Yup same here. By default the content we create has the username = realname. But if someone creates a username that is different than the real name, it fails. It seems like this was just a simple oversight. I've added it to the commons install profile.

http://drupalcode.org/project/commons.git/commit/28866c7

japerry’s picture

japerry
Location KOMK
commented

A quick follow up here, we should be doing this in the privatemsg module instead:
https://drupal.org/node/2077223#comment-7807667

I've committed the patch to the make file, and reverted our update.
http://drupalcode.org/project/commons.git/commit/a7c431d

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

raushan’s picture

raushan commented

Thanks for detail reply.