[com_fields] Disable the option to show the user field on the front

[laoneo]

Pull Request for Issue #13873.

Summary of Changes

The user form field doesn't work on the front. Why is not part of this pr. This pr removes the option to define where the field to display.

Testing Instructions

• Create a new user field.
• Open the options tab.

Expected result

The "Show On" setting should not being displayed.

Actual result

The "Show On" setting is displayed.

Documentation Changes Required

[brianteeman]

Thank you

[ghost]

I have tested this item 🔴 unsuccessfully on 0d3897e

"Shown On" is shown at User- and Artices-Field (PR-Title ist about User, Screenshot about Articles).

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/14500.}

[laoneo]

It's about the "User" custom field. Did you create a user custom field?

[ghost]

@laoneo Created a New Field and Shown on is shown in Tab Options.

[laoneo]

@franz-wohlkoenig Is it really a user field?

@PhilETaylor there is some documentation already https://docs.joomla.org/J3.x:Adding_custom_fields/User_Field. The purpose of the field is to select a user. It is not too much complicated.

[ghost]

I have tested this item ✅ successfully on 0d3897e

My brain told me till now "User Group" … sorry and thanks for hint, @laoneo

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/14500.}

[mbabker]

JFormFieldUser cannot be used on the frontend due to a hardcoded dependency in the layout to the com_users backend component (why the hell are library classes still hardcoded to depend on components!?). Until a proper proxy is in place for the support to happen, this PR is valid and should be merged.

Let's leave comments about architecture or design docs out of this for the moment.

[mbabker]

You can either write the support for the frontend com_users component required to use JFormFieldUser in a frontend edit context (this limitation is not new to the addition of com_fields, all that did was further expose the architectural flaw) or you can remove from the UI a misleading and unusable option. The latter is a better choice unless someone has a PR for the former ready in the next couple of days. Even then, this PR could easily be reverted as part of that one.

[ghost]

If custom field is added in the backend with option "required", then adding an article in frontend at the moment (beta 3) becomes impossible because on submit we get en error message "Warning Field required: NameOfField"

[laoneo]

@ysrostov can you please open a new issue for your problem. This will also happen when you set that setting to back end only and try to edit an article in the front. We need to decide what we should do in that situation. Thanks.

[ghost]

Sure thing
#14692

[normanmm]

I have tested this item ✅ successfully on 0d3897e

Result is as expected

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/14500.}

[jeckodevelopment]

RTC

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/14500.}