@AlexRed your additional comment: similar #13753

we can use Contact Field to allow edit it in frontend by Guest?
And the info insert by guest in the contact field Where are going?

Editor user field can be edit by default in the User Registration page but not work also if set the acl permission, not data saved for the user in the editor field.

In the latest stagin the Editor user field can be edit by default in the User Registration page but not work if no set the acl permission. Other Field type can't be edit if no ACL permission.

@AlexRed means closing is okay?

Nooooooooo
The problem is in the stagin.
The Editor user field can be edit by default in the User Registration page but not work if no set the acl permission.

misreading your Comment, so no closing.

oppsss... sorry for my bad english.
Please can you try it and confirm ?

to be honest: i don't get the Issue-Point. I guess you mean Editor-Field should also get by ACL-Default to not edit.

it is ACL-Default to not edit, but you can edit it :(
But the text not saved in the database

thanks, got it, set "confirmed" on Issue Tracker.

the same Editor Field in the contact Mail form can be edit when permission is not set but in this case the data is saved or better the data is send in the mail body.

for me an ACL "column" in the field list is important, to show if the field can be edit or no by the users.

I confirm the issue.
If the Editor field does not allow Public to use it, we have an issue indeed, specially if the field is required.

@laoneo @Bakual
please look into this. It is easy to mistake here.
I even get the Readmore and Field by default as editor-xtd buttons.

I guess this is more of a problem of the editor that it doesn't have a disabled mode.

for me an ACL "column" in the field list is important, to show if the field can be edit or no by the public. By default all new field are set to no edit in the ACL but the administrator can't see it.

we can use the "checkbox" icon:
red "checkbox-unchecked" for no permissio for all (default)
green "checkin" if allow for all
checkbox-partial if permission for only some group

Every field has permission

What is the problem here? You can set the acl.for everything so I don't understand the issue

the editor field is editable with ACL set to no edit. But not work, no data saved.

So it is not editable then. It would be a security issue for public users
to be able to use the rich text editor and definitely should not save any
data by default

Are you saying that the field should not be displayed.

http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
Virus-free.
www.avg.com
http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On 5 April 2017 at 10:51, Alessandro Rossi notifications@github.com wrote:

the editor field is editable with ACL set to no edit. But not work, no
data saved.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#14049 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABPH8Wdj0HkXnT_WPTXhMhLWFnhJBEbZks5rs2QjgaJpZM4L_DgW
.

--
Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
https://brian.teeman.net/ http://brian.teeman.net/

for me yes, why display a field in the User registration form or in the Contact Mail form if it is not editable ?
But it can be "required" and block the procedure

That's a different question and a very valid one which nobody raised till now. We can make it that way, when a field is not editable, then it will not be shown. But then I guess we will get tons of requests why a field is not visible just because the permission is wrong set (keep in mind, the edit value permission is initially only allowed for super admins).

But also now I guess we will get tons of requests why a field is visible but no editable, just because the permission is wrong set (by default).
So for me an ACL "column" in the field list is important, to show if the field can be edit or no by the public. By default all new field are set to no edit in the ACL but the administrator can't see it.

and if the Field is not visible we solve the editor problem.

Now that I understand what you mean my personal recommendation would be that if a user does not have the acl priviliges to edit a field then it should be disabled but styled to show that you dont have the permission to edit it. We already have similar styling elsewhere for example in the edit profuile page when you have set the option to disable changing the username

but you can't do it for the editor field.
And like for the username is not editable is not editable now the other user custom field, no special styling, only not editable. We need a message about not editable for no permission or similar, but also for the editor field if we decide to show the field also it is not editable

The problem is that the editor formfield (not the custom field itself) doesn't support readonly/disabled states.
It's a duplicate of #13665, thus I'm closing this issue.