I've been working more on this without much success. The real problem with this is that the FORMS_FIELD_MAX_LENGTH setting does not get used for the Field *choices* max_length option even though the *default *field uses this setting.
I've tried recreating the Field model and changing the choices max_length option to 3000; however, this essentially forces the recreation of the entire Mezzanine form app, since a different related_name is needed to avoiding clashing with the current Field model. All the methods referencing form.fields would need to be updated to form.extended_fields to reference the new Field model. I also tried using Field.add_to_class to inject the new choices field into the model but the same problem arises, since the original choices field already exists. Is there any way to remove the existing choices field before injecting the new one? Thanks for the assistance! On Tuesday, December 31, 2013 12:24:53 PM UTC-8, [email protected] wrote: > > > I need to increase the max_length for the field choices in a form from > 1000 to 3000 characters. I looked at the Mezzanine configuration > documentation to see if I could find anything that would allow this. I > didn't, so then I attempted to extend the Mezzanine Field model and > override the choices field with one of the correct length. As Django > doesn't allow overriding fields, this didn't work either. > > Is there any way to do this short of recreating the Field model with the > increased choices length? > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
