Look at Image Editor module first - it has all the functionality of this module and more.
Bring Photoshop-like functionality into your Drupal website! Meet Pixlr power - create/edit any images online in the powerful and feature-rich image editor and save resulted images back to your site!
This module tries to detect whether a website is running on a LAN or on localhost and if yes, outputs tiny message warning a user about this.
Useful in cases when a locally running website is accessed via real domain name.
Module uses hook_boot() to startup and thus is not cached.
CSS style of the message and message text is configured in admin/settings.
The decision whether a website is running locally is made by IP address tests.
This simple module acts as a bridge to integrate the DrupalChat module in the Tray.
OpenLayers Proximity enables geographical proximity search for the OpenLayers module (6.x-2.x). The module exposes a filter to the Views module where users can specify starting point and radius of the proximity search. The starting point can be specified by simply providing the name of its location. Search radius can be given in kilometers or miles and it's easy, for external modules, to specify their own units of measurement.
The module changes the behavior of apachesolr and allows for extending / overriding the SolrPHPClient behavior.
As of now, it writes the index to a directory rather than posting it to the Solr server.
This module replaces the jQuery served from your Drupal site with a copy served from Google's Libraries API: http://code.google.com/apis/libraries/
The module adds an option on the Performance form to use Google's jQuery.
Nodefeedback provides a form on the node view pages to answer/vote on custom questions. It should be useful for Knowledge Base / Wiki sites and/or some others needing users input on the content.
Supported question types are:
- radio buttons (answers are stored in the Voting API DB as the votes on the question tags)
- text-areas (answers are stored in the custom table).
This module provides a themed function called "get_exposed_filter_output()" which print out the values of the exposed filter used in a view.
This can be useful in the view header, in case the exposed filter is in a block, but there is a need to show the user according to what filter he got the results.
The idea is based on the discussion - #658566: Use data from exposed filter in title or header.
This module helps you find views that use a given content type.
The fingerprint module uses features to make configuration dumps for Drupal, a bit like the crash report with all the settings that you can get from most desktop software. But fingerprint is more than that: it exports all the settings in XML which makes it easier to read and search your sites' configurations. The tool is not for importing or making backups, but it gives you the ability to search similarities and differences between Drupal site. Amongst others you'll be able to use it to:
