Extend and customize Drupal functionality with contributed modules.
If a module doesn't quite do what you want it to do, if you find a bug or have a suggestion, then join forces and help the module maintainer. Or, share your own by starting a new module.
A small module to provide third party integration with Chartbeat, for real-time site monitoring statistics. Note that the module currently just reports to Chartbeat. If you would like to do more with it, then please get involved in the issue queue.
This module provides "like" and "dislike" widgets for contents inside Drupal, making it easiers to promote features as the one seem on many social network websites.
Technically speaking, the module provides 2 tags for Voting API, "like" and "dislike", working in a different way from Vote Up/Down, that is like a "plus or minus" approach. Likes are separate from Dislikes here.
Drupal Computing is a framework that facilitates distributed computing between Drupal and external programs written in non-PHP languages such as Java and Python. It is particularly designed for the cases where you need to use Drupal with non-PHP, computational-intensive code libraries (such as Apache Mahout, NumPy/SciPy, R, etc) for offline big data analytics. In addition to this Drupal module, you also need the companion Java and Python client library at https://github.com/danithaca/drupal-computing. The target audience would be developers who write Java/Python programs for Drupal.
The Keyword Analysis module uses an open source algorithm that extract keywords on your Drupal server without needing to connect to a 3rd party API. Via the Content Analysis UI it can be used to extract keywords from node content, from any URL or from a text field.
The module was design to be a quick analysis to seed the Keyword Research module. It is recommended to use both in conjunction with each other.
In order to use this module you must download the free autokeyword.php class. Place the file in a subdirectory named "lib" so that you have:
The module connects any Drupal 7 site with drupalmonitor.com. As the name says, Drupalmonitor is a tool to actively monitor Drupal sites. It's not only a "heartbeat" kind of monitoring. It's much more powerful. Using the drupalmonitor connector, the tool can gather data from the drupal site like how many users, nodes, last cron run, page requests, etc. On drupalmonitor.com, the data will be processed and shown in graphs over time.
Quant provides an engine for producing quantitative, time-based analytics for virtually any Drupal component. Quant takes raw data about normal Drupal actions, such as node creation, and plots the activity over time, with the selected time being configurable. See the screenshot provided for a better understanding.
Enabling the recording and presentation of statistics for the Search API module. There are plans to implement usage and performance statistics in the near future. For now this module gives your Drupal site a top search phrases block for all the Search API indices on your site.
Visitors find your site with a search engine. Are you interested in what they were searching for?
Search Engine Referers is a simple module to view the search engine queries used by your visitors. It parses the referer URLs of popular search engines in you access log and extracts the search queries. Currently supported: Google, Yahoo!, Live.com, Yandex.ru, Rambler.ru.
This module logs user login activity for every user on a Drupal installation. This can be used to provide important user information about when and from where their user account was used to login to the website. If a user notices unusual activity, the user might take required action to protect the account from getting compromised.
The module logs the following information about a login activity;
IP address of the host being used for the login activity.
Further, it also provides a report page at admin/reports/login_activity where login activity related information of all the users is displayed in the form of a report.
I have started to port User Details to Drupal 8. Keep an eye on D8 port issue for more info.
If you are reporting a issue please make sure to give as much information as possible so I can re-produce the issue.
The "User Details" module comes with two blocks, "User Detils: logged-in user" and "User Details: authored user".
The idea for "User Details" started as a request from an end-user, to have a centreal place for quick links to important locations on the website.
For Drupal 6 this was just some custom code you could add to a custom block.
For Drupal 7 the "User Details" module has expanded to its own module, which allows non-coders to alter and customize to thier liking.
The "User Details" module is a basic collection of user data (or variables) and commonly used links in a block. In no way is this a required part of any website, only for the ease of naviagtion.
Below is a list of all the stats and links that can be turned on as part of the "User Details" blocks.The links come with some default images, but you can change these by uploading an image to your web server and typing in the location for each image.
There are just some things that you need to know immediately upon conversion; you can't wait to see it in your Google Analytics / Piwik / etc report. This module is that missing piece to the puzzle that tracks important information about your website visitors at the time of conversion. It also exposes that information with tasty little tokens that can be used virtually anywhere. It does the tracking in three separate cookies and exposes that information in 6 tokens.
This project introduces a vendor independent framework for deeply monitoring Drupal and all its projects / modules. It provides a 360 degree perspective on Drupal system health, being a critical piece for true enterprise Drupal platforms.
Our goal is to make monitoring an affordable and well established standard feature. These days, every website is somehow mission critical and the era of lazy-/unmonitored enterprise applications need to have an end.
With this vendor independent definition, we recommend every contrib module to provide own sensors that allow us to measure module health by default.
The project monitoring is no monitoring application on its own. It provides a lightweight sensor definition framework with a set of sensors that can be collected by any monitoring product. Integrations into the most popular Open Source products Nagios / Icinga (monitoring system) and Munin (trends monitoring grapher) will be available out of the box. Integrating additional monitoring products is easy.
The base platform for sensor definition is production ready. Publishing of the integration into products and contrib modules will follow soon. Contact us if you need it NOW and want to support development.
There are no known major issues.
This module provides the display of AWStats web statistics data (generally collected from web server logs).
The BAWStats module integrates the third party betterAWStats system into drupal. The betterAWStats project is a PHP library and CGI that displays AWStats web statistics data in a convenient and customizable way.
In a nutshell, the LimeSurvey Sync module is a powerfull survey module on Drupal integrating in a user-friendly way the best free open source survey software : LimeSurvey.
Compared to the well known webform module : this module does everything that webform does and much more.
manage answers as nodes (allowing to manage access to answers),
store revisions (older versions) of answers,
make graph results availables,
manage huge surveys,
LimeSurvey Sync V3
The LimeSurvey Sync v7.x-3.x handles LimeSurvey datas as Entities (not nodes anymore).
All LimeSurvey datas are availables from Drupal. If your start using the LimeSurvey Sync module, you should use this version.
Because of the significant new structure, there is no update script from 7.x-1.x. If you want to upgrade, you should do it as a fresh new start. More information on the V3.
This version has a dependency to the Customizable entities module