Custom Fields – Save and Reuse?

This topic contains 4 replies, has 2 voices, and was last updated by  identity 5 years, 1 month ago.

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket
  • Author
    Posts
  • #508977

    identity
    Lifetime Member
    Post count: 445

    Is it possible to save and reuse custom fields?

    On the Custom Fields tab, under the “Standard Fields” and “Predefined Fields” sections there is a “Custom Fields” section, which appears empty…

    There are no custom fields here yet.

    What is that for and how does it work? Haven’t really seen any mention of it.

    My hope and what would be extremely valuable is that we could create reusable field “templates” that could be used like the Predefined Fields…. create them once, accessible across all CPTs, and then pull them in and edit/modify as needed for the specific instance. At least this would reduce some of the repetitive nature of creating CPTs.

    Cheers

    #508988

    Alex Rollin
    Moderator
    Post count: 27815

    The whole tab is “Custom Fields”.

    That section is for when a developer adds a new predefined customizaed field.

    It is not possible to save and re-use custom fields.

    See: https://wpgeodirectory.com/support/topic/cloning-exporting-importing-templating-cpt-custom-fields/

    #509026

    identity
    Lifetime Member
    Post count: 445

    Thanks.

    In light of the inability to export/import, I was hoping this would be another way to ease the load.

    I see these as two different features.

    For this one specifically, would love to see this added to the roadmap. I would envision a separate section/tab within the Geodirectory section that would allow the construction of additional pre-defined fields…user-generated pre-defined if you will.

    It would have a similar interface to the Custom Fields section, but this would simply allow the creation and configuration of additional pre-defined fields.

    From there, once saved, they would simply show up under the Custom Fields tab of the CPTs. Just like the other pre-defined fields, they could be added and then modified for each specific CPT.

    Consider it a kind of copy-paste on steroids for custom fields!

    Export/import of whole CPTs…structure, fields, etc. would still be extremely useful, and ideally the two features could work independently of each other but could also be used in tandem for maximum effect.
    – Construct user-generated custom fields
    – Create a CPT template base, including user-generated fields
    – Create new CPT by importing in a CPT template base
    – Add any remaining unique/additional predefined or user-generated custom fields to complete CPT configuration.
    – Ideally…import pricing and package template bases as well.

    Thanks!

    #509087

    Alex Rollin
    Moderator
    Post count: 27815

    Thank you for the feedback, I have taken it up as a suggestion for the developers to review.

    #509176

    identity
    Lifetime Member
    Post count: 445

    Great! Appreciate it, thanks.

    Cheers

Viewing 5 posts - 1 through 5 (of 5 total)

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket
20% Discount Offer
Hurry! Get your 20% discount before it expires. Get 20% Discount