Hi, maybe there’s the debug log and notification suppressing enabled in Notifications -> Settings -> Debugging?
I enabled it tried testing again. Error log is empty.
This is the notification log:
Notification
Source WordPress
Title event published to author
Hash notification_6176550fcea7e
Trigger CC Events published - post/cc-events/published
Carrier Email - email
Carrier data
subject
notification test
body
Hi, working?
recipients
Array
(
[0] => Array
(
[type] => email
[recipient] => {cc-events_author_user_email}
)
)
parsed_recipients
Array
(
[0] =>
)
I uninstalled the plugin then reinstalled it. When I did, I got this message:
Warning: Item in BracketSpace\Notification\Store\Trigger Store doesn’t exists. in /home/customer/www/commercecitynorth.com/public_html/wp-content/plugins/notification/src/ErrorHandler.php on line 39
But isn’t the Suppressing checkbox enabled? In this case, no email will be sent.
Also, when you uninstalled the plugin, you need to configure the triggers one more time in Notifications -> Settings -> Triggers. Just enable the CC Events post type and it should go back to normal.
I didn’t click on the suppress checkbox and I already did reconfigure the triggers for the custom post types.
I rolled back to version 7.24 and it is working again. Your plugin must have updated at about the same time I took my site off of staging. Seems like it was a pretty big update, are their any issues with me running 7.24?
I updated the plugin on my old staging site and it stopped working as well. I am happy to provide you with credentials to log in to the staging site if you would like to use it for troubleshooting.?
That would be awesome! Could you email us via the contact form?
Feel free to do whatever you want, I saved a backup.
Thanks! Before I even logged in I found out a bug in the new release and I’m working on the fix now. The update will be available within a few hours.
New version 8.0.1 should resolve that issue already. Can you confirm @sugarweb it’s still a case when you update?
We are busy trying it, thank you. We’re also using the Scheduled Triggers add-on, which seems to be the more serious error message. But will confirm asap.
