Maintenance fixes only

How it works

The ApacheSolr SEO blocks provides some extra blocks that improve the user
experience of filtering and the positioning of the ApacheSolr pages result of a

Overview

Date Reminder allows a registered user to request an email reminder to be sent at a specified time before an event. Generally these would be calendar events, but any node type that has a CCK datetime can support reminders.

Features

• When reminders are enabled for a node, registered users (with the appropriate privilege) can request reminders to be sent before each occurrence of the date/time. The user specifies how long before the date/time to send the reminder.
• When reminders are enabled for a node type, anyone who can edit the node can enable or disable reminders for that node.
• Reminders are sent using the Messaging system. The usual reminder method is email, but other messaging transports should work. (Well, not Drupal 7. The Drupal 7 version just uses straight email.)
• System administrator can control:
  • Which node types allow reminders, and which date field (if there are several) in a type to use as the basis of reminders.
  • Which (registered) users can request reminders.
  • Which users can request reminders to arbitrary email addresses instead of their own.
  • Which users can see or administer other users' reminders.
  • Content of reminder messages.
  • If and how long reminders should be kept after last date occurrence.
  • The list of allowed lead times for reminders from which users can select.

An effort is under way to move much of the documentation here to the Date Reminder section of the Site Builders Guide. Currently that document is very incomplete, but watch there. Information on this module page will gradually be moving there.

OpenLayers Quick Query: Have you tried using geofield with openlayers_views and a map with 5000 nodes? No? I have and the result is: 280 MB, 2 min load time and all nodes are loaded into memory. But slow is not the entity_load, but the field_attach. With this short module and some custom code you can easily make your layers fast again:

Example

function hook_openlayers_quick_query_info($view) {
  if ($view->name == 'my_map') {

    // Add wkt field information
    $info['wkt_field'] = 'field_geolocation';

    // Add needed fields
    $info['fields'][] = [
      'field_name' => 'field_geolocation'
    ];
    $info['fields'][] = [
      'field_name' => 'field_other',
      'additional_fields' => TRUE,
    ];

    return $info;
  }
}

For a complete example see openlayers_quick_query.api.php.

Explanation

pjax is a jQuery plugin that loads new content into the current page without a full page load. This is usually quicker and smoother than a full page reload, because Drupal only has to deliver the main page content and not the full page – and the browser only has to redraw a smaller amount of markup.

In addition to this, pjax updates the page URL with the proper page path using HTML5 pushState – not with #url-fragments that are commonly used with ajax-loaded content. It also updates the page title with the title of the loaded page. In other words, it has all of the benefits of standard page loads (permalinks, SEO), while taking advantage of partial page loads in the browser.

Browsers that don't support pushState – specifically IE < 10 – will automatically fall back to full page loads. In other words, nothing will break, but the module will not provide any benefits for those browsers.

For a quick example of this technique, see the original pjax demo. A more elaborate example is Github's project file browser.

Just a fserver sandbox project

Changes

Changes and patches to original fserver

Creates a RuTube PHP Stream Wrapper for Resource and implements the various formatter and file listing hooks in the Media module.