Strothi

@isaumya,

well, nothing other than what I already showed you. I set WP to debug mode, plus switched on the log on the server side, but nothing appears in the logs.

If you tell me what exactly you’d like to see, I am happy to provide screencasts for you.

I don’t have Cloudflare set up for my dev environment, so I can’t replicate the issue there. I guess you have it running on your environment? Would you mind checking if the error appears also on your end when using Buddypress?

Kind regards, Philip

Dear @isaumya,

Well, somehow the plugin does seem to affect the function here because I don’t even need to disable it to get the function working again, simply deactivating caching in your plugin’s settings does the trick!

Which however renders it useless, so it would be great if we could figure out, what’s causing the issue ??

Kind regards, Philip

Dear @isaumya,

it literally just says: “The link you followed has expired.</p><p>Please try again.”

Kind regards, Philip

Dear @isaumya,

Thanks for getting back to me. I tried disabling the JSON API endpoint as part of my initial debugging, but it didn’t do anything.

I’m not sure what you would like me to post from the network tab. The response is 403, as outlined above.

If you are interested in the headers data, you can check out a screenshot here: https://www.evernote.com/l/AAKv0e1JA7xP6qbA_ODe2X7El95vJ4DIInsB/image.png

Kind regards, Philip

Dear @bindlegirl,

thanks for your suggestion. So, I have run multiple tests on my website and the issue is quite strange, as it seems to just appear when I set the number of jobs to 3! As you can see here, the widget shows different data depending on the number of jobs it is set to show: https://fslci.org/jobs/ (sidebar & footer)

I deactivated ALL plugins except for WP Jobs Manager and the weird behavior remains. I thought it might indeed be a strange caching issue, but I cleared the cache in the backend multiple times, checked with different browsers and yet, nothing changes.

Any idea what might cause this issue or what I still could test?

Kind regards, Philip

Dear @boonebgorges,

I forgot to report back last week, but all is fine now! ??

Have a great Easter!

Kind regards, Philip

Dear @yehudah, @tneville,

is this plugin still supported? If so, I would highly appreciate if you could help me solve the visible handshake issue described above!

Thanks a lot in advance.

Kind regards, Philip

Dear @boonebgorges,

I think that was the solution. I just sent out a test notification and while I blocked the smtp send out to not spam my members, all logs look good! I don’t have an error anymore on the server side and the BPGES log says that the correct amount of emails was successfully send out! I’ll report back on Thursday when my actual mailing goes out, but it looks like the issue is solved ??

Thank you SO MUCH!

Have a great day.

Kind regards, Philip

Dear @boonebgorges,

thanks for your answer. So to test the issue, I sent out an admin notification to one group with 196 users today and 113 mails were sent. The bpges debug log just says:

[17-Mar-2021 17:50:55] Beginning batch of immediate notifications for 7838.

The server log says the following:

[Wed Mar 17 18:51:47.205984 2021] [fcgid:warn] [pid 25803:tid 139710261266176] (32)Broken pipe: [client 141.101.69.43:41064] mod_fcgid: ap_pass_brigade failed in handle_request_ipc function
[Wed Mar 17 18:51:48.505551 2021] [fcgid:warn] [pid 25803:tid 139710303229696] (32)Broken pipe: [client 162.158.158.237:13252] mod_fcgid: ap_pass_brigade failed in handle_request_ipc function
[Wed Mar 17 18:51:53.759707 2021] [fcgid:warn] [pid 26531:tid 139710244480768] [client 141.101.96.37:36192] mod_fcgid: read data timeout in 60 seconds, referer: https://domain.org/wp-admin/admin-ajax.php?action=wp_bpges_send_queue&nonce=7babbcaf9f
[Wed Mar 17 18:51:53.759748 2021] [core:error] [pid 26531:tid 139710244480768] [client 141.101.96.37:36192] End of script output before headers: admin-ajax.php, referer: https://domain.org/wp-admin/admin-ajax.php?action=wp_bpges_send_queue&nonce=7babbcaf9f

So something is causing a core error ??

