Maintenance fixes only

VBO Hide module helps to not show the views bulk operation form
when there is no data in the view.
It simply removes the view bulk operation form when no data.

Add the X-Originating-IP header to all outgoing emails to assist with investigation of the sources for spam and unsolicited bulk email.

A standard Drupal install sends email as if it was originating from the web server when in fact, the email originated with a person's web browser. Use this module to include information in the outgoing email header about the IP address of the person who submitted a request to a Drupal website.

Without this module, Drupal effectively becomes an anonymizing service because the standard email headers will have the email origin listed as the web server IP address instead of the user elsewhere on the Internet. By using the information from X-Originating-IP, you can track down individuals who send undesirable communications through contact or webforms.

X-Originating-IP: [xxx.xxx.xxx.xxx]

The originating IP is based on the ip_address() Drupal API function.

If Drupal is behind a reverse proxy, we use the X-Forwarded-For header instead of $_SERVER['REMOTE_ADDR'], which would be the IP address of the proxy server, and not the client's. The actual header name can be configured by the reverse_proxy_header variable.

Name: Views content breadcrumb
Description: Create breadcrumb for view page and panel_pane display.
Drupal 7

A jQuery based agegate module which works on date of birth.

No settings yet but number of years and timezone offset can be configured in agegate_dob.js

Postal code, locality or administrative area filtering functionality for the Drupal Commerce orders. This module provides 2 main modes (whitelisting and blacklisting) which allow shop owners to restrict the areas of a country that they deliver to.

Cookie-Aware Page Cache module extends Drupal core's default database cache to key page cache entries by cookie in addition to URL.

You may need this if you are preparing different markup for pages depending on the value of a user's browser cookie, and the default database cache is the only caching mechanism available to you. For example, you may be displaying local information on a user's favorite store location, which is kept in a cookie. Or you might be using Context Breakpoint module, which uses a cookie to pass information about the user's screen size to use as a condition in the Context system.

You can specify more than one cookie to take into account when querying the page cache. However, you should only select cookies with limited sets of possible values. The performance benefits of page caching decrease as the number of possible cookie value combinations increases.