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?

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

ayalon created an issue. See original summary.

ayalon’s picture

I 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?

ayalon’s picture

Title: Module is not working correctly » Module should use third party settings API to work correctly
FileSize
7.58 KB

Thx 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.

ayalon’s picture

Please use the updated version of the patch, I had to fix another bug.

  • eloiv committed cb772a2 on 8.x-1.x authored by ayalon
    #2897662: added third party settings API to work correctly
    
eloivaque’s picture

Thank you @Ayalon

eloivaque’s picture

Status: Active » Fixed
eloivaque’s picture

Status: Fixed » Closed (fixed)