Required and Default Value are not applicable so this will cause confusion.
For Show Close Button, I expect the button to not display if set to false.

Required and Default Value are not applicable so this will cause confusion. For Show Close Button, I expect the button to not display if set to false.

Hi,

i'm not exactly sure what you mean with "required". I've removed the empty default value on the close form field xml.

The documentation says this about the close button:
close (optional) a value of 'true' (for alerts) or the value for the data-dismiss of the Bootstrap close icon

Wondering if the default should be "true" instead of empty to show the possibility.

i'm not exactly sure what you mean with "required". I've removed the empty default value on the close form field xml.

The documentation says this about the close button: close (optional) a value of 'true' (for alerts) or the value for the data-dismiss of the Bootstrap close icon

I was expecting it to look like this without the close button.

i'm not exactly sure what you mean with "required". I've removed the empty default value on the close form field xml.

The documentation says this about the close button: close (optional) a value of 'true' (for alerts) or the value for the data-dismiss of the Bootstrap close icon

I was expecting it to look like this without the close button.

Those settings are not added by the plugin. Do you know of a custom field that has these settings removed so i could check that?

I have tested this item ✅ successfully on 84c1b7c

Hi Tom, I have successfully tested this.

(1 question, why can't we have this for the User Accounts area as well? :) )

(1 question, why can't we have this for the User Accounts area as well? :) )

Hi Emmanuel,

With User Accounts area do you mean the website front-end?
Technically there is no reason why we could not allow this. I've created and tested this already but it's not in the PR because it is not a "plain" implementation of the note form field. If maintainers would want this to also be available in front-end of the website then i could add that.

(1 question, why can't we have this for the User Accounts area as well? :) )

Hi Emmanuel,

With User Accounts area do you mean the website front-end? Technically there is no reason why we could not allow this. I've created and tested this already but it's not in the PR because it is not a "plain" implementation of the note form field. If maintainers would want this to also be available in front-end of the website then i could add that.

Hi Tom, no I meant backend actually... I know the backend has Users --> User Notes area but that is not referenced in the user's profile itself which is not so convenient, that's why I liked the idea of this being available in the custom fields for Users that would one could have a notes field inside the user's profile... (vs having to go back and forth between a user's profile and the User Notes area).

@exlemor you are comparing apples and pears

@exlemor like brian said that is totally different from what this is and does. So then the answer is no not with this PR.

I started testing (and I'm not familar with custom fields). I created a Note custom field with 'notes field description' and 'notes field heading', you see the representation in the screenshots. As mentioned before, some settings like 'Default Value' is unused. 'Automatic Display' is also not used, as there is no content? 'Editable In' works as 'Shown In'. But what hurts me, if I set 'Required' in the custom field, the article is no longer saveable in administrator backend or site frontend, see error message:

Backend-View with error

Frontend edit view

Shouldn't we disable the options that can't be used and rename ‘Editable In’ to ‘Display In’? And maybe a use case would be helpful. If this is just a header for the following custom field, couldn't this be ¿easier? implemented with CSS in the following custom field? I would like to continue to support testing, thx.