Actively maintained

Module to integrate the GameAnalytics.com service with Rules.

GameAnalytics.com recently decided to open up their for free use, so this module is to integrate Rules with their API.

This module will allow your users to log in with only their email. No account yet? No problem, we'll create one on the fly.

We live in an age of restrictions and private areas. Web 2.0 caused almost every site to evolve and have some sort of account system. The problem with this is that most of these systems require the users to remember a password to authenticate themselves.

In most cases, while necessary, a password or login in general breaks UX. Users loose their password, they need to wait for password reset emails or they just don't bother in the first place and will never create an account.

That is where 'Email Only Login' (EOL) comes in.

But BEWARE! Only some use cases allow for such a low level of security. Obviously in such a system it's easy to log in as someone else. Only use this module in those cases where this doesn't really matter or where there is enough trust between the users, in a closed ecosystem for example, to allow for such openness. As a rule of thumb this module should only be used for non sensitive data websites where knowing who is currently using the website is more important than make their customized content private. You should also make sure your site makes this clear to the users.

A simple module to expose the current session as a token (for example, for consumption within the Rules module).

Neo4J Drupal Connector

The module attempts to connect Drupal with the Neo4J database. It is a concept module, the end goal is not yet finalized.

The problem

Drupal mostly relies on traditional databases, which performs badly at certain conditions. Imagine you have lot's of references. Your interest is to know (let's say) which node has a certain field value that is connected to another node - no matter how deep is the connection. Or another example, you're on a node interested in which other nodes has similar characteristics (by having similar field values or connect to the same contents). There queries are hard to describe with a relational - or even with a traditional no-sql database. That's where Neo4J and the graph database plays an important role.

The solution

This module doesn't intend to change the backend to a graph database, it doesn't serve Drupal as a whole. In fact it's an overlay. It maintains all entities with certain properties which you can select as well as their field data. Then you can create queries against the graph database (directly to the graph db engine or through views) and filter your content. So you only query it when you need graph query, then retain the content IDs and use that to present content or feed Views with it.

What the module does?