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.

Custom Standard Fields / More Fields

  1. Is there a possibility to have the standard field types (dropdown, radio, checkbox, etc) applied into / within a custom field type? For "WP-as-a-CMS" use case scenarios, using Gravity Forms as a basic data entry tool for non-authors would be fantastic.

    For authors, I've been using the More Fields plugin (http://wordpress.org/extend/plugins/more-fields/) to customize the admin console for a similar effect. Although the support for it leaves something to be desired. The concept it has implemented of using custom fields to create custom data types and post types in the admin console is fantastic.

    I know that enhancing custom fields and post types are on the radar for a future WP core functionality. It would be great if Gravity Forms could be looked at as strong references on how to implement that type of functionality.

    Posted 9 years ago on Thursday September 10, 2009 | Permalink
  2. We plan on implementing field types with the Post Custom Field. So you can allow users to populate a custom field via a text box, dropdown, checkboxes or radio buttons. No timetable yet, but we do plan on implementing this.

    Posted 9 years ago on Thursday September 10, 2009 | Permalink
  3. RichardBest
    Member

    Hi there - Just wondering whether there's any timetable for this modification yet please? I agree with Idealien that this would be an awesome addition to GF. I think it would make GF even more super-attractive to those who want to use WordPress as a grunty CMS. Would love to hear a timetable if you have one in mind.

    Many thanks
    Richard

    Posted 9 years ago on Friday October 9, 2009 | Permalink
  4. RichardBest
    Member

    Hmmm. It's just occurred to me that, if you added this feature, you could potentially provide an alternative (and better supported) solution to Flutter's custom write panels. You might also want to provide some advice to people on how they actually use the custom field data entered for a given post or page.

    You'll see I've just referred to "post or page". Currently, of course, GF enables one to set up forms which create posts but not pages. If you were to add the kind of custom field functionality referred to above, I suggest it'd be extremely helpful to add "create a page with custom field functionality" (as one can do with Flutter). The reason for this is that it'd then make populating pre-existing page templates much easier. As far as I'm aware, there are limited post template functions available for WP, in contrast to the page template functionality which is built in to the core.

    Would love to hear your thoughts on these ideas.

    Richard

    P.S. I would, in all likelihood, purchase a developer licence if you added this functionality. It would make GF one of the most powerful plugins on the market (IMHO). Cheers.

    Posted 9 years ago on Friday October 9, 2009 | Permalink
  5. RichardBest
    Member

    P.P.S. I think you'd also want to include a "post template" / "page template" drop down menu option within the form creation screen to enable the site admin (but not necessarily the user) to select a given template for the posts or pages created through the form.

    Posted 9 years ago on Saturday October 10, 2009 | Permalink
  6. Yes, we have considered adding Page creation functionality and probably will be adding this in the future. As you mentioned, it opens up some interesting possibilities with the enhanced custom field types.

    Posted 9 years ago on Saturday October 10, 2009 | Permalink
  7. RichardBest
    Member

    Thanks. Any idea on the timetable around these custom field and page creation options? Keen to know as it may influence whether I use GF for a project or pursue another option.

    Thanks
    Richard

    Posted 9 years ago on Saturday October 10, 2009 | Permalink
  8. The custom field enhancement are planned for the 1.3 release.

    I'm not sure on the page creation options, we have to decide how we want to handle it. If we want to use the existing Post fields, or create a new category of fields for Page FIelds. While we could just add options to the Post Fields, it may be more intuitive for less advanced users if they had their own category.

    Posted 9 years ago on Sunday October 11, 2009 | Permalink
  9. Just a follow-up response for additional thoughts. There is HUGE potential for this with the post types feature that 2.9 has started to implement. I've done many development backflips to enable users to submit and/or manage separate post types (rideshare board, job board, etc) that use custom fields to store the data elements. In the end the admin customization to allow authors to edit without having to use category selection and custom fields is almost too painful to be worth it.

    What if entries per gravity form were (optionally) manage-able through different sections within the admin and when you click edit it takes you to the form with existing data pre-populated. That's probably getting more integrated into the admin process than you want GF to be, but I think there are interesting possibilities here.

    It speaks volume about your development prowess when I can make it easier for joe user to submit the core details about a particular post type through the non-admin front-end than I can for joe editor through the admin console :/

    Posted 9 years ago on Wednesday December 30, 2009 | Permalink
  10. any update on this?

    Posted 9 years ago on Saturday January 16, 2010 | Permalink
  11. Update on which part?

    Gravity Forms 1.3 introduced field types to enhance the Post Custom Field usage. A Post Custom Field can now take the form of a variety of field types (drop downs, radio buttons, etc.).

    Posted 9 years ago on Saturday January 16, 2010 | Permalink

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