Project

General

Profile

Bug #8023

Reply to CAC Message gets posted to forum

Added by Matt Gold about 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority name:
High
Assignee:
Category name:
Reply By Email
Target version:
Start date:
2017-04-25
Due date:
% Done:

0%

Estimated time:

Description

Hi All,

A confusing situation:

screenshots attached

History

#1 Updated by Matt Gold about 2 years ago

  • Priority name changed from Normal to High

#2 Updated by Raymond Hoh about 2 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.

#3 Updated by Matt Gold about 2 years ago

thanks, Ray. Please let me know whether this gives you what you need

#4 Updated by Raymond Hoh about 2 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.

#5 Updated by Matt Gold about 2 years ago

Okay -- thanks for your work on this, Ray

#6 Updated by Raymond Hoh about 2 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?

#7 Updated by Boone Gorges about 2 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?

#8 Updated by Raymond Hoh about 2 years ago

Can you try again?

That did it. Thanks!

Also available in: Atom PDF