Go to Joomla backend >> Users >> Fields and Create a new Field (text, colorpicker or textarea) and add them to the registration form (with or without creating a group).
text fields should only be disabled when the user select them to be disabled but only the editor field seems to be enabled.
Disabled Fields
Tested in Firefox & Chrome
Editor fields seems to work
text input, color picker & textarea don't.
php: Windows NT MY-PC 6.1 build 7601 (Windows 7 Professional Edition Service Pack 1) i586
dbversion: 5.5.5-10.1.21-MariaDB
dbcollation: utf8_general_ci
dbconnectioncollation: utf8mb4_general_ci
phpversion: 5.6.30
server: Apache/2.4.25 (Win32) OpenSSL/1.0.2j PHP/5.6.30
sapi_name: apache2handler
version: Joomla! 3.7.0-beta3 Beta [ Amani ] 21-February-2017 15:03 GMT
platform: Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT
useragent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
I created a video of the whole process https://www.dropbox.com/s/717zgayo90d7064/joomla37customfields.mp4?dl=0
This might have already been reported so feel free to merge it or otherwise.
Similar Issue on the forum: https://forum.joomla.org/viewtopic.php?f=706&t=948218
Labels |
Added:
?
|
Title |
|
||||||
Status | New | ⇒ | Closed | ||||
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-03-19 07:47:39 | ||||
Closed_By | ⇒ | Bakual |
Confirmed... Silly me.
Shouldn't that be the default setting?
No, by default permissions have to be disabled, not enabled. It depends on the context if it public should be able to edit something, basically it would only be for registration fields and the contact formular where public should be allowed to edit the value. All other cases we expect at least a registered user or even higher rights.
Thanks bakul, your comment works for me
That's a permission setting.
You need to make sure the "Public" group has the "Edit Custom Field Value" set to "Allowed" (check "Permissions" tab of your custom field). Then visitors will be able to edit values in that field.
I'm closing this issue since it is a misconfiguration, not a bug.,