The importer is reading directly from the table definition to give the maximum character values. In this case, it looks like you may have edited your table to allow 40 characters. Editing the database alone however does not change the forms in Gibbon, which would also need to be edited to allow 40 characters.
I’ve checked and the default database length for that field in Gibbon is indeed 20 characters:
The importer is reading directly from the table definition to give the maximum character values. In this case, it looks like you may have edited your table to allow 40 characters. Editing the database alone however does not change the forms in Gibbon, which would also need to be edited to allow 40 characters.
I’ve checked and the default database length for that field in Gibbon is indeed 20 characters:
There is a maxLength method on those fields that you could edit. This would be a codebase change, so as you’ve noted it would get overwritten by an upgrade.
There is a way to keep changes if you use Git to track and merge your code. You could fork the Gibbon Core repo on GitHub, then run git init on your local code to setup a local repo and add the fork as a remote repository. There lots of info and tutorials online for setting up repositories. Once you have these setup, anytime there is a new version you can merge it in, and prevent overwriting your modifications. It’s technical to setup, but the best way to safely change the codebase.