Bug #8023
closedReply to CAC Message gets posted to forum
0%
Description
Hi All,
A confusing situation:
- I was trying to troubleshoot something with a CAC user, so I sent her a message through the Commons by visiting the CAC and replying through the CAC messaging interface
- She replied and I received an email notification of her reply
- I replied to her message by hitting "reply" from my email client (Gmail web)
- I received a notification that seemed to indicate that my reply had been posted to the CUNY Digital Humanities Initiative as a forum post
- It looks like my email reply was posted as a comment on a forum thread that I had started this morning -- https://commons.gc.cuny.edu/groups/digital-humanities-initiative/forum/topic/fwd-digital-humanities-at-the-community-college-in-the-us-please-respond-to-our-survey/#post-54970
screenshots attached
Files
Updated by Raymond Hoh over 7 years ago
Hi Matt,
Sorry to hear about this.
Can you take a screenshot of the email headers from the initial email from Marilyn? I want to see the Reply-to email header for that email and compare it to the first two screenshots you took.
Updated by Matt Gold over 7 years ago
- File original_msg (10).txt original_msg (10).txt added
thanks, Ray. Please let me know whether this gives you what you need
Updated by Raymond Hoh over 7 years ago
Thanks Matt.
I'm still looking into this. Somewhere along the process, the unique querystring used in the Reply-To email header is being hijacked by bbPress, instead of the one associated with private messages.
I'm going to try to duplicate this locally and will report back.
Updated by Raymond Hoh over 7 years ago
- Status changed from Assigned to Resolved
- Target version set to 1.10.18
Fixed in https://github.com/cuny-academic-commons/cac/commit/d7850af7456cf9e8e7604f8126c80c629488c630
The issue was with the RBE module written for bbPress and the BP Group Email Subscription (GES) plugin, and with the recent auto-connect option written for IMAP mode.
Long story short, the GES RBE code was stamping on other RBE modules. Fix is deployed on production.
Side note: Boone, I'm having problems using git on the production server.
I tried using git fetch origin on production, but got the following:
error: cannot open .git/FETCH_HEAD: Permission denied
I had similar troubles when performing git operations in the development directory as well. Is this due to the changes made to the git repo?
Updated by Boone Gorges over 7 years ago
Yeah - I manually moved some .git directories around and I neglected to check file permissions. I just made the .git dir group-writable. Can you try again?