Shortly after moving a website to another server *all* custom notifications are triggered and send, regardless of the conditions (like post type or status) are being met. This is of course very annoying and also interupts our workflow, because now it is not clear when to take action or not (people have to login to WP to see if there was actually an update for their case).
Do you have any idea how this could have happened? Could it be something on the new server? The plugin was not updated between the moment it worked correctly and this issue, so I’m not sure where to look. Thank you for your assistence!
PP Revisions is not installed, PP Statuses is though
I have 4 workflows set up and all 4 workflows are triggered when a post is updated in any way by a contributor (via a front-end form). See screenshots for an example: the conditions When to notify and For which content are both not met, but the log shows the notification was sent anyway.
@rizaardiyanto Thank you for this beta version! I just installed it and will let you know how it works out. I’ll have to wait until a contributor (a type of client on this website) will do an update before I can check if it resolved the issue, so it may take a day or two.
One contributor updated a post so here is a first update. The issue is partly solved.
The When to notify part is working correctly for now. But the For which content condition is not (always) respected. For instance, I have set up a workflow for When the content is updated with only one post type assigned (Bedrijven (Company)). But the notification is still send when another post type gets updated (Ondernemer (Vendor)).
Good to know: a Vendor post is set as the parent of a Company post. Maybe this information will help you look in the right direction.
Edit every notification on the website, confirm the settings are correct and then save each work flow again. Even if the settings are correct, you should still save them to trigger the meta key saving.
After that you should test again by creating or updating post belonging to another post type.
@rizaardiyanto There may be a new issue (which is probably not a real issue since it may only happen because of the existing issue). The notification send for the wrong post type now sometimes lacks a user (see screenshot). The notification send for the correct post type (updated by the same user) does show the user.
Please note that the post type here (Ondernemer) was not set in the workflow.
This issue did not occur before. Thought reporting this may help your investigation.
Upgrading to a paid plan for a plugin that doesn’t fully work correctly is not really an option I’m afraid (I’m also still experiencing other bugs I reported before).
Two other users commented on this topic with similar issues, but those comments were removed by a moderator stating that they should start their own topic. In this topic of a third user, notifications are also sent wrongly and a fourth user confirmed this.
Therefor I hope you can assist free users as well. Thank you!
Hi @ldwd. Sorry, this is as far as we’re able to debug this one for you on the free forums.
It looks like you use many of our plugins, which we appreciate. And we’ve answered over a dozen support threads for you here on the WordPress forums. But our free support can not solve everything.
@stevejburge I’m very sorry to hear that. The help of the PP team over the past 18 months has been much appreciated.
Your free support may not solve everything, though I do hope my help will solve one of the issues as I sent you detailed bug fixing in this topic. Would you please be willing to implement them until WordPress core has it’s own comments section? Thank you!
