Confirmed, works in backend forms but not in frontend.

The user field is not available on the front end, probably because of security reasons or lack of resources. So should we do some kind of warning when it is not available on the front or what do you guys suggest?

Not sure why its not available on the front end - that sounds like a bug to me BUT even without addressing that if a field can not be used in the frontend or inn the admin then there shouldnt be the option to set it to display there at all. The option should be disabled in the field creator. That woudl be the correct way to do it - not displaying a message

Pr #14500 removes the show on option when editing the field. Implementing the user field for the front can be done in another pr.

So we can close here @PhilETaylor @laoneo ?

I don't know if somebody will ever volunteer to make the user field available on the front. But the issue itself is not solved. @PhilETaylor should decide.

Well it comes down to expectation and documentation - like most of com_fields, its inconsistent, has no defined structure or documented goals...

Therefore its hard to know if this is a bug, a feature, an oversight, or just plain wrong.

If only there were some documentation or design document, or ux team that could be consulted...

Also as the "User" custom field has configuration:

One can quite rightly expect that it could be rendered on the frontend...

Not sure why its not available on the front end

The field (JFormFieldUser, not the com_fields thing) requires a view that is only available in the backend component. If it is desired to support this field on the frontend then proxy support used in other components must be added.

@PhilETaylor please have a Look at #14500 which removes "Show on" at "User" custom field.

I already left my thoughts here

#14500 (comment) #14500 (comment)

On 12 Mar 2017, at 20:08, Franz Wohlkönig notifications@github.com wrote:

@PhilETaylor https://github.com/PhilETaylor please have a Look at #14500 #14500 which removes "Show on" at "User" custom field.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub #13873 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/AAYa3K6uPyjA4Z_pt-1vvyvSVt85QmSsks5rlFCvgaJpZM4L1sw4.

So this one is a "wont fix"