I am trying to port a fairly simple website to Backdrop. In that site, I use Field Extra Widgets which is a tiny utility module that simply adds two options for the edit form of fields: "hidden" and "read-only". This is for cases where one needs for example to provide a default value for a field, but wants to either prevent users from changing it when creating/editing the content or hide it out of their way (so that the form is not cluttered).
I am confident that I can port this module to contrib so that I can use it in this specific Backdrop-converted site, but I believe that such a tiny feature would be of value to core (it will be another thing to brag about Backdrop 1.5.0 in the DrupalSouth talk I might give ).
So, do I port it in contrib and see if we can merge it in core at some point in the future? ...or do I (please) get some guidance to add these small but very useful features in core now(-ish)?
Recent comments
OK, I did some more testing and figured this one out. In the paragraphs field setting for each content type you are using them, you can make the following selection for Default Edit Mode. I was in...
How to use 'Paragraphs Editor Preview'
Typically in a basic site, and as far as I know (I may be wrong) Backdrop doesn't store cookies for anonymous users, EXCEPT if you have things that need to persist, for example, if you create a View...
Does Backdrop set any Cookies / session variables for guests?
A couple of other things to keep in mind: - Roles in Backdrop do not use numeric IDs, but machine names. I see that the database insert command is trying to insert a numeric id as a role - Is this a...
Importing users from D7 site using Feeds - uses insert rather than update