Actively maintained

Description

This module enables the website to permanently store the access tokens
that the module fboauth retrieves from Facebook when the user grants access
to the application that fboauth is managing.

Usage

Once the module is enabled, each user will have a page at /user/UID/fboauth
that allows the user to grant the application all permissions required for all
actions declared in the hook_fboauth_actions implementations.

This allows any module that uses fboauth to use the stored token to perform
calls to facebook's api without having to redirect the user to FB (which is the
behaviour fboauth uses), or even without having any interaction from the user
(ie: from hook_cron).

This is useful when a module wants to perform a call to Facebook on behalf of
a user but it is not possible to use the normal workflow of redirecting the
user to facebook to get a valid access_token.

// Retrieve stored access_token for the current user.
$access_token = fboauth_tokens_get_user_access_token();

// Call facebook api.
$params = array(
  'message' => 'Hello world',
);
$result = fboauth_graph_query('me/feed', $access_token, $params, 'POST');

The module does not provide any facility to know if the provided token is still
valid.

So if your call to fboauth_graph_query() returns an error, your module will be

The device detection module uses the WURFL Cloud Service (http://www.scientiamobile.com/cloud) to identify the visitor's device, and

This project is based on this issue: #844944-46: Live preview of what the URL will be in the field.

From the person who wrote the patch:

Here's an approach that uses AJAX, so that it works for any token pattern without exposing the token structure to the client-side code. Whenever any form element is changed, the "live preview" is marked as needing an update, and via css, becomes grey. An AJAX request to update it is only triggered when the preview element is visible, so that if its vertical tab isn't currently open, we don't generate needless round trips to the server.

Credit for the original code goes to effulgentsia

Currently, this module creates a preview URL, which can be edited by the user. The thing that makes it a little hard to use, at the moment is the fact that URL Alias settings don't seem to be able to be moved out of the vertical tabs without some code. If you want to move the URL alias settings out of the vertical tabs, so you can have them under the title, for example, then you would need to create a custom module with the code below:

<?php
function MYMODULE_base_form_alter(&$form, &$form_state, $form_id) {
if (isset($form['#node_edit_form']) && $form['#node_edit_form']) {
$form['path']['#group'] = '';
$form['path']['#title'] = '';

Combining some patches.

Goal of this module is to allow a user to interact with documents they have stored in Google Drive

Domain Toolkit
==================================================
Domain Access is used to create multiple domains and grant user access
to this domains. For the D7-Version of Domain Access, there are some
contributed modules missing (e.g. hierarchical domains, inherited
permissions, …). This features are implemented by custom modules,
bundled in domain_toolkit.

Relationships
==================================================
Domains
----------------------------------------------------------------------
Every domain has a parent (or -1 for the root element) domain. This
relationship is saved in the domain table for every domain.

Users
----------------------------------------------------------------------
Every user is assigned to one or more Domains. This assignment stands
for the ability to manage the structure of elements (menus, …) of this
domain, creating content FROM this domain and publishing content TO this
domain and it's children.

Content
----------------------------------------------------------------------
Every node has one source domain and one or more publish domain(s). The
source domain is the domain, the node was published from. Editing &
deleting this node can only be done from the source domain (**ATTENTION**:
This differs greatly from the original Domain Access behavior!). Because