This is the only part of your post I don't understand; other than that your terminology is OK. What do you mean by "IP check?"CarolC1 wrote: Thu Mar 09, 2023 3:13 am I sent the server people a question about whether there's a new IP check or something like that, but have not heard back.
Yes, something like that. Maybe some kind of new server security they activated after the server was getting hit repeatedly. I don't know enough about it to make an educated guess or ask them intelligent questions.Mick wrote: Thu Mar 09, 2023 9:19 am Maybe meaning something like Spamhaus or other similar blacklist checker?
Thanks for your reply. I tried testing it. I went to the db and made sure nobody was subscribed to the Test Forum. Then I went to Test Forum and posted. The first post submitted immediately. I posted a reply and it took forever. Posted another reply, which also took forever. Logged in with a second account and posted another reply. Still took forever.Brf wrote: Thu Mar 09, 2023 2:43 pm Usually, that type of posting-hang is due to bad email addresses in post notifications where someone has subscribed to a forum or popular topic.
Good tip! If so, setting "Email package size" to non-zero in the ACP > Email settings would queue up email notifications instead of sending them synchronously. It won't eliminate the delay due to bad emails addresses, but it'd at least move it to the cron background task and off the page response.Brf wrote: Thu Mar 09, 2023 2:43 pm Usually, that type of posting-hang is due to bad email addresses in post notifications where someone has subscribed to a forum or popular topic.
Code: Select all
SELECT COUNT(*) as notification_count FROM phpbb3_notifications GROUP BY item_id ORDER BY notification_count DESC;
If you haven't changed anything to cause this problem then that usually means your host has. You should check with them, maybe they changed your PHP version without telling you? Also, you should inform the extension author in Prime Notify support, I'm sure he'd like to know .