While working on #2994 I noticed that there are many add- and edit-forms in /seeddb that use crispy-forms.
Some use crispy-forms explicitly (and thus are already mentioned in #2794), some implicitly. Some use basic fields and are therefore universally convertible by using seeddb/_form_fields.html from #2994, some use "special" fields and need additional tweaks.
Add/edit forms in seeddb by URL:
NB! No differentiation between "add" and "edit" is needed here since both form types stem from the same template - seeddb/edit.html, unless otherwise specified below.
While working on #2994 I noticed that there are many add- and edit-forms in
/seeddbthat use crispy-forms.Some use crispy-forms explicitly (and thus are already mentioned in #2794), some implicitly. Some use basic fields and are therefore universally convertible by using
seeddb/_form_fields.htmlfrom #2994, some use "special" fields and need additional tweaks.Add/edit forms in seeddb by URL:
NB! No differentiation between "add" and "edit" is needed here since both form types stem from the same template -
seeddb/edit.html, unless otherwise specified below./seeddb/netboxgroup/(Uncrispyfypython/nav/web/seeddb/forms/__init__.py:DeviceGroupForm#2988)/seeddb/netbox/add/edit form #2997/seeddb/service/add/and/seeddb/service/edit/)/seeddb/room/(Uncrispyfy foundation5 field #3000)/seeddb/location/(Uncrispyfy foundation5 field #3000)/seeddb/organization/(Uncrispyfy foundation5 field #3000)/seeddb/usage/(Uncrispyfy foundation5 field #3000)/seeddb/type/(Uncrispyfy foundation5 field #3000)/seeddb/vendor/add(edit not possible) (Uncrispyfy foundation5 field #3000)PrefixVlanFormin seedDB #3118/seeddb/cabling/(Uncrispyfy foundation5 field #3000)