Benefit of config entities over regular config entries?


A config entity is useful when there need to be multiple variations of the configuration, think views, image styles, or node bundles. If there is no need to create variations, as in which stores the site's basic information or core.extensions which stores the list of enabled modules, a basic config entry is appropriate.

Similar questions

Batch process stuck repeating first operation over and over
It's my first time working with the Batch API. I have a batch operation that I have almost working, but it gets stuck on the first item and I'm out of ideas on how to fix it. What the batch thing does is iterate over a bunch of nodes and transform the fake-locations scattered over a dozen text fields into real Location CCK fields. When the batch pr...
Feeds importing unique nodes over and over
I'm trying to import events to a calendar from an external ics.. I installed the Calendar module with the Feeds module. Unfortunately it creates the whole time new nodes. Even if the UID is unique (mapped to field field_gimme_uid) in the node. Update nodes is setted 'on'. I have checked everything but everything seems alright. The unique field is c...
Drupal watchdog database table flooded with same message over and over?
I've: And still, the same error message is being written to Watchdog. I execute: "delete from watchdog" and IMMEDIATELY after I check in the watchdog table, the same error is there. Not that it would help, but here's the error: AND So, my questions are:
My Drupal 7 batch processing code is repeating the final iteration of the batch process over and over. Can someone help me fix it?
I'm trying to move data from an old database to a new one. My code doesn't currently write anything (which is fine), but the reading repeats over and over on the last record even though $context['finished'] is set to 1. Any idea what I'm doing wrong?
Attaching Entities to other Entities
I have two custom entities in a D7 site. One is 'additional' data on an entity, and I want to attach that data to the main entity every time it is loaded. Within Entity/Entity API, how can I do that correctly? attachLoad sounded correct but seems to be Field related, all my data are not fields (yet).
Using "Model Entities" Module to Create Custom Entities
Model Entities: I've been trying to use this contrib module to create my own entity (the "client" entity). Steps I've undertaken: So far debugging has gotten me this far: So I suspected it's something to do with the custom "views" that the module is implementing. And indeed, it did not register the custom view proper...

Also ask

We use cookies to deliver the best possible experience on our website. By continuing to use this site, accepting or closing this box, you consent to our use of cookies. To learn more, visit our privacy policy.