We need to get rid of user pictures and use build in fields instead. See related Drupal issues: - [ ] Convert user pictures to Image Field - [ ] Fix user_picture field creation
Also for reference, here is the change record.
Follow-ups: - We'll need to lock the picture field - This will introduce a performace regression, so we should keep an eye on this issue.
GitHub Issue #:
243
Recent comments
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Importing the staged config throws an error: another field with the same name already exists
Thanks, I have to go out now, I will try later on and report back
Importing the staged config throws an error: another field with the same name already exists
Hi Francis. Yes, what config do you have in staging for it? You might have configs like: field.field.field_video_embed field.instance.node.page....
Importing the staged config throws an error: another field with the same name already exists