{"action":"created","issue":{"url":"https://api.github.com/repos/engram-design/FieldManager/issues/3","labels_url":"https://api.github.com/repos/engram-design/FieldManager/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/engram-design/FieldManager/issues/3/comments","events_url":"https://api.github.com/repos/engram-design/FieldManager/issues/3/events","html_url":"https://github.com/engram-design/FieldManager/issues/3","id":69185903,"number":3,"title":"FWIW: I Deleted Default Field Group, oh no!","user":{"login":"Natetronn","id":582149,"avatar_url":"https://avatars.githubusercontent.com/u/582149?v=3","gravatar_id":"","url":"https://api.github.com/users/Natetronn","html_url":"https://github.com/Natetronn","followers_url":"https://api.github.com/users/Natetronn/followers","following_url":"https://api.github.com/users/Natetronn/following{/other_user}","gists_url":"https://api.github.com/users/Natetronn/gists{/gist_id}","starred_url":"https://api.github.com/users/Natetronn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Natetronn/subscriptions","organizations_url":"https://api.github.com/users/Natetronn/orgs","repos_url":"https://api.github.com/users/Natetronn/repos","events_url":"https://api.github.com/users/Natetronn/events{/privacy}","received_events_url":"https://api.github.com/users/Natetronn/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-04-17T17:54:06Z","updated_at":"2015-04-18T00:12:53Z","closed_at":null,"body":"I just deleted the Default Field Group and all it's Fields so I could see how the import works. The import was successful but, no fields display because the Default Field Group doesn't exist any longer. I tried going to Settings > Fields to add in a group and receive an error at that point (probably because fields exist but, no groups exist.)\r\n\r\nI was hoping when we export a whole group of fields that the group would go with it. That way it just creates it and adds the fields to the group on import. It would be nice if it asked us if we wanted to rename the group on import as well.\r\n\r\nI noticed there was a dropdown for the group we want to add the fields to. In my case it was blank because no Group existed (I deleted it.) This seems like a good place to test for the existence of a Group/s and if one doesn't exist ask if we'd like to create it (or just create a Default one automagically maybe.)\r\n\r\nOR and I'm just thinking out loud here, just don't allow us to delete the only field group that exists.\r\n\r\nNow, I wouldn't actually have done this in production but, I did want to test things out and give you feedback on this just the same because I KNOW someone is actually going to go down this road because, well, they can. \r\n\r\nI'll manually add back in my group to the DB to get myself unstuck at this point but, I know others may not appreciate having to do that ;-)\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/engram-design/FieldManager/issues/comments/94103721","html_url":"https://github.com/engram-design/FieldManager/issues/3#issuecomment-94103721","issue_url":"https://api.github.com/repos/engram-design/FieldManager/issues/3","id":94103721,"user":{"login":"engram-design","id":1221575,"avatar_url":"https://avatars.githubusercontent.com/u/1221575?v=3","gravatar_id":"","url":"https://api.github.com/users/engram-design","html_url":"https://github.com/engram-design","followers_url":"https://api.github.com/users/engram-design/followers","following_url":"https://api.github.com/users/engram-design/following{/other_user}","gists_url":"https://api.github.com/users/engram-design/gists{/gist_id}","starred_url":"https://api.github.com/users/engram-design/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/engram-design/subscriptions","organizations_url":"https://api.github.com/users/engram-design/orgs","repos_url":"https://api.github.com/users/engram-design/repos","events_url":"https://api.github.com/users/engram-design/events{/privacy}","received_events_url":"https://api.github.com/users/engram-design/received_events","type":"User","site_admin":false},"created_at":"2015-04-18T00:12:53Z","updated_at":"2015-04-18T00:12:53Z","body":"Well caught, I actually want to improve the import process into more of a mapping-style similar to [FeedMe](https://github.com/engram-design/FeedMe). This will allow you to define which groups you'd like fields to be allocated into, rather that putting all fields into a single group.\r\n\r\nShort-term though, I'd like to be able to create a field group directly from the Import screen, which would be handy. Possibly even automagically as you suggest. Along with that, you should be able to specify a handle prefix for all the fields you import, just so there's no duplication (error) between other existing fields. This is only an issue when importing/exporting on the same site.\r\n\r\nI've now added some error-handling so that you must specify a group.\r\n\r\nI agree exporting groups would be beneficial - the problem being that what if you don't want to preserve the groups on the new site? In a boilerplate scenario, this would be fine, where you have a set group of default fields you want to use on every new site. But what if you want to pick a few, from different groups on one site, but have them all in one group on another? It's sort of an edge-case, but something that could be easily handled with the group-mapping above...\r\n\r\nAnd thanks for the detailed description!"}}