Okay, Me and one of my friends played around with this for a bit and I think we’ve figured out why this occurs.
If “Save and Continue” is clicked BEFORE the custom field is added, then everything works fine.
I suppose that adding in the custom field before the first save essentially make WordPress try to add a custom field for a record that does not yet exist (hence the error/problem).
Perhaps you all could look into this a little further for me? Maybe a check can be included into the code to make sure that the post is created before the custom field can be created (or something to that effect)?
Unfortunately, the problem still exists when I deactivate Role Manager. 🙁
