bachir
0efc41f121
updateField()'s client branch previously rejected any name that didn't match an existing "Client" term, on the assumption the front-end's datalist restricted input to known names -- it doesn't, it only suggests them, so this blocked adding a genuinely new client from the inline edit even though the content type itself allows it. Now creates the term (same "autocreate" behavior as a standard Drupal entity reference autocomplete widget) rather than erroring. Frontend also appends the newly created name to allClientsList so it shows up in the filter dropdown/datalist immediately, not just after a reload picks it up via fetchClientNames(). Verified live: typed a brand-new client name inline, save succeeded, confirmed the taxonomy term was actually created in the database and the filter datalist updated immediately -- then reverted the test node and deleted the test term.