Content editing experience

Description

Vote defines a new entity type (vote). Votes can be cast on ANY entity type that "your drupal" knows (even on "vote" itself).

Vote provides "functions" and "voting types":

A function basically provides a handler which defines how and where a function stores its result values. Each function can have its own db table to store the results in order to allow more complex functions to break the INTEGER barrier which the default result table uses for its results.

A voting type basically combines a group of functions. For example a voting type "percent" would combine the functions "average" and "count" while "points" would also use the "sum" function.

Voting types and functions both use a set of classes as handlers to provide custom option forms and advanced (and individual) functionality for each function / voting type. The functions handler -for example- makes it possible to store function result values in seperate db tables with different table structures.

Edit Limits adds certain limits to editing nodes and comments. This can set the number of times a node can be edit.

Input filter for referencing git commits. Ideally this would be used on d.o

Description

A module suite providing extensible, configurable and fast typeahead ability for the core search. Also it might be used as an API.

Disclaimer

This module is in an early development stage, It is not intended to be used in production.

Installation

• Enable the module as usual.
• Goto admin/settings/search/autocomplete & configure your sense!

Develop a Searchsense Provider

• If required, Alter Searchsense's administration form by implementing hook_form_searchsense_admin_alter().
• If required, attach proper form validation and submission callbacks.
• Implement hook_searchsense() and return a provider-id-keyed array of keyed suggestions, if you want to extend its suggestions.
• Implement hook_searchsense_alter() if you're interested in modifying the suggestions.
• Checkout submodules for code examples.

API usage example

<?php
/**
* Implements hook_searchsense().
*/
function nodesense_searchsense($a1 = '', $a2 = '', $limit = 10) {
$matches = array();

if ($a1 && ($query = variable_get('nodesense_query', FALSE))) {
$results = db_query_range($query, $a1, 0, (int) $limit);
while ($result = db_fetch_object($results)) {

Description

The module tracks recently viewed nodes for both anonymous and authenticated users.
It provides an API function for others to get a list of recently viewed items and also defines a configurable recently viewed items block. You might want to make use of the recently_viewed_views submodule which provides a customised default View to benefit the endless flexibility of Views.

Also if Ubercart module suite is enabled, there's another useful submodule named recently_viewed_products which adds an another default view for UC specific products with the same said functionality.

Disclaimer

This module is in an early development stage, It is not intended to be used in production.

Important notice

Since the module initiates sessions, it's incompatible with Varnish Cache.
In future releases there might be an option to work with cookies instead of sessions addressing this issue.

Recommended modules

Here is a list of recommended modules to be used with "Recently viewed views integration" and "Recently viewed products" submodules:

• Views Argument Sort
• Semantic Views

Wysiwyg Fields is an Inline field management system, a module that bridges the gap between Drupal fields and CKEditor, giving the power of Drupal's field system via the simple usability of a CKEditor dialog.

What that means is that Wysiwyg Fields allows for any Drupal field to be embedded directly into CKEditor and behave as a native CKEditor plugin, removing unnecessary clutter from your Drupal entity forms.