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.
Boost provides static page caching for Drupal enabling a very significant performance and scalability boost for sites that receive mostly anonymous traffic. When there is no problem with your file system performance it is a good solution for shared hosting.
Since Drupal 8+ Version of this module Boost can serve cached content from files directly via RequestEvent independent from the used webserver. But it is still a good idea to use the webserver for serving static files. In this case there is even no PHP involved to serve content and get the maximal boost.
The 6.x-2.0-alpha3 release (and later) require the PHP cURL extension.
Overview
This module provides an interface to PayPal using Instant Payment Notifications (IPN). It currently supports paid memberships (subscriptions), donations (tip jar) and paid adverts (classified ads).
lm_paypal is not a generic payment processing module. If you want a more complete commerce system, suggest you look at ubercart or ecommerce.
LM Paypal now consists of four modules:
lm_paypal which handles talking with PayPal, receiving, validating and processing PayPal IPN messages. To use the other modules this module is required.
lm_paypal_donations which works with lm_paypal to provide donation buttons ("tip jar")
lm_paypal_subscriptions which works with lm_paypal to provided paid role memberships. If Organic Groups is installed then OG subscriptions can also be created.
lm_paypal_paid_adverts which works with lm_paypal and lm_paypal_subscriptions to allow any node type to be flagged as requiring payment to be published. Articles created with these flagged node types are only publically viewable once paid for using an admin configured paypal subscription. This provides a "classified ads" system for Drupal.
Update: For Drupal 8 please use the redirect module. This project is deprecated for D8
What?
GlobalRedirect is a simple module which…
Checks the current URL for an alias and does a 301 redirect to it if it is not being used.
Checks the current URL for a trailing slash, removes it if present and repeats check 1 with the new request.
Checks if the current URL is the same as the site_frontpage and redirects to the frontpage if there is a match.
Checks if the Clean URLs feature is enabled and then checks the current URL is being accessed using the clean method rather than the 'unclean' method.
Checks access to the URL. If the user does not have access to the path, then no redirects are done. This helps avoid exposing private aliased node's.
Make sure the case of the URL being accessed is the same as the one set by the author/administrator. For example, if you set the alias "articles/cake-making" to node/123, then the user can access the alias with any combination of case.
Most of the above options are configurable in the settings page. In Drupal 5 you can access this after enabling the globalredirect_admin module. In Drupal 6, the settings page is bundled into the module.