PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Gravity Forms Custom Post Type Submissions Plus Edit Flow

  1. I have a site at http://theurbandater.com/guest-post - that form is used for people to submit content to the site. When submitted it creates a post and I can assign a default status. That works great. =)

    I'm using it conjunction with a plugin called 'Edit Flow'. But I have an issue choosing a default status in the GF Form editor area.

    The problem is that in Gravity Forms I can only choose draft, pending review, publish. The custom statuses generated by Edit Flow are not selectable. I'm not sure where the issue is, but I'm posting here and then on the other plugin vendor's site, too.

    Posted 11 years ago on Tuesday December 11, 2012 | Permalink
  2. David Peralty

    The reason they are not selectable is because Edit Flow doesn't store those statuses in regular WordPress, but instead in their own function that Gravity Forms would have no idea about... You would have to find out how to access their statuses with PHP and then create a dropdown with those selections and then when the post is created, update the post status with the custom status selected. And you'd have to write similar PHP to access it in the backend as well.

    At least that's my assumption from a cursory glance.

    Posted 11 years ago on Tuesday December 11, 2012 | Permalink
  3. Cool. I'll pass on the info and see what comes of it.

    Posted 11 years ago on Wednesday December 12, 2012 | Permalink
  4. For reference, I'm including a link to the other conversation here: http://wordpress.org/support/topic/custom-post-status-and-gravity-forms?replies=2

    Posted 11 years ago on Wednesday December 12, 2012 | Permalink
  5. According to the developer:

    Clarification: Edit Flow registers each custom status using core's (incomplete) custom status API, so if you use get_post_stati(), a list of all custom statuses should be produced.

    So my assumption is that Gravity Forms isn't calling to WordPress with the same function to query statuses. Does that sound right?

    Posted 11 years ago on Wednesday December 12, 2012 | Permalink
  6. David Peralty

    I will pass this on to our developers to look at and answer. All my best!

    Posted 11 years ago on Wednesday December 12, 2012 | Permalink
  7. You are right, Gravity Forms currently only supports the built-in post statuses. Using the get_post_stati() seems like a good idea and I will talk to the team and see if that is something we can include in the next version.

    Posted 11 years ago on Wednesday December 12, 2012 | Permalink
  8. Cool! You guys most definitely rock! =)

    Posted 11 years ago on Wednesday December 12, 2012 | Permalink
  9. Just circling back on this to see when you guys might think of implementing, if at all. =)

    Cheers!

    Posted 11 years ago on Thursday January 10, 2013 | Permalink
  10. I'll forward your question to Alex. Thanks for checking back.

    Posted 11 years ago on Friday January 11, 2013 | Permalink
  11. We looked into it, but decided not to implement it for two reasons.
    1- The get_post_stati() function returns all possible statuses and a lot of them don't really make sense to be an option when creating the post. They would confuse most users.
    2- WordPress doesn't use that function in the post edit screen. They actually hardcode a few post status (similar to how Gravity Form does).

    What we decided to do is include a Gravity Forms filter that will allow you do add post statuses to the list when needed. This filter will be available in GF 1.7

    Posted 11 years ago on Friday January 11, 2013 | Permalink
  12. Alex,
    Thanks for the awesome reply. That makes a lot of sense. I'll convey your reasoning to the Edit Flow peeps.

    Thanks again for the reply. =)

    Posted 11 years ago on Tuesday January 15, 2013 | Permalink

This topic has been resolved and has been closed to new replies.