Provides field_get_value(), field_get_values(), and field_set_values() functions for developer and themer use.
Developers and themers expect to constantly type some form of $entity->field_data['und'][0]['value']; throughout site customization modules and themes. It gets tedious, the code can be difficult to read, and you find yourself staring at the output of devel's dsm() far too much.
D6 port of Guiders-JS.
The purpose is to integrate this port back into Guiders-JS module.
D6 needs a slightly patched version of guiders.js library due to outdated jquery version included in core. You can download the patched guiders.js library here https://github.com/mwsam/Guiders-JS while I'm trying to get it included in original repo.
CRM Core is a set of modules for managing contacts, activities and relationships within your Drupal website. It is designed to provide a basic framework for managing these items and interacting with other components of Drupal.
CRM Core allows you to manage contacts, activities and relationships in your Drupal website. It provides extensive support for these entities, and includes a number of tools to make them easier to support in your Drupal website.
In addition to these basic features, CRM Core integrates with a number of other components within Drupal, including views, VBO, ctools, rules, solr, services, field api and search api.
Why use CRM Core?
An extensive discussion of why you would want to use CRM Core can be found in the handbook. This page details the design philosophy behind CRM Core and other things to consider when trying to make the case for why you would want (or not want) to use it.
Daemonize a cron job making it able to run continuesly.
Many times you need to implement hooks to alter the behaviour of an existing module. One option would be to open the module file and alter the behaviour. However this approach is not upgrade proof i.e. when you upgrade the module, the code is lost. The other alternative is to write a new module everytime to want to change the behaviour.
Block Sections allows blocks to display different content depending the current path. This way there is no need to create multiple custom blocks in order to vary the content of them.
A possible use case for this module is when a block contains advertisements. With Block Sections the ads can be specifically targeted for different sections of the website:
This simple module simply lists all Features-Exportable components that have not been exported to a feature. The output can be copied into any of your Feature modules .info files for quick and easy re-creation.
For developers, it will help you to see what pieces of your Drupal site are not yet exported to code via the Features module.
Views Expanded provides Views style plugin that can mimic Mega menu functionality in Drupal.
There are already some implementations of Mega menu but they are mostly based on menus or blocks which lack flexibility provided by Drupal.
So what's special about this module?
Views Expanded allows you to display any entity as expanded content. Along with Display Suite and Views attach modules this can allow you to put in there almost everything. Think of images, subcategories or argument driven Views! Yay.
This project is a first small step in an attempt to do something similar to
what is found at the Khan Academy (khanacademy.org).
This first step allows for setting up Rules components used for evaluating an
answer towards a given correct answer, in dynamic ways. It contains:
* A new entity type, "Question". It is used to store questions, and descriptions
of answers (either in exact form or in lists of answer alternatives).This module adds an action wrapping of drupal_http_request() to use Rules for making HTTP requests. It has many general uses, because the Hypertext Transfer Protocol is the foundation of web data communication.