Please note: For some reason BP GES always is 1 hour off the actual time, hence the 1 hour difference between the two logs.

Kind regards, Philip

• This reply was modified 4 years ago by Strothi.

Dear @boonebgorges, dear @r-a-y,

I hope I find you well. I would truly appreciate if you could help me with this issue. As outlined above, I’m also happy to donate to the plugin development in return for assistance with the matter ??

Kind regards, Philip

Dear @boonebgorges,

I hope you had a good weekend. Any idea on how to further debug and address my issue?

Kind regards, Philip

Hi @yehudah,

I hope I find you well. Could you be so kind and let me know how I at least could address issue b)? That would be great ??

Thanks a lot in advance.

Kind regards, Philip

Dear @boonebgorges,

so, the issue is still present ?? I just tried to send out the weekly digest to our 651 users and only 95 mails went out. The log from BP GES says the following:

[04-Mar-2021 12:46:45] Beginning batch of immediate notifications for 7761.
[04-Mar-2021 12:46:45] Finished sending immediate notifications for 7761. A total of 0 notifications were sent over all batches.
[04-Mar-2021 14:45:18] Beginning batch of immediate notifications for 7762.
[04-Mar-2021 14:45:18] Finished sending immediate notifications for 7762. A total of 2 notifications were sent over all batches.
[04-Mar-2021 15:18:03] Beginning batch of immediate notifications for 7763.
[04-Mar-2021 15:18:03] Finished sending immediate notifications for 7763. A total of 0 notifications were sent over all batches.
[04-Mar-2021 17:00:07] Beginning digest batch of type dig for timestamp 2021-03-04 17:00:04.
[04-Mar-2021 17:00:08] Finished digest run of type dig for timestamp 2021-03-04 17:00:04. Digests were sent to a total of 95 users.
[04-Mar-2021 17:00:09] Beginning digest batch of type dig for timestamp 2021-03-04 17:00:08.
[04-Mar-2021 17:00:10] Finished digest run of type dig for timestamp 2021-03-04 17:00:08. Digests were sent to a total of 95 users.
[04-Mar-2021 17:00:12] Beginning digest batch of type sum for timestamp 2021-03-04 17:00:10.

I can see that in the queue I have the remaining 556 entries ??

So essentially BP GES does not process any batches after the first one is sent. Even though the log appears to indicate that 2 batches were processed – unless I’m reading it wrong?

I also don’t have any errors in debug.log so I’m not sure why it’s not working. To recap, I’m using the following combination:

BP GES -> CronJob Scheduler -> Post SMTP Mailer -> Mailersend

I can see that Mailersend just sends out the first batch.

Any ideas what I can do to debug the issue?

Kind regards, Philip

@iberezansky Ah, I just realized what the issue might be. Ok, thanks ?? I’ll test and report back!

• This reply was modified 4 years ago by Strothi.

Dear @boonebgorges,

I noticed that I could stop the sending of emails on the SMTP server side, so I tested again what happened with my two groups and debugging for BP GES on:

[26-Feb-2021 16:52:38] Finished sending immediate notifications for 7731. A total of 3 notifications were sent over all batches.
[26-Feb-2021 17:00:16] Beginning digest batch of type dig for timestamp 2021-02-26 17:00:15.
[26-Feb-2021 17:00:17] Finished digest run of type dig for timestamp 2021-02-26 17:00:15. Digests were sent to a total of 95 users.
[26-Feb-2021 17:00:18] Beginning digest batch of type dig for timestamp 2021-02-26 17:00:17.
[26-Feb-2021 17:00:19] Finished digest run of type dig for timestamp 2021-02-26 17:00:17. Digests were sent to a total of 95 users.

So now it looks like the processing is working fine and I’m even more confused than before. The 95×2 equal the 190 members in the group. I did send out a final test message this afternoon and for that I also have no items in wp_bpges_queued_items – suggesting to me that that should have worked, if not for my SMTP server being set to not send out any mails.

I’ll investigate this further when I send out another round of emails to my users…

Kind regards, Philip

• This reply was modified 4 years ago by Strothi.