* Take ctools exportables and port them straight to hook_entity_info().
* Use the controller to load objects defined in code too.

Comments

fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Active » Fixed

Done, see http://github.com/fago/entity/commit/e3911f0304622add50de7badf3c656ecd63...

* There is new flag controlling whether an entity is exportable: $entity_info['exportable']
* It's possible to specify a 'name key' now, so entities may also have string based identifiers, while internally (e.g. by the field API) the numeric id is used.
* Defaults are automatically incorporated by the entity loader.
* $entity_info['export'] can be used to define further properties as known by ctools exportables.
* Whether entities are defined in code/db is written to $entity->status by default, but that's configurable.
* The "can disable" feature of ctools that allows disabling exportables defined in code with a variable(_get) is currently not supported.
* I enhanced the test module to test exportables and improved profile2 to make use of it for defining profile types in code.

fago’s picture

fago
Primary language German
Location Vienna
commented

also see #681362: d7: Support exportable entities

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.