Drupal (contributions)

This is a low-level API for implementing A/B tests in code. Its design is based on the excellent A/Bingo for Ruby on Rails, written by Patrick McKenzie. PLEASE NOTE: This module doesn't provide a UI for creating tests - they must be created in code. ... [More] If you're looking for module to create A/B tests in the UI check out Multivariate. Unfortunately, the Multivariate module isn't good for creating tests in code or that involve a lot of code. For example, let's say you're writing a custom module and you want to test two variations on a custom form. The A/B test module will allow you to do that with only two lines of code! Super quick tutorial Showing your two variants: if (abtest('mytest')) {  // the first version}else {  // the second version} Tracking conversion: abtest_track_conversion('mytest'); [Less]

Blocks the user from using a site until they confirm they are old enough to access it.

The new module known as ProjectUS must allow to manage clients, projects, tasks and time reports, in such a way that a monitoring of asigned tasks and project evolution can be easily made. The chosen platform is fruit of Overtus commitment with open ... [More] source software and, as the company sees it, is a way to give the community back some of that big effort that provides us with so many benefits. The tools for project management are mainly thought for the English-speaking community, that's why it is hard to adapt it to particular non-English-speaking processes. In addition to this, these tools are still not available for Drupal 7.0 and so, they probably won't be either in the next Drupal 8.0 which is comming very soon. The module will be registered under GNU license (v2.0), so that everybody can make his/her modifications on it. Analysis and development stages will take place inside the company and the final results will be released in the official version, where hopefully we could contribute to the community with another tool for project management. Areas considered: Clients management Projects management Tasks management Time report management [Less]

Helps search_api module to correctly push the data from the current site to the central solr index.

Fetches results from different DBs according to the domain and nid.

A small module to modify node teasers. It removes anchor tags from node teaser, or replaces URLs with node path, or replaces anchor tags with span tags with specified CSS class.

Rethinking watchdog(): logging in Kohana 3 Frederic Marand Sun, 2012-11-04 11:27 Read more about Rethinking watchdog(): logging in Kohana 3 2 comments Add new comment Continuing this exploration of logging solutions used in ... [More] various projects, let's look at logging in Kohana 3. While Monolog and log4php share a mostly common logging model of a frontal Logger object instantiated as many times as needed to supply different logging channels, in which log events are Processed/Filtered then written out by Handlers/Writers, Kohana builds upon a simpler model, which can be summarized by three patterns: Singleton: there is only one instance of the Kohana Log Observer: Log_Writer instances are attached (and detached) to(/from) the logger instance and handle events they are interested in based on their own configuration. Much like a Drupal hook, all writer instances receive each Log event Delegation: the Log exposes a write() to trigger the buffered writing, but does not implement it itself, but delegates to the Log_Writer objects to perform it. Buffered logging control is a Log property, not a Log_Writer property. [Less]

Rethinking watchdog(): logging in Kohana 3 Frederic Marand Sun, 2012-11-04 11:27 Read more about Rethinking watchdog(): logging in Kohana 3 2 comments Add new comment Continuing this exploration of logging solutions used in ... [More] various projects, let's look at logging in Kohana 3. While Monolog and log4php share a mostly common logging model of a frontal Logger object instantiated as many times as needed to supply different logging channels, in which log events are Processed/Filtered then written out by Handlers/Writers, Kohana builds upon a simpler model, which can be summarized by three patterns: Singleton: there is only one instance of the Kohana Log Observer: Log_Writer instances are attached (and detached) to(/from) the logger instance and handle events they are interested in based on their own configuration. Much like a Drupal hook, all writer instances receive each Log event Delegation: the Log exposes a write() to trigger the buffered writing, but does not implement it itself, but delegates to the Log_Writer objects to perform it. Buffered logging control is a Log property, not a Log_Writer property. [Less]

Rethinking watchdog(): logging in Kohana 3 Frederic Marand Sun, 2012-11-04 11:27 Read more about Rethinking watchdog(): logging in Kohana 3 2 comments Add new comment Continuing this exploration of logging solutions used in ... [More] various projects, let's look at logging in Kohana 3. While Monolog and log4php share a mostly common logging model of a frontal Logger object instantiated as many times as needed to supply different logging channels, in which log events are Processed/Filtered then written out by Handlers/Writers, Kohana builds upon a simpler model, which can be summarized by three patterns: Singleton: there is only one instance of the Kohana Log Observer: Log_Writer instances are attached (and detached) to(/from) the logger instance and handle events they are interested in based on their own configuration. Much like a Drupal hook, all writer instances receive each Log event Delegation: the Log exposes a write() to trigger the buffered writing, but does not implement it itself, but delegates to the Log_Writer objects to perform it. Buffered logging control is a Log property, not a Log_Writer property. [Less]

Rethinking watchdog(): logging in Kohana 3 Frederic Marand Sun, 2012-11-04 11:27 Read more about Rethinking watchdog(): logging in Kohana 3 2 comments Add new comment Continuing this exploration of logging solutions used in ... [More] various projects, let's look at logging in Kohana 3. While Monolog and log4php share a mostly common logging model of a frontal Logger object instantiated as many times as needed to supply different logging channels, in which log events are Processed/Filtered then written out by Handlers/Writers, Kohana builds upon a simpler model, which can be summarized by three patterns: Singleton: there is only one instance of the Kohana Log Observer: Log_Writer instances are attached (and detached) to(/from) the logger instance and handle events they are interested in based on their own configuration. Much like a Drupal hook, all writer instances receive each Log event Delegation: the Log exposes a write() to trigger the buffered writing, but does not implement it itself, but delegates to the Log_Writer objects to perform it. Buffered logging control is a Log property, not a Log_Writer property. [Less]