Feature Request: Make the photo field on users a standard field type
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 3.6k
- Forks
- 705
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 134
Description
The photo field thats on users would be a great field type to be able to use everywhere. Its nice that its limited to a single asset and that it must be an image.
It doesn't expose anything you cant already do with the standard assets field but its a nicer user experience for a single image with the short cuts to "change image" and "edit image"
Its also a lot cleaner in the templating as you dont have to .one() or [0]
Id say about 60%-70% of the time we are using an assets fieldtype a photo fieldtype would be a better fit.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Compare the existing users photo field with the standard assets field to determine the implementation scope, then verify that a reusable single-image field supports the stated editor shortcuts and simpler templating behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100