Actively maintained

After you make a site active, the previous nodes added need a domain_source.domain_id to match.

The Domain Send All is a modules developed to address specific conditions while using DA and active/inactive sites for staging. See the module code for more information.

Inline Devel - what is it?

Inline Devel is a module that extend the regular devel executed form with an
IDE options.

Why should you use it?

The execute code form is good for debugging data without edit files.
The problem is that we don't have an auto complete for functions and classes.
Inline devel offers you this solution. When starting to type the function name,
you'l get a list of functions, classes, interfaces and hooks available to you.

Yes, you can define hooks. All the hooks you'l write down in the execute code
form will be attached as hooks defined by the module inline_dvel_dummy_module.
If you worried - inline devel is not writing on the files of the modules but
create a session with a stack of the hooks you defnied or any other functions.

How to use it?

Becuase this module extend the devel execute form you need to go the form.
Go to ?q=devel/php. In the form start to type your code and you'l get the list
of available functions, classes, interfaces and hooks.

If you'd like to delete some functions that you defined in the execute code
form emable first the module "Inline Devel UI" and then go to
?q=admin/config/development/inline_devel_admin and there you can delete the
functions.

Features

1. Use ctrl + s to submit the form
2. Use tab for a much more easier indentation

This module provides minimal entity type that is fieldable with absolutely zero extraneous functionality.

Why would you want to use this when node module enables you to create as many custom content types as you want?
Downside that i find difficult to overcome with node entity is there are too many modules that depend on it and force added functionality that you don't always want, and it gets worse when you cannot disable the added functionality. What if you want to use a custom content type to store information that is not meant for public "content consumption"? too bad! you cant with node (or at least i found no easy way to prevent that). Your custom node type will appear in search results, have comments attached to it (minimal metadata when comments are disabled), etc etc etc. I didn't want any of that and was fed up with not being able to turn off unwanted extra functionality on node types, so i created this module to provide a way to create custom content types without any extraneous functionality, unless explicitly added via fields.

Important notice

While module is currently in usable shape, it is not yet in optimal quality.
This is my first ever attempt at writing custom entity implementation and i am still learning.