Closed steph643 closed 9 years ago
I solved this (for now) by adding the following line to my schema:
registered_emails: { type: [Object], blackbox: true, optional: true }
@steph643 I'd say there's nothing in your error for which accounts-emails-field
is responsible for...
As you already discovered, it's the schema validation which is failing and you have to patch it ;-)
Yes, thank you.
At this occasion, I felt some information is missing. Maybe you could add something like this to the doc:
The registered_emails
field which is added to the Meteor.users
collection has the same format than the built-in emails
field (as described in the Meteor documentation):
registered_emails: [
{ address: "cool@example.com", verified: true },
{ address: "another@different.com", verified: false }
],
If you use aldeed:collection2 with Meteor.users, you need to add the registered_emails
field to your schema:
registered_emails: { type: [Object], blackbox: true, optional: true }
Yeah, would be useful!
Could you please make a PR for this?
After installing your package, I get the following serve-side error when logging-in:
My guess is that you are trying to write your
registered_emails
field and that it conflicts with myMeteor.users
schema (which looks like this). Before I investigate further, can you please tell me if this is a know issue? Hopefully with a know workaround?