Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hi
I think, the module is very helpful and a good idea. I tested it and it works out of the box.
But there is a serious issue, if you want to deploy the configuration to another system.
If you completely start with an empty database and import your drupal config, the "cardinality_config" on the field configuration is wiped out. Even if you try to import it again, its constantly getting wiped out / the config is lost.
It seems, that the value gets saved to the config, if you save the field form but then somehow not is imported during config-import on a new instance.
Any ideas?
Comment | File | Size | Author |
---|---|---|---|
#4 | field_config_cardinality-2897662-v2.patch | 7.49 KB | ayalon |
Comments
Comment #2
ayalon CreditAttribution: ayalon commentedI think the problem is, that if you save the parent entity, the field configuration of every field is sometime saved. Because the cardinality is only save in the form alter submit function, the value gets lost if a configuration updates all dependent configurations.
Maybe this is a reason, why the cardinality_config gets lost?
Comment #3
ayalon CreditAttribution: ayalon at Liip commentedThx to the help of @larowlan I was able to figure out the issue.
I rewrote the part, how the configuration is stored and retrieved. Additionally I added support for multivalue select widgets.
Comment #4
ayalon CreditAttribution: ayalon at Liip commentedPlease use the updated version of the patch, I had to fix another bug.
Comment #6
eloivaqueThank you @Ayalon
Comment #7
eloivaqueComment #8
eloivaque