• I use GF + Gravity Forms Post Updates to publish and update posts in the frontend in conjunction with Better Notifications for WordPress to send notifications to the admin and user when a post is published or updated.

    This is the ideal workflow:

    1. The User (logged in) submits a GF form which is published as a post
    2. A “new post published” notification is sent to the admin and to the user
    3. The admin makes an edit to the post using Gravity Forms: Post Updates
    4. A notification is sent to the user that their post has been updated

    The problem is that when a post is updated using Gravity Forms: Post Updates, the post_status is first changed from <i>publish</i> to draft and then from <i>draft</i> to <i>publish</i>. The draft->publish change triggers the “new post” notification to be sent instead of the “post updated” notification.

    Is there a way to prevent the post_status change when a post is updated with Gravity Forms: Post Updates?

    This question might be related: Retain Published status on update?

    Thanks!

Viewing 1 replies (of 1 total)
  • Thread Starter KostasNi

    (@kostasni)

    The problem ended up being not with this plugin or the Better Notifications for WordPress plugin, but with the way Gravity Forms handles the post creation/update.

    If anyone else runs into this problem, I’ve added some more details in this thread.

Viewing 1 replies (of 1 total)
  • The topic ‘Unwanted Post Status change on update’ is closed to new replies.