Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
This module provides a way to autosave data entered in any Drupal form without actually submitting the form, which helps if the user is writing an article or a comment and the browser crashed or th
NOTE: If you'd like to log via Redis, check out my custom version of log4php on Github.
Overview
This module is designed to centralize the logging functionality of Drupal into a single module replacement for watchdog, reducing the overall burden of maintaining Drupal modules simply to support multiple watchdog backends. Apache log4php is a common-purpose library that allows messages to be logged to a wide variety of backends and provides much more granular control than Drupal's built-in capabilities.
Apache log4php™ is a versatile logging framework for PHP.
Feature highlights:
Configuration through XML, properties or PHP files
Various logging destinations, including:
Console (stdout, stderr)
Files (including daily and rolling files)
Email
Databases
Sockets
Syslog
Several built-in log message formats, including:
HTML
XML
User defined pattern
Features
This module provides simple integration with the Apache log4php library.
This module allows the single-sign-on system provided by the Bakery module to be optional, rather than required for all users.
Users who first create an account on the Bakery master site will be able to visit the slave sites have their account information and sessions propagated (just like they normally can on sites using Bakery). However, users who try to register on the slave site will be allowed to create a completely local account.
This is useful in situations where, for example, site administrators are required to have shared accounts spanning multiple sites, but regular end users should only be able to create accounts on a single public-facing site. It is similar to other optional single-sign-on systems (for example, OpenID) in that respect, but the user experience is simpler all around.
How to use it
Configure the Bakery module as you normally would. (This module depends on Bakery being enabled and configured correctly in order to work.)
On the slave sites where you intend to enable this module, grant all authenticated users the Bakery module's "Bypass Bakery" permission. (Make sure you are aware of the implications of doing so; for example, users with shared accounts will not be automatically logged out of the slave site when they log out of the master site.)
Welcome to Grassroots Interests.
As the name suggests get you the common interest out of specific keyword.
The GI Search module adds the extra functionality to the search displaying the common term or URL you wish to focus when a certain "keyword" is searched. This module is not dependent on search but it takes the argument passed in URL to match with the manually entered keywords, bind them with title and URL of our choice, within the site or some external URL.
Thus purpose of this module is to enhance user search experience.
By providing binding of as many keywords as we want to a URL.
Features
* Enhances user experience in search without interfering the search.
* Works with default drupal search, Apache SOLr search ... etc.
* Only dependent on URL arguments.
* Manually added keywords to add more sense to search.
* Give clue to user about the trends followed throughout the website.
* Super light adds no extra load.
* Can also be used for featuring some specific URL where you want user
to have a look.
* Any number of keywords can be added using a user friendly interface.
* Using panels plugin can be placed anywhere we want to show suggestions.
* Developers can write there custom block using the functionality provided.