Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Any way to overwrite existing fields on import? #14

Open
superwick opened this issue Nov 12, 2015 · 2 comments
Open

Any way to overwrite existing fields on import? #14

superwick opened this issue Nov 12, 2015 · 2 comments

Comments

@superwick
Copy link

Would be nice to be able to import existing fields, and have that only update the field metadata, and not affect any entries that may be using these fields (unless the fields go away). If i try to import fields that already exist, it tells me the handle name exists and won't import.

I hope this makes sense.

@engram-design
Copy link
Member

So you'd like to be able to overwrite settings for the field? For instance - a text field has things like placeholder, size, etc. Where it gets tricky is things like element fields which have a limit. What if you change the field limit to 1, but your entries have more than one element (think Assets)? These will be removed next time you edit the entry, which might not be what you want. I'm sure there are other cases too, but its something to consider.

@furioursus
Copy link

Even with this caveat, I think this is a great idea. ACF Pro for WordPress (hiss) does just this, albeit through its regularly generated JSON files that can be pushed up from local in order to keep fields in sync without having to rely on editing on production first and then distributing on every other server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants