{"action":"created","issue":{"url":"https://api.github.com/repos/meteor-useraccounts/core/issues/462","labels_url":"https://api.github.com/repos/meteor-useraccounts/core/issues/462/labels{/name}","comments_url":"https://api.github.com/repos/meteor-useraccounts/core/issues/462/comments","events_url":"https://api.github.com/repos/meteor-useraccounts/core/issues/462/events","html_url":"https://github.com/meteor-useraccounts/core/issues/462","id":95036197,"number":462,"title":"How to add additional fields after signed-up by third party services?","user":{"login":"juliomac","id":3759295,"avatar_url":"https://avatars.githubusercontent.com/u/3759295?v=3","gravatar_id":"","url":"https://api.github.com/users/juliomac","html_url":"https://github.com/juliomac","followers_url":"https://api.github.com/users/juliomac/followers","following_url":"https://api.github.com/users/juliomac/following{/other_user}","gists_url":"https://api.github.com/users/juliomac/gists{/gist_id}","starred_url":"https://api.github.com/users/juliomac/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/juliomac/subscriptions","organizations_url":"https://api.github.com/users/juliomac/orgs","repos_url":"https://api.github.com/users/juliomac/repos","events_url":"https://api.github.com/users/juliomac/events{/privacy}","received_events_url":"https://api.github.com/users/juliomac/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-07-14T20:45:44Z","updated_at":"2015-08-04T01:17:52Z","closed_at":null,"body":"On my accounts-password signup, I pretty much could add all extra information for payment I want, but when the user signs-up via Facebook, for instance, it logs without ever asking to fill in these extra fields.\r\n\r\nI have added fields to atForm using template, such as on the example below:\r\n\r\n     AccountsTemplates.addField({\r\n        _id: 'CardName',\r\n        type: 'text',\r\n        required: true,\r\n        re: /[a-zA-Z\\ÁÉÍÓÚÝÂÊÎÔÛÀÈÌÒÙÄËÏÖÜŸÇÃÑÕáéíóúýâêîôûàèìòùäëïöüÿçãñõŒœßØøÅåÆæÞþÐð\\s\\']{3,}/,\r\n        template: 'GuestCardName'\r\n    });\r\n\r\nWith template:\r\n\r\n    <template name=\"GuestCardName\">\r\n\t<div class=\"form-group\">\r\n\t    <label for=\"at-field-{{_id}}\">Nome no Cartão</label>\r\n\t    <!-- Pattern of Last name contains \\s to allow more than one surname-->\r\n\t    <input type=\"text\" class=\"form-control validcolored\" id=\"at-field-{{_id}}\" name=\"at-field-{{_id}}\"\r\n\t    value=\"julio\">\r\n\t</div>\r\n</template>\r\n\r\n\r\nWhat is the best strategy?\r\n\r\nI though on letting the user logs in with 3rd party service then, when needed, ask to complete with a second payment information form.\r\n   Negative: It is not an elegant solution: I can't re-use the templates because of the ```id=\"at-field-{{_id}}\"``` that I have to have on addField. Is another a way to re-use it?\r\n\r\nAn alternative approach would be to have two Signup forms structure (https://github.com/meteor-useraccounts/core/issues/358), the second only with the missing fields and meld it all up with ```splendido/meteor-accounts-meld``` . Think it is a waaay to wild alternative.\r\n\r\nAs a suggestion, a possible feature for the package would be to have a form state=\"completeProfile\". We could have it in our configuration set as ```true``` and add fields only to it.\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/meteor-useraccounts/core/issues/comments/127446269","html_url":"https://github.com/meteor-useraccounts/core/issues/462#issuecomment-127446269","issue_url":"https://api.github.com/repos/meteor-useraccounts/core/issues/462","id":127446269,"user":{"login":"splendido","id":6148980,"avatar_url":"https://avatars.githubusercontent.com/u/6148980?v=3","gravatar_id":"","url":"https://api.github.com/users/splendido","html_url":"https://github.com/splendido","followers_url":"https://api.github.com/users/splendido/followers","following_url":"https://api.github.com/users/splendido/following{/other_user}","gists_url":"https://api.github.com/users/splendido/gists{/gist_id}","starred_url":"https://api.github.com/users/splendido/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/splendido/subscriptions","organizations_url":"https://api.github.com/users/splendido/orgs","repos_url":"https://api.github.com/users/splendido/repos","events_url":"https://api.github.com/users/splendido/events{/privacy}","received_events_url":"https://api.github.com/users/splendido/received_events","type":"User","site_admin":false},"created_at":"2015-08-04T01:17:52Z","updated_at":"2015-08-04T01:17:52Z","body":"I know [Telescope](https://github.com/TelescopeJS/Telescope) is doing something like your first proposal (to have a second step with a dedicated form...) but they've change all the code recently and I have no idea where to look for now...\r\n\r\nThe idea to have a specific internal state to expose just profile fields is a good one!\r\nI'll try to keep it in mind for v2.0\r\n"}}