Reciepts no longer being captured as Activities

Question

Reciepts no longer being captured as Activities

Closed this issue 2 years ago · 9 comments

We've enjoyed the features afforded by this extension for a while and it had been working quite well. A few months back, we upgraded our PHP version to PHP 7.3 from 7.2 and since that upgrade, the receipts are no longer being captures as activities. This may not be an issue per se, but any suggestions on debugging this situation would be helpful.

petednz commented 2 years ago

Thx 2mice

Answer 1 · 2022-02-02T00:53:08.000Z

Hi @einsty we run this extension on a number of sites the majority on PHP 7.3 so hopefully that's not the issue!

It would help if you could indicate which version of the code (CiviCRM + extension) you are using - has that changed in the same period you noticed the reciepts not working - and can you try triggering the workflow to generate a receipt where you would expect it to generate an activity - and just check in your relevant logs (CiviCRM and CMS) to double check that there are no errors being thrown up.

Answer 2 · 2022-02-02T21:23:21.000Z

I think i just identified this on a site, dating back to Oct 8 2021 - will have to do some digging soon.

Answer 3 · 2022-02-02T21:53:07.000Z

Thanks @petednz. I have not yet had a chance to debug, but will try as soon as possible also.

…

On Wed, Feb 2, 2022 at 3:23 PM petednz ***@***.***> wrote: I think i just identified this on a site, dating back to Oct 8 2021 - will have to do some digging soon. — Reply to this email directly, view it on GitHub <#58 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALYJZWWLMARPJXWMBGIDMDUZGOFJANCNFSM5NKPA25Q> . You are receiving this because you were mentioned.Message ID: <fuzionnz/nz .***@***.***>

-- *Orin Fink, managing partner* *P* 312.340.6503 | *C *312.933.3433 | *F* 312.329.1963 15 West Hubbard Street, Suite 300 | Chicago, IL 60654

Answer 4 · 2022-02-05T10:11:17.000Z

@einsty Can you pls confirm if #59 fixes the problem?

Answer 5 · 2022-02-20T15:59:14.000Z

I've mad the changes in that PR directly, will report back on if it resolves the problem after a few cycles.

…

On Sat, Feb 5, 2022 at 4:11 AM Jitendra Purohit ***@***.***> wrote: @einsty <https://github.com/einsty> Can you pls confirm if #59 <#59> fixes the problem? — Reply to this email directly, view it on GitHub <#58 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALYJZUFHEOMAZATMWZSORLUZTZVBANCNFSM5NKPA25Q> . You are receiving this because you were mentioned.Message ID: <fuzionnz/nz .***@***.***>

-- *Orin Fink, managing partner* *P* 312.340.6503 | *C *312.933.3433 | *F* 312.329.1963 15 West Hubbard Street, Suite 300 | Chicago, IL 60654

Answer 6 · 2022-05-03T02:58:02.000Z

@einsty any comments yet?

Answer 7 · 2022-05-03T03:54:59.000Z

Oh my, thanks for the prompt. Yes, it seems that it had resolved the issue!

On Mon, May 2, 2022 at 9:58 PM petednz ***@***.***> wrote: @einsty <https://github.com/einsty> any comments yet? — Reply to this email directly, view it on GitHub <#58 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALYJZVROFCLLUV2BJRQOUTVICI4JANCNFSM5NKPA25Q> . You are receiving this because you were mentioned.Message ID: <fuzionnz/nz .***@***.***>

-- *Orin Fink, managing partner* *P* 312.340.6503 | *C *312.933.3433 | *F* 312.329.1963 15 West Hubbard Street, Suite 300 | Chicago, IL 60654

Answer 8 · 2022-12-15T01:15:46.000Z

Recommend closing: OP reports a successful fix, and PR was merged.