You can't fix stupid

On 2 Nov 2016 3:29 p.m., "Phil Taylor" notifications@github.com wrote:

Steps to reproduce the issue

Clean install
Add a single field (just one) - anything - save and close
Edit a content item
Actual result

A tab entitled Fields which is totally blank, confusing..
[image: screen shot 2016-11-02 at 15 25 30]
https://cloud.githubusercontent.com/assets/400092/19935216/22f18878-a111-11e6-9d85-f5913f3aea1e.png Expected
result

Either the tab should not be there at all, or the blank page should tell
me im an idiot and how to fix the problem.
System information (as much as possible)

e76aa02
e76aa02

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#12703, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABPH8dKS-kq38xF2xCNtCW2-uEyX6AEIks5q6KxdgaJpZM4KnYKc
.

i agree with @PhilETaylor

I can't reproduce your issue.
Just did a clean install and the single text field is displayed under the Fields tab.
It also shows when one creates a new article.

Ok I have replicated your not replicating :)

The "trick" is to create the field as a CAPTCHA field... not a text field

This then gives a blank tab... instead of no tab.

The reason is that this field is front end only for obvious reasons. There
should be an indicator of this in the admin. I did come across this in
earlier testing.

Additionally there is a bug in that the option to display this field in the admin is still available

Also there is zero point in having the required option as who wants a captcha without it being required

I am not even sure if that option will work anyway see
https://github.com/joomla/joomla-cms/blob/staging/libraries/cms/form/field/captcha.php#L110

Changed the title to show that this is an issue with the captcha field in com_fields

Maybe captcha shouldnt even be a field type available in com_fields as com_users and com_contact already support captcha natively

+com_content submit an article
+com_weblinks submit a weblinks

I never used the captcha field when I was working with DPFields, so probably it would make sense to remove it completely from com_fields.

As this is a captcha only problem it is solved by #12719 so we can close here @PhilETaylor ?

tested #12719