This module adds PHP-based password strength checking and validation
routines that mirror the jQuery routines, so that administrators can
restrict passwords to only be, for example, "high" strength. The module
simply modifies existing password confirm fields (where two passwords
are entered, like the user edit form), so no other setup is required
beyond configuring the desired enforcement rules.
ok landry@
is a configuration file, even though it's buried deep in code
directories. Pointed out by Tobias M. Boelz <tmb at usta dot de>.
Thus, use @sample and bump.
OK espie@ stephan@
fixes a session reuse issue even though this release has not been tagged
as 'security relevant'. Details at http://drupal.org/node/967244.
Make sure you upgrade all files while you're logged in (or have access
to settings.php) otherwise you'll lock yourself out pretty easily, in
case you use Captcha for logins. Database upgrade required, too.
- install drupal modules/themes as root:daemon rather than www:www
(only the files/ directory needs to be writeable by 'www').
- don't install 'settings.php' world-readable since it contains the
DB password. Use 640, owner 'www' instead.
- bump all modules.
tested in production, including upgrade szenarios.
ok sthen@ and landry@, maintainer timeout.
This group of modules is sort of a recipe module that makes things
easier by showing how to integrate some other modules as well as
providing miscellaneous features that aren't distributed by Views
itself. Sometimes these modules are only base recipes that will
need to be themed and spiced up to fit your needs.
Ubercart is an e-commerce suite developed for Drupal. It has been
designed with the end user in mind, focusing on usability in three key
areas: store configuration, product and catalog creation, and order
administration. On the front end, all major systems are configurable and
integrate with the standard Drupal systems (node, taxonomy, user, etc.).
On the back end, the settings pages and order administration pages have
been designed with ease of use in mind.
The Frequently Asked Questions (faq) module allows users, with
appropriate permissions, to create question and answer pairs which
they want displayed on the 'faq' page. The 'faq' page is automatically
generated from the FAQ nodes configured.
The Session API is a very simple set of functions that extend the core
sessions workings, allowing data to be stored and associated with a
user's session.
The Link checker module extracts links from your content when saved and
periodically tries to detect broken hypertext links by checking the
remote sites and evaluating the HTTP response codes. It shows all broken
links in the reports/logs section and on the content edit page if a link
check has been failed. An author specific broken links report is also
available in "My Account".
Provides a central transliteration service to other Drupal modules, and
sanitizes file names while uploading. Generally spoken, it takes Unicode
text and tries to represent it in US-ASCII characters (universally
displayable, unaccented characters) by attempting to transliterate the
pronunciation expressed by the text in some other writing system to
Roman letters.
In simple use cases the search_config module allows site admins to
decide which fields to display on the advanced search form when enabled.
There is also the option of excluding node types from search results.
Once selected they are also automatically removed from the advance
search form. This gives more control over the content that can be
searched to those who need it.
On 404 Not Found error pages, Drupal will skip rendering of several
pieces of your website for performance reasons. This module simply
revives those features on 404 pages to show lost users how to get
to real pages.
This module provides two ways of referencing relevant content. Both of
these methods provide configuration to filter for specific content types
and vocabularies, limit the maximum size of the result and provide some
header text. The result on both cases are a list of nodes which the
module considers most relevant based on the categorization of the
current page. This is achieved by finding other nodes which are of one
of the allowed types and have the most number of terms in common.
This module enables you to make the Menu Settings required on specific
content types. It forces a node from one or more content types to be
included in the menu system before the content will be saved
successfully. This can be useful in a number of situations, e.g. when
using [menupath-raw] in the Pathauto settings, which expects a node to
live within the menu system.
The Override Node Options module allows permissions to be set to each
field within the Authoring information and Publishing options field
sets on the node form. It also allow selected field sets to be set as
collapsed and / or collapsible.
This module allows you to grant access for specific user roles to view
unpublished nodes of a specific type. Access control is quite granular
in this regard. Additionally, using this module does not require any
modifications to your existing URL structure.
Used in concert with the Override Node Options module, you can give
specific roles the ability to publish/unpublish certain node types
without giving those roles administrative access to all nodes.
The tables module allows you to create a table in a node using a simple
markup. Tables are entered using a simple macro format.
This module allows you to set the "class" for the table to allow
different appearances for different tables. It also comes with a css
sheet to do a number of different appearances.
The SpamSpan module obfuscates email addresses to help prevent spambots
from collecting them. The problem with most email address obfuscators is
that they rely upon JavaScript being enabled on the client side. This
makes the technique inaccessible to people with screen readers. SpamSpan
however will produce clickable links if JavaScript is enabled, and will
show the email address as example [at] example [dot] com if the browser
does not support JavaScript or if JavaScript is disabled.
This module will create a main book page for content type selected in
BookMadeSimple settings. This is a shortcut to create a node and click
on Update book outline.
A dropdown listbox will be added in books links. Only allowed content-
type (define in content-type settings) are printed. Selecting a content
type will add it as a child page of the book page.
Adds a block for every CCK field you selected for being available as
block. This makes it possible to show the field's value of the
currently shown node in the block (placed left, right or in whatever
region) instead of (or next to) the node's main content area. Kind of
a simple panel variation.
The notify module allows users to subscribe to periodic emails which
include all new or revised content and/or comments much like the daily
news letters sent by some websites.
Even if this feature is not configured for normal site users, it can
be a useful feature for an administrator of a site to receive
notification of new content submissions and comment posts.
This module adds a tab for sufficiently permissioned users. The tab shows
all revisions like standard Drupal but it also allows pretty viewing of
all added/changed/deleted words between revisions.
The idea behind the Zen theme is to have a very flexible standards-
compliant and semantically correct XHTML theme that can be highly
modified through CSS and an enhanced version of Drupal's template
system. Out of the box, Zen is clean and simple with either a one,
two, or three column layout of fixed or liquid width. In addition,
the HTML source order has content placed before sidebars or the navbar
for increased accessibility and SEO.