Actively maintained

The Content Share module is designed to serve any Drupal site's content via a URL. A content consumer can initiate a transfer by a simple http request. This can be done from a client application or in a browser. The content from the originating site is returned in JSON, XML and other formats, enabled via the Services module.

This module allows you to host and manage your content in Drupal, but embed it in any other page/website that allows JavaScript.

Here's how it works.

1. Let's assume that your drupal site's URL is http://drupal.site/. Install and enable this module there. Create one or more pages of content there.
2. You want to embed the above content in some other site. Let's assume there is a plain HTML page at http://some.other.site/host-page.html
3. In host-page.html, include the following script tag anywhere<script type="text/javascript" src="http://drupal.site/cms_embed/init"></script>
4. Now you can have any number of container DIV's in your page that have a special attribute named "data-cms-embed". Like so ...<div data-cms-embed="http://drupal.site/path/to/content">this will be replaced</div>The content inside the DIV will be replaced with the content in http://drupal.site/path/to/content. Not just that, the extra stuff (header, footer, sidebars, blocks etc.) outside the content area will not be fetched.
5. If you want to further narrow down the parts of the content page that you want to embed, then you can provide an extra attribute named "data-cms-fragment" to the same DIV. Like so ...


Spaces Overrides mongodb storage backend for high performance and scalability of large spaces-enabled sites.

Video detailing what this does
Video detailing how this works
This module adds a system similar to publish / unpublished status of nodes. The reason that this is needed is so that you can tell certain roles they can't view nodes while others can. The issue with publishing status is that there is no grey. Menu systems automatically hide unpublished nodes while also checking for the node_access.

This blocks situations where admins and sub-admins need to work on content in the context that it will be presented left in a position where they are unable to do so. This will help create the same level of security that publish status does but without the limitations on admin-esk users to actively work with content the way it will eventually render (menu wise).

Use this module if you want to be able to limit what some users see in books and menus but still want others to have full visibility of those posts.

This should work with other node access methods as the priority of the grants in this module are very high. This is intentional so that it takes priority over all other access control projects, much in the same way that unpublishing a node takes priority over all access control methods.

This module defines a new field type Spotify Play Button, allowing you to embed spotify tracks.

Get public IP of specified client