Unsupported

This module allows single sign-on to Drupal using external HTTP authentication. Current version only supports basic authentication method and users must have matching REMOTE_USER header from external system and in Drupal username. This means you will have to manually manage both Drupal users and user accounts on your external system. Future versions of the module may include option of automatically creating new users to Drupal with preset user roles.

The module is intended for running a intranet site that is fully protected with HTTP basic authentication or a separate admin site from your public Drupal site. Connections to the admin site should be SSL encrypted and it can use any external system for authentication. Usual configuration on public sites is to redirect all admin pages to the admin site and possibly also require a VPN connection to access the admin site.

This module will allow Drupal to replace textarea fields with the CKEditor 4 - a visual HTML editor, usually called a WYSIWYG editor. This HTML text editor brings many of the powerful WYSIWYG editing functions of known desktop editors like Word to the web. It's very fast and doesn't require any kind of installation on the client computer.

What is CKEditor?

CKEditor is the far superior successor of FCKeditor. The editor has been rebranded and completely rewritten. It is now much faster (the code has been optimized), loads faster (the number of files has been reduced, so the browser will perform less HTTP requests) and developer-friendly.

Useful links

• CKEditor 4 project page
• CKEditor SDK – CKEditor 4 features explained with live examples
• CKEditor 4 documentation
• CKEditor 4 features documentation

Background

In some cases, it is required to allow users to claim authorship of a particular node.

For example:

• (original motivation of this module) After running Path Copier, you want users to find their nodes and claim authorship and then modify the node themselves.
• ... ...

Introduction

Allow registered users to claim authorship of a particular node. The module will store the history of who have made claims. Site administrators can set who can make claim.

How it Works

The process of claiming a node is as follows.

1. A node of a type that can be claimed is made by AUTHOR
2. Node is viewed by USER, WHO has a role with permission to claim
3. AUTHOR gets (optional) email notification about the claim.
4. AUTHOR navigates to node and approves (via approval link) ownership change. If there are multiple claims a table of past claims will be displayed
5. USER now is the author of the node

To-do:

Below are features that seem to be incomplete in the existing release or are planned features for the future of Claim Node Ownership.

To Finish:

• Allow registered users to vote on if a claim is legitimate
• Allow registered users to report a spam claim to administrator

This feature and many other checkout improvements are available for 6.x in the Ubercart Checkout Tweaks module.