https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10848
--- Comment #42 from Jacek Ablewicz <[email protected]> --- (In reply to Owen Leonard from comment #38) > I find that it's not possible to make the "library" selection mandatory. Is > there a reason for that? No, I just forgot about it. While it would not affect form submission itself (there will be always some non-empty value submitted in case when AllowPurchaseSuggestionBranchChoice is enabled), similar logic applies for itemtype, and yet our librarians found it vitally important that this field too could be marked as mandatory. And I agreed, good for consistency. Also still useful as an optional remainder for the user that a given field is relatively important and that they should pay a closer attention to set it accordingly. > Note that there is a JS validation plugin available in the OPAC if you want > to use it. See opac-memberentry.tt for an example. The plugin can be set up > to validate a form based on the markup (requiring fields which are , so it's > not necessary to dynamically configure the fields in the JS if you don't > want to. Hm, would it be as simple as adding jquery.validate.min.js include and one jquery call $('#add_suggestion_form').validate(); to the template? Let me see how it works ( please do not adjust your set).. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
