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
As I work through things I flush the caches after every change I make. As far as I can tell I have the custom module in the correct place (/modules/custom/fix_zero_search) and the file...
custom module not showing up in modules list
If you haven't already, flush all the caches. If it is in the modules folder whether directly or in a custom folder it will show up. If not, something else is wrong with your site; check...
custom module not showing up in modules list
Awful idea! That's not how modules get installed! The number in db indicates the installed state and schema version. You're not supposed to fiddle in the database directly. There's an...
custom module not showing up in modules list