OpenLayers Heatmaps
Component type
Categories
Maintenance status
Development status
Downloads
Component created
Component changed
Overview
This module allows you to create Heatmaps layers through the Openlayers module.
This module allows you to create Heatmaps layers through the Openlayers module.
This project has been deprecated if favour of Facet API Bonus. All features of this module have been transfered.
Keep content clean!
TextCleaner is a simple module aimed at keeping content clean of empty HTML tags.
The best example for using this module would be if you have Fields that are HTML formatted with WYSIWYGs. WYSIWYGs sometimes insert empty HTML tags that can make your content look messy.
For example, the following markup can be seen in a variety of WYSIWYG output(s) and difficult to remove for the end-user (from a WYSIWYG UI):
Allows for customers to take over a seller-created order and pay it.
This approach takes commerce to a more traditional seller's perspective, where a seller wactively contacts customers for sales, and te customers use their credit cards.
By adding ability to send a tokenized login mail from the admin order payment ui, you can allow for the customer to pay for their own (heavily discounted?) order, even if they have no account.
The seller:
Then the customer:
Twitter pull in is a small and light module.
This module allows to feed nodes with tweets from a twitter account.
The fields attached to the node are :
The customizables fields in admin pages are:
This module allows to render breadcrumbs according to a hierarchy of nodes defined via node reference fields.
This module adds a method for sending preconfigured, tokenized per-nodetype SMS messages from nodes. Message structure are configured in admin, and cannot be changed by the end user.
Features:
Turns out this module already exists. It's called Environment Indicator by mrfelton. Thanks to stella for pointing that out in #1398060: environment indicator module.
I'm therefore retiring this project.
[NOTE: This module has been deprecated as of June 2013 in favor of Cache Expiration. If you're currently using Boost Expire, please follow these directions to switch from Boost Expire to Cache Expiration on your site!]
A cache expiration module to go with Boost for Drupal 7.
Currently, Boost for Drupal 7 doesn't do any active cache expiration (see #1069438: How to Flush Boost Cache in Drupal 7.x), and this means that when you update a node, post a comment, etc., Boost will continue serving stale content from its static HTML cache until the file is finally cleaned up on a cron run.
For many sites, especially smaller sites where content is updated infrequently and cron may be run hourly or even less frequently, this means stale content will be served for quite some time, unless someone visits the Performance page and clears all the site's caches manually.
This module alleviates that problem by simply flushing Boost's static HTML cache every time a node or comment is posted or updated. You can set the module to respect your site's Minimum cache lifetime so it doesn't flush the cache until the minimum lifetime has passed.
This module may become deprecated in favor of a more universal solution (like Boost integration with the Cache Expiration module).
This is a nasty hacked up version of apachesolr for D7, don't use!