At a high level, what needs to be undertaken to take a module's configuration data and make it exportable by Features?

Whether this is a contrib module that does not yet have Features support or a custom module that I have written, where can I start so that I can get it in code?

  • 1
    Too trivial: answered by looking at the readme files for the Features module. – user7 Mar 6 '11 at 20:48
  • Have to say I disagree. For one, the concept of features and exportability is not a novice issue. Secondly, if for questions like these we are just going to say, "refer to the readme", then this site will add no value over what can be found on drupal.org. – markdorison Mar 6 '11 at 22:56
  • If referring to the readme is all it takes to answer a question, that speaks more about the quality of the question than the quality of the answer. – tim.plunkett Mar 7 '11 at 15:58
  • 1
    People just saying "RTFM" is the reason sites like StackOverflow were created in the first place. – David Csonka Feb 23 '12 at 15:12

Instructions are in the Features API.txt, which provides several examples of how to better integrate your module with Features.

The easiest way seems to be building your module around the CTools Export API. Here's a pretty good article explaining how to do that.

| improve this answer | |

If your module is already taking advantage of the Entity API:

specify EntityAPIControllerExportable as the controller class, set the exportable key in hook_entity_info() to TRUE and include the schema fields necessary (module, status column) by copying the schema as defined in entity_exportable_schema_fields() to your hook_schema() implementation

See the Community Docs: Make an entity type exportable

| improve this answer | |
  • looks working . – monymirza Dec 7 '12 at 4:59

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.