# data[].attributes.body.value
This project is an implementation of the <strong><a href="https://affiliate-program.amazon.com/gp/advertising/api/detail/main.html">Amazon Product Advertising API</a></strong>. 

It's modular in design, with a central "<strong>Pure API</strong>" component that interacts with Amazon, and optional modules to handle expanded data for additional product types, features like wish-lists and customer reviews, etc.

<h2>Major Update - 2/9/17</h2>
The Amazon Product Advertisement API module requires serious attention and has been severally ignored the last 3-4 years.

The <strong>Drupal 7</strong> version requires updates, but for the most part is relatively stable.

The <strong>Drupal 8</strong> version is a joke (my fault - kamescg) and really should have never been released, because it was really just a rudimentary port from the Drupal 7 version.

Enough requests have been made that I think it's merits some developer love to re-launch this module, so it can serve the Drupal community and the many people who I assume are earning an income using the Amazon Product Advertisement API Module. 

I'm thinking about starting a public fund, so we can ensure the module will continue to have support, so if anybody is interested in either funding the project or becoming a sponsored developer, please contact me directly (kamescg) or open an issue ticket, so everyone can get involved.

# data[].attributes.body.processed
This project is an implementation of the Amazon Product Advertising API.

It's modular in design, with a central "Pure API" component that interacts with Amazon, and optional modules to handle expanded data for additional product types, features like wish-lists and customer reviews, etc.

Major Update - 2/9/17

The Amazon Product Advertisement API module requires serious attention and has been severally ignored the last 3-4 years.

The Drupal 7 version requires updates, but for the most part is relatively stable.

The Drupal 8 version is a joke (my fault - kamescg) and really should have never been released, because it was really just a rudimentary port from the Drupal 7 version.

Enough requests have been made that I think it's merits some developer love to re-launch this module, so it can serve the Drupal community and the many people who I assume are earning an income using the Amazon Product Advertisement API Module.

I'm thinking about starting a public fund, so we can ensure the module will continue to have support, so if anybody is interested in either funding the project or becoming a sponsored developer, please contact me directly (kamescg) or open an issue ticket, so everyone can get involved.

# data[].attributes.body.summary
This project is an implementation of the Amazon Product Advertising API. 

It's modular in design, with a central "Pure API" component that interacts with Amazon, and optional modules to handle expanded data for additional product types, features like wish-lists and customer reviews, etc.


The Amazon API Module and Amazon Store will now be actively maintained, updated and enhanced. 

# data[].attributes.body.value
Allows users to annotate content in Drupal.
7.x-1.x
Annotation entity was provided by this module for Drupal 7. This module only provides storage for annotations and currently only one lib (Annotator) was supported. So to make annotation, please install Annotator module. This module is started with https://github.com/sanduhrs/drupal-annotator/tree/7.x-1.x/modules/annotation by sanduhrs (Thanks very much!).
6.x-1.x
We currently support both image annotation and text annotation. This D6 module is in a very early alpha stage. Do not download this module unless you plan to contribute code. 6.x and 7.x are completely different, and there is no upgrade path.

🇺🇦

#StandWithUkraine Please consider supporting Ukraine in a fight for their freedom and safety of Europe.

# data[].attributes.body.processed
Allows users to annotate content in Drupal.
Back to top
7.x-1.x

Annotation entity was provided by this module for Drupal 7.
This module only provides storage for annotations and currently only one lib (Annotator) was supported. So to make annotation, please install Annotator module.

This module is started with https://github.com/sanduhrs/drupal-annotator/tree/7.x-1.x/modules/annot… by sanduhrs (Thanks very much!).
Back to top
6.x-1.x

We currently support both image annotation and text annotation.

This D6 module is in a very early alpha stage. Do not download this module unless you plan to contribute code.
6.x and 7.x are completely different, and there is no upgrade path.

🇺🇦

#StandWithUkraine
Please consider supporting Ukraine in a fight for their freedom and safety of Europe.

Back to top

# data[].attributes.body.value
Drupal 8.x
This module provides a Atom 1.0 feed style and row plugin for the Drupal 8.x views Feed display.
Drupal 7.x and 6.x
The Drupal 7.x and 6.x versions of this module are not supported. Provides an Atom 1.0 feed. To help expose some of Atom's functionality, try Syndication.

# data[].attributes.body.processed
Back to top
Drupal 8.x

This module provides a Atom 1.0 feed style and row plugin for the Drupal 8.x views Feed display.
Back to top
Drupal 7.x and 6.x

The Drupal 7.x and 6.x versions of this module are not supported.

Provides an Atom 1.0 feed.

To help expose some of Atom's functionality, try Syndication.
Back to top

# data[].attributes.body.value
The Drupal bbcode.module adds a BBCode filter to Drupal. This allows you to use HTML-like tags as an alternative to HTML itself for adding markup to your posts. BBCode is easier to use than HTML and helps to prevent malicious users from disrupting your site's formatting.

See the help screen of the module (or the code) for information on which tags and variants are supported. This implementation is not necessarily the same as the original BBCode implementation.

Note that this filter also recognizes and converts URLs and email addresses to links automatically.

The quicktags module can be used in conjunction with this module to provide a BBCode formatting bar above all text areas.

# data[].attributes.body.processed
The Drupal bbcode.module adds a BBCode filter to Drupal. This allows you to use HTML-like tags as an alternative to HTML itself for adding markup to your posts. BBCode is easier to use than HTML and helps to prevent malicious users from disrupting your site's formatting.

See the help screen of the module (or the code) for information on which tags and variants are supported. This implementation is not necessarily the same as the original BBCode implementation.

Note that this filter also recognizes and converts URLs and email addresses to links automatically.

The quicktags module can be used in conjunction with this module to provide a BBCode formatting bar above all text areas.

# data[].attributes.body.value
A simple module that enables a block which displays the users' birthday
dates.

# data[].attributes.body.processed
A simple module that enables a block which displays the users' birthday
dates.

# data[].attributes.body.value
📑 Allow users to save any page of your Drupal site as a favorite. The bookmarked link can have a custom title - and even more fields if you want to add new ones on the flag:bookmark. Indeed, under the hood favorites are simply flagging entities referencing a path_alias and are stored per user.
How to use
Install the module as you would usually do: composer require drupal/bookmarks drush en bookmarks Place the block to display the link on front:

Go to Admin > Structure > Block layout

Add the Bookmarksin one or more regions

(optional) Customize the template with a custom Twig:

Create a custom flag--bookmark.html.twig template (e.g. you can copy the example provided in this module under /templates)

Alternatives

Flag provides an example bookmark flag and supporting views. However, that sub-module only supports placing the bookmark link on content entities (i.e. Node pages). Whereas, this Bookmarks module allows a user to save any page of your Drupal site as a favorite.

Drupal's core Shortcut module allows users to create and manage customizable lists of shortcut links to important pages on their site. Shortcuts can be organized into sets, and users can create as many sets as they like. For example, users can create sets for different roles, such as moderators, administrators, and users. Users with the "Select any shortcut set" permission can choose a shortcut set created by anyone on the site. Whereas, this Bookmarks module lists favorites specific to that user only.

# data[].attributes.body.processed
📑 Allow users to save any page of your Drupal site as a favorite.

The bookmarked link can have a custom title - and even more fields if you want to add new ones on the flag:bookmark. Indeed, under the hood favorites are simply flagging entities referencing a path_alias and are stored per user.

How to use

Install the module as you would usually do:

composer require drupal/bookmarks
drush en bookmarks

Place the block to display the link on front:

Go to Admin > Structure > Block layout

Add the Bookmarksin one or more regions

(optional) Customize the template with a custom Twig:

Create a custom flag--bookmark.html.twig template (e.g. you can copy the example provided in this module under /templates)

Alternatives

Flag provides an example bookmark flag and supporting views. However, that sub-module only supports placing the bookmark link on content entities (i.e. Node pages). Whereas, this Bookmarks module allows a user to save any page of your Drupal site as a favorite.

Drupal's core Shortcut module allows users to create and manage customizable lists of shortcut links to important pages on their site. Shortcuts can be organized into sets, and users can create as many sets as they like. For example, users can create sets for different roles, such as moderators, administrators, and users. Users with the "Select any shortcut set" permission can choose a shortcut set created by anyone on the site. Whereas, this Bookmarks module lists favorites specific to that user only.

Back to top

# data[].relationships.field_project_images.data[].meta.alt
Screenshot showing the "Add/Remove" bookmark block

# data[].relationships.field_project_images.data[].meta.alt
Screenshot of a the default Bookmarks views, displayed in a tab on User pages.

# data[].attributes.body.value
Creates a breadcrumb trail, which serves as a navigational aid for the user.  The breadcrumb trail contains links to pages higher in site hierarchy, i.e., above the current location.

The primary goal of this project is to replace Drupal core's breadcrumb trails functionality deeply buried into <code>includes/menu.inc</code> by moving it into a dedicated module, to be moved into core for D8.

Co-authors + maintainers wanted.
<!--break-->
<h3>Goals</h3>
<ol>
<li>Expose a block containing the breadcrumb.  Make it possible to spawn multiple blocks (configurations) for Panels (Everywhere) compatiblity.</li>
<li>Configuration options:
<ul>
<li>Optional custom prefix; e.g., "You are here:" (none by default)</li>
<li>Separator character/string, if any. (» by default)</li>
<li>Whether to include current page, optionally clickable. (disabled by default)</li>
<li>Configurable "Home" string.</li>
<li>Whether to hide breadcrumb if it only contains "Home".</li>
</ul></li>
<li>Make it exportable.</li>
<li>Default to menu_get_active_breadcrumb() as data source, but allow to tie in other modules (such as <a href="http://drupal.org/project/hansel">Hansel breadcrumbs</a>, <a href="http://drupal.org/project/clickpath">Clickpath</a>, or custom code)</li>
<li>Purposively account for "attached alike" breadcrumb enhancements like a <a href="http://drupal.org/node/787896">"Back to last non-admin page" link</a> prefixed to the output, or a custom #pre_render that needs the entire menu link $tree for each link in $trail to convert each breadcrumb link into a dropdown link list providing access to sibling pages (like <a href="http://drupal.org/project/crumbdown">Crumbdown</a>).</li>
<li>Consider merging one or more of the following:
<ul>
<li><a href="http://drupal.org/project/menu_breadcrumb">Menu Breadcrumb</a></li>
<li><a href="http://drupal.org/project/menutrails">Menu Trails</a></li>
<li><a href="http://drupal.org/project/custom_breadcrumbs">Custom Breadcrumbs</a></li>
<li><a href="http://drupal.org/project/nodetrail">Node Trail</a></li>
<li><a href="http://drupal.org/project/taxonomy_menu_trails">Taxonomy Menu Trails</a></li>
<li><a href="http://drupal.org/project/taxonomy_breadcrumb">Taxonomy Breadcrumb</a></li>
<li><a href="http://drupal.org/project/primary_term">Primary term</a> / <a href="http://drupal.org/project/pt2ami">Primary Term to Active Menu Item</a></li>
</ul>
...but stay within the common scope and constraints of Drupal core.
</li>
<li>Move this module into Drupal 8 core.</li>
</ol>

# data[].attributes.body.processed
Creates a breadcrumb trail, which serves as a navigational aid for the user. The breadcrumb trail contains links to pages higher in site hierarchy, i.e., above the current location.

The primary goal of this project is to replace Drupal core's breadcrumb trails functionality deeply buried into includes/menu.inc by moving it into a dedicated module, to be moved into core for D8.

Co-authors + maintainers wanted.

Goals

Expose a block containing the breadcrumb. Make it possible to spawn multiple blocks (configurations) for Panels (Everywhere) compatiblity.

Configuration options:

Optional custom prefix; e.g., "You are here:" (none by default)

Separator character/string, if any. (» by default)

Whether to include current page, optionally clickable. (disabled by default)

Configurable "Home" string.

Whether to hide breadcrumb if it only contains "Home".

Make it exportable.

Default to menu_get_active_breadcrumb() as data source, but allow to tie in other modules (such as Hansel breadcrumbs, Clickpath, or custom code)

Purposively account for "attached alike" breadcrumb enhancements like a "Back to last non-admin page" link prefixed to the output, or a custom #pre_render that needs the entire menu link $tree for each link in $trail to convert each breadcrumb link into a dropdown link list providing access to sibling pages (like Crumbdown).

Consider merging one or more of the following:

Menu Breadcrumb

Menu Trails

Custom Breadcrumbs

Node Trail

Taxonomy Menu Trails

Taxonomy Breadcrumb

Primary term / Primary Term to Active Menu Item

...but stay within the common scope and constraints of Drupal core.

Move this module into Drupal 8 core.

# data[].attributes.body.value
Allows you to add other site users to your buddy list, organize these into groups, and monitor their content. It is a basic building block for anyone wishing to make a social networking site in Drupal. The 4.7 version is much more feature-rich than the 4.6 version. Allows integration with other modules, such as Invite, to do things like add invited members to buddylists automatically. The word "buddy" can now be changed altogether by editing the translations array at the top of the buddylist.module file.
Maintainers
Josh Koenig (joshk) Dominik Kiss (nodestroy)
Drupal 5.0 version available for testing
Please test out the new 5.0 version and report any bugs you may find. There is also a new working group dedicated to discussing social networking sites (like MySpace and Facebook). If you are interested in this area, please join the group and take part in the discussion.

# data[].attributes.body.processed
Allows you to add other site users to your buddy list, organize these into groups, and monitor their content. It is a basic building block for anyone wishing to make a social networking site in Drupal. The 4.7 version is much more feature-rich than the 4.6 version. Allows integration with other modules, such as Invite, to do things like add invited members to buddylists automatically. The word "buddy" can now be changed altogether by editing the translations array at the top of the buddylist.module file.
Back to top
Maintainers

Josh Koenig (joshk)
Dominik Kiss (nodestroy)
Back to top
Drupal 5.0 version available for testing

Please test out the new 5.0 version and report any bugs you may find. There is also a new working group dedicated to discussing social networking sites (like MySpace and Facebook). If you are interested in this area, please join the group and take part in the discussion.
Back to top

# data[].attributes.body.value
Lets users maintain catalog of books, albums, products, etc. Just type in an ISBN or product code and all relevant details are downloaded. Interacts with Amazon.com via web services

# data[].attributes.body.processed
Lets users maintain catalog of books, albums, products, etc. Just type in an ISBN or product code and all relevant details are downloaded. Interacts with Amazon.com via web services

# data[].attributes.body.value
This is a simple chat module that allows your site's visitors to chat in an HTML/Javascript pop-up window. Registered users can invite other users to join the chat. No additional software is required. If you are using Drupal 4.7 or higher, consider using the more advanced Chat Room module instead of Chat Box.

Road Map

# data[].attributes.body.processed
This is a simple chat module that allows your site's visitors to chat in an HTML/Javascript pop-up window. Registered users can invite other users to join the chat. No additional software is required. If you are using Drupal 4.7 or higher, consider using the more advanced Chat Room module instead of Chat Box.

Road Map

# data[].attributes.body.value
The Checkmail module checks a POP3 or IMAP e-mail account and prints one or more of the following: the total number of e-mail messages in your INBOX, the number of recent (new) e-mail messages (IMAP only), the number of unread e-mail messages (IMAP only), the total size of the e-mail messages in your mailbox. This module provides both a block and page for output.
<!--break-->
This module can encrypt the login password(s), if you are using either the AES encryption (https://drupal.org/project/aes) or Encryption (https://drupal.org/project/encrypt) modules. If you choose not to use either of them, your passwords will not be encrypted, so that if your server is compromised, the attacker could have access to your plaintext password(s).

# data[].attributes.body.processed
The Checkmail module checks a POP3 or IMAP e-mail account and prints one or more of the following: the total number of e-mail messages in your INBOX, the number of recent (new) e-mail messages (IMAP only), the number of unread e-mail messages (IMAP only), the total size of the e-mail messages in your mailbox. This module provides both a block and page for output.

This module can encrypt the login password(s), if you are using either the AES encryption (https://drupal.org/project/aes) or Encryption (https://drupal.org/project/encrypt) modules. If you choose not to use either of them, your passwords will not be encrypted, so that if your server is compromised, the attacker could have access to your plaintext password(s).

# data[].attributes.body.value
A module that lets you track CVS commit messages. You can see it in action at http://drupal.org/cvs. Interfaces with the project module to make releases via specific CVS branches and tags, and provides per-project source code access control.

The HEAD branch of this module has been ported to Drupal 6 and is now running on drupal.org. However, we'd like to put some finishing touches on things before we create an official 6.x-1.0 release for widespread use.

Please read about How to help with the project* modules if you can spare any effort to support one of the key modules that powers drupal.org and all Drupal development.

This module is maintained by Derek Wright (dww) and Chad Phillips (hunmonk) of 3281d Consulting. Anyone interested in paid support, customization, or sponsoring features should contact 3281d.com.

# data[].attributes.body.processed
A module that lets you track CVS commit messages. You can see it in action at http://drupal.org/cvs. Interfaces with the project module to make releases via specific CVS branches and tags, and provides per-project source code access control.

The HEAD branch of this module has been ported to Drupal 6 and is now running on drupal.org. However, we'd like to put some finishing touches on things before we create an official 6.x-1.0 release for widespread use.

Please read about How to help with the project* modules if you can spare any effort to support one of the key modules that powers drupal.org and all Drupal development.

This module is maintained by Derek Wright (dww) and Chad Phillips (hunmonk) of 3281d Consulting. Anyone interested in paid support, customization, or sponsoring features should contact 3281d.com.

# data[].attributes.body.value
Introduction

Devel module contains helper functions and pages for Drupal developers and inquisitive admins:

A block and toolbar for quickly accessing devel pages

A menu tab added to entities to give access to internal entity properties

Urls created to view the internal entity properties even when there is no menu tab, for example /devel/paragraph/n

Debug functions for inspecting a variable such as dpm($variable)

Debug a SQL query dpq($query or print a backtrace ddebug_backtrace()

A block for masquerading as other users (useful for testing)

A mail-system class which redirects outbound email to files

Drush commands such as fn-hook, fn-event, token, uuid, and devel-services

Devel Generate. Bulk creates nodes, users, comment, taxonomy, media, menus, block content for development. Has Drush integration.

This module is safe to use on a production site. Just be sure to only grant access development information permission to developers.

Collaboration

https://gitlab.com/drupalspoons/devel is our workplace for code, MRs, and CI.

Create a personal fork in order to make an MR.

We plan to move bck to drupal.org once it uses Gitlab for issues.

We auto-push back to git.drupalcode.org in order to keep Security Team coverage and packages.drupal.org integration.

Chat with us at #devel on Drupal Slack.

Local Development

DDEV is configured with https://github.com/ddev/ddev-drupal-contrib for for easy local development, test running, etc.

Version Compatibility

Devel version | Drupal core | PHP | Drush
5.5+ | 10.4+ | 8.3+ | 13.7+
5.2-5.4 | 10+ | 8.1+ | 12+
5.0, 5.1 | 9,10 | 8.1+ | 11+
4.x | 8.9+,9 | 7.2+ | 9+
8.x-2.x | 8.x | 7.0+ | 8+

Maintainers

See https://gitlab.com/groups/drupaladmins/devel/-/group_members.

# data[].attributes.body.processed
Introduction

Devel module contains helper functions and pages for Drupal developers and inquisitive admins:

A block and toolbar for quickly accessing devel pages

A menu tab added to entities to give access to internal entity properties

Urls created to view the internal entity properties even when there is no menu tab, for example /devel/paragraph/n

Debug functions for inspecting a variable such as dpm($variable)

Debug a SQL query dpq($query or print a backtrace ddebug_backtrace()

A block for masquerading as other users (useful for testing)

A mail-system class which redirects outbound email to files

Drush commands such as fn-hook, fn-event, token, uuid, and devel-services

Devel Generate. Bulk creates nodes, users, comment, taxonomy, media, menus, block content for development. Has Drush integration.

This module is safe to use on a production site. Just be sure to only grant access development information permission to developers.

Collaboration

https://gitlab.com/drupalspoons/devel is our workplace for code, MRs, and CI.

Create a personal fork in order to make an MR.

We plan to move bck to drupal.org once it uses Gitlab for issues.

We auto-push back to git.drupalcode.org in order to keep Security Team coverage and packages.drupal.org integration.

Chat with us at #devel on Drupal Slack.

Local Development

DDEV is configured with https://github.com/ddev/ddev-drupal-contrib for for easy local development, test running, etc.

Version Compatibility

Devel version | Drupal core | PHP | Drush
5.5+ | 10.4+ | 8.3+ | 13.7+
5.2-5.4 | 10+ | 8.1+ | 12+
5.0, 5.1 | 9,10 | 8.1+ | 11+
4.x | 8.9+,9 | 7.2+ | 9+
8.x-2.x | 8.x | 7.0+ | 8+

Maintainers

See https://gitlab.com/groups/drupaladmins/devel/-/group_members.

Back to top

# data[].attributes.body.value
Event is a custom entity that allows you to store events on your drupal site. The module is under construction with the Conference Organizing Distribution
Versions
Version one of this module includes the event_group and gevent sub modules. These modules depended on version 1 of the Group Module. In order to provide support for newer versions of the Group Module, these projects have been split into their own projects as part of Event Version 2. They are available below.

Event Group - For managing group attendees using Groups.

Group Events - For managing ownership/access to Events using Group Membership.

Key features
Custom event entity with fields related to event management Example views for sites to implement their own event API for other modules to share a common data format for events
Installing
Composer is recommended for installing. Make sure when you require in or use composer update, you use --with-all-dependencies otherwise the machine_name core patch won't get applied. If you don't use composer, you must patch core yourself with the latest patch here: [#2685749]
Contribute!
If you're a camp, event organizer, or site needing the use of events, this module is the one for you. If you're looking to build something, help by contributing back your work! You can find us in #drupal-cod on Drupal slack
Older event module
The last release of this module was in Drupal 5 and is no longer supported. There is a D6 port that was started, but this has also been abandoned. If you're looking for support, you should contact Killes. There is no upgrade path from D5/D6 to the D8 version of event. Please take some time to look at the module's settings and read the documentation.

# data[].attributes.body.processed
Event is a custom entity that allows you to store events on your drupal site. The module is under construction with the Conference Organizing Distribution
Back to top
Versions Version one of this module includes the event_group and gevent sub modules. These modules depended on version 1 of the Group Module. In order to provide support for newer versions of the Group Module, these projects have been split into their own projects as part of Event Version 2. They are available below. Event Group - For managing group attendees using Groups. Group Events - For managing ownership/access to Events using Group Membership. Key features Custom event entity with fields related to event management Example views for sites to implement their own event API for other modules to share a common data format for events Installing Composer is recommended for installing. Make sure when you require in or use composer update, you use --with-all-dependencies otherwise the machine_name core patch won't get applied. If you don't use composer, you must patch core yourself with the latest patch here: [#2685749] Contribute! If you're a camp, event organizer, or site needing the use of events, this module is the one for you. If you're looking to build something, help by contributing back your work! You can find us in #drupal-cod on Drupal slack Older event module The last release of this module was in Drupal 5 and is no longer supported. There is a D6 port that was started, but this has also been abandoned. If you're looking for support, you should contact Killes. There is no upgrade path from D5/D6 to the D8 version of event. Please take some time to look at the module's settings and read the documentation.
Back to top

# data[].attributes.body.value
This module augments your site's search results by incorporating
those external web pages which were linked to from your users' posts.
This has the nice effect of making your site a grand destination for the
topic in which you specialize. It is also handy for assimilating external
knowledge into your own 'knowledge repository'. 

# data[].attributes.body.processed
This module augments your site's search results by incorporating
those external web pages which were linked to from your users' posts.
This has the nice effect of making your site a grand destination for the
topic in which you specialize. It is also handy for assimilating external
knowledge into your own 'knowledge repository'.

# data[].attributes.body.value
Ezmlm has moved to Github

# data[].attributes.body.processed
Ezmlm has moved to Github

# data[].attributes.body.value
A module that lets you organize and maintain a feature list by category.

The 5.0 and later version has configurable categories.

This module was used to run the Drupal.org "features" page but is now retired.

NOTE: This modules precedes, and is not related in any way, to the more popular features module!

# data[].attributes.body.processed
A module that lets you organize and maintain a feature list by category.

The 5.0 and later version has configurable categories.

This module was used to run the Drupal.org "features" page but is now retired.

NOTE: This modules precedes, and is not related in any way, to the more popular features module!

# data[].attributes.body.value
Feedback allows users and visitors of a Drupal site to quickly send feedback messages about the currently displayed page, using a fixed positioned and ajaxified feedback form.  This helps site administrators in quality assurance of their pages, contents and theme.

Because the form is submitted via AJAX, a user will not be redirected to another page and can continue visiting/using the site after posting feedback.

All feedback messages are listed and grouped by status in an administrative feedback log.  Each feedback message can be marked as 'done'.  Privileged users are able to see existing feedback messages for the currently displayed page to prevent submitting duplicate feedbacks for already known issues (f.e. during site building).  Since feedback messages are additionally stored with a 'masked' path (similar to dynamic menu item arguments in D6, i.e. <code>user/%/edit</code>), existing feedback messages for similar pages can be displayed (except node/% paths).

Feedback optionally integrates with <a href="/project/browscap">BrowsCap</a> to additionally record the user agent for each feedback message, which helps in tracking down theming issues.
<!--break-->
<h3>Dependencies</h3>
<ul>
<li>3.0.x (Drupal 8, 9): None
<li>6.x-1.x, 7.x-1.x: None.</li>
<li>5.x-2.x: <a href="/project/jquery_update">jQuery Update 2.x</a></li>
</ul>

<h3>Installation</h3>
<ul>
<li>Please see current README.txt, https://git.drupalcode.org/project/feedback/-/blob/3.x/README.txt</li>
</ul>

<h3>Credits</h3>
Current Maintainers:
<ul>
<li><a href="https://www.drupal.org/user/368613">Christopher Gervais (ergonlogic)</a></li>
<li><a href="https://www.drupal.org/user/536298">M Parker (mparker17)</a></li>
<li><a href="https://www.drupal.org/user/44299">Squiggy Rubio (squiggy)</a></li>
<li><a href="https://www.drupal.org/user/241634">Tim Plunkett (tim.plunkett)</a></li>
</ul>

Former Maintainers: 
<ul>
<li><a href="http://drupal.org/user/2755531">Ben Hall (Eluchel)</a></li>
<li><a href="http://drupal.org/user/54136">Daniel F. Kudwien (sun)</a></li>
<li><a href="http://drupal.org/user/112500">Jody Hamilton (Jody Lynn)</a></li>
</ul>

This project has been sponsored by:
<ul>
<li><a href="http://www.unleashedmind.com">unleashed mind</a>
Specialized in consulting and development of Drupal powered sites, our services include installation, development, theming, customization, and hosting to get you started. Visit http://www.unleashedmind.com for more information.</li>
<li><a href="http://zivtech.com">Zivtech</a></li>
<li><a href="https://consensus.enterprises/">Consensus Enterprises</a>
We help small teams do big things.
</li>
<li><a href="https://ocasi.org/">OCASI - Ontario Council of Agencies Serving Immigrants</a>
OCASI was formed in 1978 to act as a collective voice for immigrant serving agencies and to coordinate responses to shared needs and concerns. OCASI is a registered charity governed by a volunteer board of directors. Its membership is comprised of more than 200 community-based organizations in the province of Ontario.
</li>
</ul>

# data[].attributes.body.processed
Feedback allows users and visitors of a Drupal site to quickly send feedback messages about the currently displayed page, using a fixed positioned and ajaxified feedback form. This helps site administrators in quality assurance of their pages, contents and theme.

Because the form is submitted via AJAX, a user will not be redirected to another page and can continue visiting/using the site after posting feedback.

All feedback messages are listed and grouped by status in an administrative feedback log. Each feedback message can be marked as 'done'. Privileged users are able to see existing feedback messages for the currently displayed page to prevent submitting duplicate feedbacks for already known issues (f.e. during site building). Since feedback messages are additionally stored with a 'masked' path (similar to dynamic menu item arguments in D6, i.e. user/%/edit), existing feedback messages for similar pages can be displayed (except node/% paths).

Feedback optionally integrates with BrowsCap to additionally record the user agent for each feedback message, which helps in tracking down theming issues.

Dependencies

3.0.x (Drupal 8, 9): None

6.x-1.x, 7.x-1.x: None.

5.x-2.x: jQuery Update 2.x

Installation

Please see current README.txt, https://git.drupalcode.org/project/feedback/-/blob/3.x/README.txt

Credits

Current Maintainers:

Christopher Gervais (ergonlogic)

M Parker (mparker17)

Squiggy Rubio (squiggy)

Tim Plunkett (tim.plunkett)

Former Maintainers:

Ben Hall (Eluchel)

Daniel F. Kudwien (sun)

Jody Hamilton (Jody Lynn)

This project has been sponsored by:

unleashed mind
Specialized in consulting and development of Drupal powered sites, our services include installation, development, theming, customization, and hosting to get you started. Visit http://www.unleashedmind.com for more information.

Zivtech

Consensus Enterprises
We help small teams do big things.

OCASI - Ontario Council of Agencies Serving Immigrants
OCASI was formed in 1978 to act as a collective voice for immigrant serving agencies and to coordinate responses to shared needs and concerns. OCASI is a registered charity governed by a volunteer board of directors. Its membership is comprised of more than 200 community-based organizations in the province of Ontario.

Back to top

# data[].attributes.body.summary
Allows users and visitors of a Drupal site to quickly send feedback messages about the currently displayed page, using a fixed positioned and ajaxified feedback form.

# data[].attributes.body.value
This project was the testing grounds for the Drupal 7 File module, which is the successor to FileField and Upload modules.

This module was committed in [#391330] to Drupal core. So there's no need to ever download this package. Previously, file.module was a precursor to Upload module in Drupal 4.0.

# data[].attributes.body.processed
This project was the testing grounds for the Drupal 7 File module, which is the successor to FileField and Upload modules.

This module was committed in [#391330] to Drupal core. So there's no need to ever download this package. Previously, file.module was a precursor to Upload module in Drupal 4.0.

# data[].attributes.body.value
This module lets people upload and download files,
with optional MIME type restrictions.
- This is now a depreciated version. Please use filestore2 instead. -

# data[].attributes.body.processed
This module lets people upload and download files,
with optional MIME type restrictions.
- This is now a depreciated version. Please use filestore2 instead. -

# data[].attributes.body.value
This module embeds Gallery2 (http://gallery.menalto.com) inside your Drupal installation to support photos, videos and other content. There is support for 2 types of image blocks and a navigation menu, inserting of images into nodes via an input filter, TinyMCE support, syncing of users between the 2 applications, ...
<!--break-->
Note that you will need to download and install Gallery2 (http://gallery.menalto.com/downloads) prior to installing this module.

You can see the module in action on Gallery's own website at: http://gallery.menalto.com/gallery.

<strong>Please post bug reports and feature requests in the <a href="http://drupal.org/project/issues/gallery">Issues tracker</a>, support requests should generally go to the <a href= "http://gallery.menalto.com/forum/78">Gallery 2 Integrations Forums</a> first.</strong> You may also check the <a href="http://groups.drupal.org/gallery2-integration">Gallery2 Integration group</a> for latest news and discussion on the module.

<h3>News & Updates</h3>
A development version of gallery module for Drupal 6 is now available! It already contains all the features targeted for this series. <strong>Please note that the D6 module requires the G2.3/svn version of Gallery2.</strong>

<i>People have asked how to support development of the Gallery 2 integration in Drupal. They explicitly asked for a <a href="http://www.profix898.de/chipin/drupal">ChipIn</a> fund to support me monetarily. <strong>But</strong> also consider - even as a non-developer - to contribute <a href="http://codex.gallery2.org/Integration:Drupal">documentation</a> and/or help on the <a href="http://gallery.menalto.com/forum/78">forums</a>, so that I can focus on coding instead.</i>

# data[].attributes.body.processed
This module embeds Gallery2 (http://gallery.menalto.com) inside your Drupal installation to support photos, videos and other content. There is support for 2 types of image blocks and a navigation menu, inserting of images into nodes via an input filter, TinyMCE support, syncing of users between the 2 applications, ...

Note that you will need to download and install Gallery2 (http://gallery.menalto.com/downloads) prior to installing this module.

You can see the module in action on Gallery's own website at: http://gallery.menalto.com/gallery.

Please post bug reports and feature requests in the Issues tracker, support requests should generally go to the Gallery 2 Integrations Forums first. You may also check the Gallery2 Integration group for latest news and discussion on the module.

News & Updates

A development version of gallery module for Drupal 6 is now available! It already contains all the features targeted for this series. Please note that the D6 module requires the G2.3/svn version of Gallery2.

People have asked how to support development of the Gallery 2 integration in Drupal. They explicitly asked for a ChipIn fund to support me monetarily. But also consider - even as a non-developer - to contribute documentation and/or help on the forums, so that I can focus on coding instead.

# data[].attributes.body.value
Note: As of September 21, 2021, this project appears to no longer be supported. If you are interested in taking this project over, or you as the project maintainer feel this message has been posted in error, please reply to https://www.drupal.org/project/projectownership/issues/3238142.

The Glossary module helps newbies understand the jargon which always crops up when specialists talk about a topic. Doctors discuss CBC and EKG and CCs. Web developers keep talking about CSS, P2P, XSLT, etc. This is all intimidating for newbies.

The glossary module scans posts for glossary terms (including synonyms). The glossary indicator is inserted after every found term, or the term itself is turned into an indicator depending on the site settings. By hovering over the indicator, users may learn the definition of that term. Clicking the indicator leads the user to that term presented within the whole glossary or directly to the detailed description of the term, if available.

The glossary uses Drupal's built in taxonomy feature, so you can organize your terms in a Drupal vocabulary. This allows you to create hierarchical structures, synonyms and relations. Glossary terms are represented with the taxonomy terms in the glossary vocabulary. Descriptions are used to provide a short explanation of the terms. You can attach nodes to the terms to provide detailed explanation on the keywords.

Please, any time you download a new version, use the "Clear Cache" button on the settings page or you may not see the new features for some time.

The Glossary module will call the Taxonomy Image module, if it's enabled, to allow you to display an image for each term in the glossary.

We will also work with the Hovertips and Clicktips module to produce fancier hovertips. This also allows the tip to "glossarize" another level deep within the glossary definition.

Firefox "fix" for hover tips: there's a Firefox add-in called "Long Titles" that allow the tool-tips display to be expanded to include the whole tip.

Note: This module does not, nor ever will, move the vocabulary management out of the Administration menu. That can be done by other modules. For example, see Taxonomy Delegate or Vocabulary Permissions.

Some people have asked the difference between this module and G2. There is a Comparison of "Glossary"-type modules.

Showcase

If you are using this module and would like to showcase your site here, please send me the link (use my Contact form).

http://www.valueofbiotech.com/biotech-basics/glossary

Drupal 7
Yes, we have begun a 7.x branch. If you are not willing to submit patches, please don't even try to use it yet.
Issues

As with all contributed modules, when considering submitting an issue:

Read the documentation (two or three times is better).

Use the "Clear Cache" button on the settings page and retry the problem.

Review the existing issues list. (Don't forget to select "<all>" for the "Status" field.)

Gather all the appropriate information. This may include (but is not limited to):

Drupal version.

Browser type and version.

Database type and version.

Error messages, if any.

Module settings.

Submit the issue. If other modules are involved, you may need to submit the issue to those modules as well.

# data[].attributes.body.processed
Note: As of September 21, 2021, this project appears to no longer be supported. If you are interested in taking this project over, or you as the project maintainer feel this message has been posted in error, please reply to https://www.drupal.org/project/projectownership/issues/3238142.

The Glossary module helps newbies understand the jargon which always crops up when specialists talk about a topic. Doctors discuss CBC and EKG and CCs. Web developers keep talking about CSS, P2P, XSLT, etc. This is all intimidating for newbies.

The glossary module scans posts for glossary terms (including synonyms). The glossary indicator is inserted after every found term, or the term itself is turned into an indicator depending on the site settings. By hovering over the indicator, users may learn the definition of that term. Clicking the indicator leads the user to that term presented within the whole glossary or directly to the detailed description of the term, if available.

The glossary uses Drupal's built in taxonomy feature, so you can organize your terms in a Drupal vocabulary. This allows you to create hierarchical structures, synonyms and relations. Glossary terms are represented with the taxonomy terms in the glossary vocabulary. Descriptions are used to provide a short explanation of the terms. You can attach nodes to the terms to provide detailed explanation on the keywords.

Please, any time you download a new version, use the "Clear Cache" button on the settings page or you may not see the new features for some time.

The Glossary module will call the Taxonomy Image module, if it's enabled, to allow you to display an image for each term in the glossary.

We will also work with the Hovertips and Clicktips module to produce fancier hovertips. This also allows the tip to "glossarize" another level deep within the glossary definition.

Firefox "fix" for hover tips: there's a Firefox add-in called "Long Titles" that allow the tool-tips display to be expanded to include the whole tip.

Note: This module does not, nor ever will, move the vocabulary management out of the Administration menu. That can be done by other modules. For example, see Taxonomy Delegate or Vocabulary Permissions.

Some people have asked the difference between this module and G2. There is a Comparison of "Glossary"-type modules.
Back to top
Showcase

If you are using this module and would like to showcase your site here, please send me the link (use my Contact form).

http://www.valueofbiotech.com/biotech-basics/glossary

Back to top
Drupal 7

Yes, we have begun a 7.x branch. If you are not willing to submit patches, please don't even try to use it yet.

Issues

As with all contributed modules, when considering submitting an issue:

Read the documentation (two or three times is better).

Use the "Clear Cache" button on the settings page and retry the problem.

Review the existing issues list. (Don't forget to select "<all>" for the "Status" field.)

Gather all the appropriate information. This may include (but is not limited to):

Drupal version.

Browser type and version.

Database type and version.

Error messages, if any.

Module settings.

Submit the issue. If other modules are involved, you may need to submit the issue to those modules as well.

Back to top

# data[].attributes.body.summary
Note: As of September 21, 2021, this project appears to no longer be supported. If you are interested in taking this project over, or you as the project maintainer feel this message has been posted in error, please reply to https://www.drupal.org/project/projectownership/issues/3238142.

# data[].attributes.body.value
Enables the organization of users into user groups. Also implements access control at the per-node level.

The groups.module is currently not being developed. I need to evaluate if a combination of taxonomy_access and organic groups module can take over the task that I designed this module for.

# data[].attributes.body.processed
Enables the organization of users into user groups. Also implements access control at the per-node level.

The groups.module is currently not being developed. I need to evaluate if a combination of taxonomy_access and organic groups module can take over the task that I designed this module for.

# data[].attributes.body.value
Allows Drupal to use the HTMLArea WYSIWYG formatter to replace text area fields.

If you are having any issues with strange things happening in Xinha, please test it at the http://xinha.python-hosting.com
This module is no longer being actively maintained. If you would like to take over htmlarea please contact me and I will reassign it to you.

# data[].attributes.body.processed
Allows Drupal to use the HTMLArea WYSIWYG formatter to replace text area fields.

If you are having any issues with strange things happening in Xinha, please test it at the http://xinha.python-hosting.com

This module is no longer being actively maintained. If you would like to take over htmlarea please contact me and I will reassign it to you.

# data[].attributes.body.value
This is a HTML correcting module. The filter scans the input, builds up a list of open tags and closes them when needed.

Note that it does not validate the document according to the HTML specifications, but merely ensures that any tags are properly nested.

This module will be part of Drupal 6 and is no longer under development in contrib.

# data[].attributes.body.processed
This is a HTML correcting module. The filter scans the input, builds up a list of open tags and closes them when needed.

Note that it does not validate the document according to the HTML specifications, but merely ensures that any tags are properly nested.

This module will be part of Drupal 6 and is no longer under development in contrib.

# data[].attributes.body.value
This module tidies Drupal's HTML output with HTML Tidy by optionally sanitizing it when it is saved or when it is displayed, like a traditional input formatter. Missing and mis-ordered tag components are replaced and reordered automatically so that user input doesn't break site structure with open tags and the like. User interface configuration supports:

Code indenting: Automatically format HTML for easier reading, or strip indenting for proper parsing and display in the less compliant browsers.

Word wrapping: Automatically wrap lines in an intelligent fashion once they get to a specified length

Info/Warning/Error information: Optionally appended to pages and includes details about the wrong HTML attributes and W3C validation info.

# data[].attributes.body.processed
This module tidies Drupal's HTML output with HTML Tidy by optionally sanitizing it when it is saved or when it is displayed, like a traditional input formatter. Missing and mis-ordered tag components are replaced and reordered automatically so that user input doesn't break site structure with open tags and the like.

User interface configuration supports:

Code indenting: Automatically format HTML for easier reading, or strip indenting for proper parsing and display in the less compliant browsers.

Word wrapping: Automatically wrap lines in an intelligent fashion once they get to a specified length

Info/Warning/Error information: Optionally appended to pages and includes details about the wrong HTML attributes and W3C validation info.

# data[].attributes.body.value
THIS MODULE IS OBSOLETE. This module allows users with proper permissions to upload images into Drupal. Thumbnails and additional sizes are created automatically. Images could be posted individually to the front page, included in stories or grouped in galleries.
Components
Image module ships with several add-on modules:

Image Gallery: Using taxonomy terms, organize and display your uploaded pictures in galleries (include Views support if you have Views 6.x-2.6 or later).

Image Attach: Allows you to easily attach image nodes to other node types.

Image Import: Simplify adding multiple images by importing images from a directory on the server.

ImageMagick Advanced: Adds advanced ImageMagick options such as image sharpening to the ImageMagick image toolkit. This component is unsupported.

Upgrading

from Drupal 5 to 6: Upgrade to 5.x-2.x first, if you haven't already. Afterwards, try the upgrade to Drupal 6 with 6.x-1.x.

from Drupal 6 to 7: Image node data may be converted to Image fields using Field convert module; the image_legacy module (in this project's git repository's 7.x-1.x branch) provides the necessary field conversion information.

Other features and functionality of the Image module package will be taken over by more generic and dedicated other modules. Most features will be taken over by Media and ImageMagick modules. Status of data migration upgrade paths varies. See [#513096] for details.

Always check the release notes before upgrading, and test the upgrade on a development copy of your site first!
Project status
Given that (a different) Image module is in Drupal 7 core, the contrib Image module remains minimally maintained now. It won't see any new features. Furthermore, very few developers rely on Image module as a site build component, and hence work on an upgrade path from Drupal 6 to Drupal 7 update is glacial. If you want to see this happen, please consider contributing below. Further details on this here: [#1665912].
Credits
Current maintainers:

Daniel F. Kudwien (sun)

Joachim Noreiko (joachim)

Previous maintainers:

Andrew Morton (drewish)

James Walker (walkah)

# data[].attributes.body.processed
THIS MODULE IS OBSOLETE.

This module allows users with proper permissions to upload images into Drupal. Thumbnails and additional sizes are created automatically.

Images could be posted individually to the front page, included in stories or grouped in galleries.

Components

Image module ships with several add-on modules:

Image Gallery: Using taxonomy terms, organize and display your uploaded pictures in galleries (include Views support if you have Views 6.x-2.6 or later).

Image Attach: Allows you to easily attach image nodes to other node types.

Image Import: Simplify adding multiple images by importing images from a directory on the server.

ImageMagick Advanced: Adds advanced ImageMagick options such as image sharpening to the ImageMagick image toolkit. This component is unsupported.

Upgrading

from Drupal 5 to 6: Upgrade to 5.x-2.x first, if you haven't already. Afterwards, try the upgrade to Drupal 6 with 6.x-1.x.

from Drupal 6 to 7: Image node data may be converted to Image fields using Field convert module; the image_legacy module (in this project's git repository's 7.x-1.x branch) provides the necessary field conversion information.

Other features and functionality of the Image module package will be taken over by more generic and dedicated other modules. Most features will be taken over by Media and ImageMagick modules. Status of data migration upgrade paths varies.
See [#513096] for details.

Always check the release notes before upgrading, and test the upgrade on a development copy of your site first!

Project status

Given that (a different) Image module is in Drupal 7 core, the contrib Image module remains minimally maintained now. It won't see any new features. Furthermore, very few developers rely on Image module as a site build component, and hence work on an upgrade path from Drupal 6 to Drupal 7 update is glacial. If you want to see this happen, please consider contributing below. Further details on this here: [#1665912].

Credits

Current maintainers:

Daniel F. Kudwien (sun)

Joachim Noreiko (joachim)

Previous maintainers:

Andrew Morton (drewish)

James Walker (walkah)

Back to top

# data[].attributes.body.value
The main advantage of the import module over the default aggregatoris that RSS items are stored as first class nodes. That means that they can be promoted to home page, queued, commented upon, etc. Anything you can do with a normal node can be done with these feed-items.

It is not yet ready for 4.6, nor for HEAD. Allthough It does work, it still needs a lot of love ad time. So you can help.

This module is no longer maintained, HEAD has been removed from CVS. Please look at to Feedparser instead

# data[].attributes.body.processed
The main advantage of the import module over the default aggregatoris that RSS items are stored as first class nodes. That means that they can be promoted to home page, queued, commented upon, etc. Anything you can do with a normal node can be done with these feed-items.

It is not yet ready for 4.6, nor for HEAD. Allthough It does work, it still needs a lot of love ad time. So you can help.

This module is no longer maintained, HEAD has been removed from CVS. Please look at to Feedparser instead

# data[].attributes.body.value
Русская версия
English version below
Возможности модуля

Показывает на отдельной вкладке ("Ключевые слова") ноды список найденных ключевых слов и фраз, а также их плотность в тексте ноды

На странице настроек модуля можно гибко настроить параметры поиска ключевых слов ноды

На странице "Все ключевые слова сайта" показывается список всех ключевых слов и плотность по всему сайту, а также ноды в которых эти ключевые слова были найдены.

Модуль может сохранить найденные ключевые слова и выбранный словарь таксономии. Этот словарь можно использовать в модуле Meta Tags для создания мета-тега keywords или просто вывести как теги ноды.

Модуль содержит 2 списка стоп-слов - русский и английский. Их использование можно отключить. Исключение стоп-слов гарантирует, что малозначимые слова и слова длиной меньше 2х символов не попадут в ключевые слова.

По умолчанию к тексту ноды для поиска ключевых слов добавляется загловок ноды и текст анонса.

Особенности применения
Поиск ключевых слов в ноде происходит при сохранении ноды, поэтому:

Если ноды были созданы до установки модуля Keywords, то при запуске cron для них тоже будут вычисляться ключевые слова

Ключевые слова вычисляются также при посещении вкладки "Ключевые слова" ноды, если они не были найдены раньше

Также список ключевых слов ноды создаётся автоматом при пересохранении ноды.

Настройки модуля влияют на результат поиска ключевых слов, поэтому в модуле реализована история изменения настроек модуля. Таким образом, если настройки модуля поменялись, то информация о ключевых словах нод (сами ключевые слова и их плотность) становится неверной. Если cron настроен верно и выполняется регулярно, то после смены настроек все ноды проиндексированные со старыми настройками будут заново обработаны при запуске cron. Благодаря истории изменения настроек модуля через какое-то время все ноды будут заново обработаны с новыми настройками.
Благодарности

Консультации по SEO-вопросам: andron13

Drupal-консультации: сайт Рецепты создания сайта на Drupal

English version
Русская версия выше
Features

Display list of node's keywords and their densities at tab "Keywords"

Display list of keywords and their densities for all site's nodes at page "All keywords". Links to nodes where keyword was found also displayed.

At module settings page you can configure proccess of finding of keywords in nodes

Module can save node's keywords as taxonomy terms to selected vocabulary. Later you can use this vocabulary to tell Meta Tags module use this terms for meta-tag "keywords" or use as usual tags.

Module contain 2 lists of stop-words - russian and english. You can disable using this lists but if you're using excluding stop-words you will not see useless words and words with lenght less than 2 chars in keywords list.

By default module adds to node's body text title and teaser to find more keywords and count real density.

Use Cases
Kyewords searching happens whan node is saving so:

If nodes was created before module was installed than when cron is running they will be parsed for keywords.

Keywords also will be generated when you're visiting tab "Keywords" if keywords was not generated before.

Keywords list is generated automaticly when node is resaved

Generating keywords depends on module settings. This means that settings changes will made all previous keywords not valid. To avoid this module has own history of settings changes. If module setting was changed and cron is running regullary than all nodes that already has keywords will be regenerated again using new settings.

# data[].attributes.body.processed
Back to top
Русская версия

English version below

Возможности модуля

Показывает на отдельной вкладке ("Ключевые слова") ноды список найденных ключевых слов и фраз, а также их плотность в тексте ноды

На странице настроек модуля можно гибко настроить параметры поиска ключевых слов ноды

На странице "Все ключевые слова сайта" показывается список всех ключевых слов и плотность по всему сайту, а также ноды в которых эти ключевые слова были найдены.

Модуль может сохранить найденные ключевые слова и выбранный словарь таксономии. Этот словарь можно использовать в модуле Meta Tags для создания мета-тега keywords или просто вывести как теги ноды.

Модуль содержит 2 списка стоп-слов - русский и английский. Их использование можно отключить. Исключение стоп-слов гарантирует, что малозначимые слова и слова длиной меньше 2х символов не попадут в ключевые слова.

По умолчанию к тексту ноды для поиска ключевых слов добавляется загловок ноды и текст анонса.

Особенности применения

Поиск ключевых слов в ноде происходит при сохранении ноды, поэтому:

Если ноды были созданы до установки модуля Keywords, то при запуске cron для них тоже будут вычисляться ключевые слова

Ключевые слова вычисляются также при посещении вкладки "Ключевые слова" ноды, если они не были найдены раньше

Также список ключевых слов ноды создаётся автоматом при пересохранении ноды.

Настройки модуля влияют на результат поиска ключевых слов, поэтому в модуле реализована история изменения настроек модуля. Таким образом, если настройки модуля поменялись, то информация о ключевых словах нод (сами ключевые слова и их плотность) становится неверной.

Если cron настроен верно и выполняется регулярно, то после смены настроек все ноды проиндексированные со старыми настройками будут заново обработаны при запуске cron.
Благодаря истории изменения настроек модуля через какое-то время все ноды будут заново обработаны с новыми настройками.

Благодарности

Консультации по SEO-вопросам: andron13

Drupal-консультации: сайт Рецепты создания сайта на Drupal

Back to top
English version

Русская версия выше

Features

Display list of node's keywords and their densities at tab "Keywords"

Display list of keywords and their densities for all site's nodes at page "All keywords". Links to nodes where keyword was found also displayed.

At module settings page you can configure proccess of finding of keywords in nodes

Module can save node's keywords as taxonomy terms to selected vocabulary. Later you can use this vocabulary to tell Meta Tags module use this terms for meta-tag "keywords" or use as usual tags.

Module contain 2 lists of stop-words - russian and english. You can disable using this lists but if you're using excluding stop-words you will not see useless words and words
with lenght less than 2 chars in keywords list.

By default module adds to node's body text title and teaser to find more keywords and count real density.

Use Cases

Kyewords searching happens whan node is saving so:

If nodes was created before module was installed than when cron is running they will be parsed for keywords.

Keywords also will be generated when you're visiting tab "Keywords" if keywords was not generated before.

Keywords list is generated automaticly when node is resaved

Generating keywords depends on module settings. This means that settings changes will made all previous keywords not valid. To avoid this module has own history of settings changes.

If module setting was changed and cron is running regullary than all nodes that already has keywords will be regenerated again using new settings.
Back to top

# data[].attributes.body.summary
En: Module counts node's keywords and their density and provide a list of keywords of all site's nodes.
Ru: Модуль вычисляет ключевые слова нод и их плотность. На отдельной странице показывается список всех ключевых слов сайта (семантическое ядро).
Ua: Модуль знаходить ключові слова у тексті нод та розраховує їх відносную кількість для однієї ноди та всього сайту.

# data[].attributes.body.value
Listhandler is a module that marries mailing list discussions and Drupal forums.
Working together with the Mailhandler module your Drupal site will monitor a mailbox for incoming email and post that to a specified forum. Any posts to the forum will conversely be posted to the mailing list.

Before submitting a bug, please check all open issues.

Related modules

The E-mail Input Filter module has been specifically written to provide a web friendly look to email mark-up.

Current Status

The 6.x-1.1 version is only a single commit since the 1.0 release, a commit that addresses a previous security concern with this module. If you are using the 1.0, please update!

The current -dev version includes a number of other bugfixes and enhancements from the previous developer.

As the current maintainer, my intentions are to get a 6x release that is stable and addresses any critical bugs, and also to begin work on a version for 7x that works with the latest version of mailhandler. That will begin after I'm confident in the 6x version, which the majority of people are currently using, so is taking priority for now.

# data[].attributes.body.processed
Listhandler is a module that marries mailing list discussions and Drupal forums.

Working together with the Mailhandler module your Drupal site will monitor a mailbox for incoming email and post that to a specified forum. Any posts to the forum will conversely be posted to the mailing list.

Before submitting a bug, please check all open issues.

Related modules

The E-mail Input Filter module has been specifically written to provide a web friendly look to email mark-up.

Current Status

The 6.x-1.1 version is only a single commit since the 1.0 release, a commit that addresses a previous security concern with this module. If you are using the 1.0, please update!

The current -dev version includes a number of other bugfixes and enhancements from the previous developer.

As the current maintainer, my intentions are to get a 6x release that is stable and addresses any critical bugs, and also to begin work on a version for 7x that works with the latest version of mailhandler. That will begin after I'm confident in the 6x version, which the majority of people are currently using, so is taking priority for now.
Back to top

# data[].attributes.body.value
This module has been comitted to core. It will be included in the Drupal 4.5 release.
This is an extended locale module that enables you to share translations through the use of PO files. PO files are files containing translations as used by the GNU gettext programm.

User contributed PO files for various languages can be found in contrib CVS.

If your language is not present, create a feature request against this project and I will add an empty PO file for your language. You can then get a PO file editor and start translating.

Recommended PO file editors are (in no particular order):

XEmacs with po-mode

GNU Emacs with po-mode

KBabel

poEdit

poEdit is said to not yet support multiple plural forms. Be sure to get a recent version for all editors, multiple plural forms are a recent additionion to the gettext standard.

# data[].attributes.body.processed
This module has been comitted to core. It will be included in the Drupal 4.5 release.

This is an extended locale module that enables you to share translations through the use of PO files. PO files are files containing translations as used by the GNU gettext programm.

User contributed PO files for various languages can be found in contrib CVS.

If your language is not present, create a feature request against this project and I will add an empty PO file for your language. You can then get a PO file editor and start translating.

Recommended PO file editors are (in no particular order):

XEmacs with po-mode

GNU Emacs with po-mode

KBabel

poEdit

poEdit is said to not yet support multiple plural forms. Be sure to get a recent version for all editors, multiple plural forms are a recent additionion to the gettext standard.

# data[].attributes.body.value
This module will not be supplied for Drupal 4.5. Similar functionality has been added to the Drupal core locale module.
This module allows to import/export Drupal translations using GNU Gettext files. It can export existing translations as PO files, or templates for new translations as POT files.

# data[].attributes.body.processed
This module will not be supplied for Drupal 4.5. Similar functionality has been added to the Drupal core locale module.

This module allows to import/export Drupal translations using GNU Gettext files. It can export existing translations as PO files, or templates for new translations as POT files.

# data[].attributes.body.value
Deprecated in favor of Multiple Email

With this module, a user may associate additional email addresses with his account.
These addresses are used by mailhandler.module to authenticate incoming emails.

# data[].attributes.body.processed
Deprecated in favor of Multiple Email

With this module, a user may associate additional email addresses with his account.
These addresses are used by mailhandler.module to authenticate incoming emails.

# data[].attributes.body.value
Create nodes by email!
Mailhandler uses Feeds to let you post nodes by email. It takes mail (usually from an IMAP mailbox) and imports it as whatever type of content you choose. Plug-in modules allow you to do more awesome things like post comments, select different authentication methods, and set properties such as published / sticky status using "commands". Hugely powerful and flexible, but includes a "quick-start" module to help get you started.
Drupal 8 release
Mailhandler for Drupal 8 was developed as a part of Google Summer of Code 2016, following the road map and motivated by Mailhandler for Drupal 7. The Drupal 8 version of the module is based on Inmail module and creates a node (of configured content type) from email. Beside the configured content type, you can specify the content type directly in your email subject. It enables you to select different authentication methods and mail analyzers as well. Mailhandler Comment is a submodule that allows you to post comments by email. In order to get started with D8 version, feel free to check Installation and How-To read me sections.
Documentation
For a complete list of features, see the Mailhandler 2.x README file. To get started, see the "Quick setup" section of the Mailhandler 2.x INSTALL file. Community documentation:

How to set up a hybridized mailing list / forum

How to set up a mailing list

Mailhandler handbook

Mailhandler Add-ons

Mail Comment - post comments by email

Media Link Command - extract video links from emails

Single Mailbox - use catch-all mailboxes

Send To Auth - authenticate users based on send-to address

History
Mailhandler was originally called "mail2web", and the 1.x branch was previously maintained by Ian Ward and moshe weitzman. Sponsorship has been provided by Praece.

# data[].attributes.body.processed
Create nodes by email!

Mailhandler uses Feeds to let you post nodes by email. It takes mail (usually from an IMAP mailbox) and imports it as whatever type of content you choose. Plug-in modules allow you to do more awesome things like post comments, select different authentication methods, and set properties such as published / sticky status using "commands". Hugely powerful and flexible, but includes a "quick-start" module to help get you started.

Drupal 8 release

Mailhandler for Drupal 8 was developed as a part of Google Summer of Code 2016, following the road map and motivated by Mailhandler for Drupal 7.

The Drupal 8 version of the module is based on Inmail module and creates a node (of configured content type) from email. Beside the configured content type, you can specify the content type directly in your email subject. It enables you to select different authentication methods and mail analyzers as well.

Mailhandler Comment is a submodule that allows you to post comments by email.

In order to get started with D8 version, feel free to check Installation and How-To read me sections.

Documentation

For a complete list of features, see the Mailhandler 2.x README file.

To get started, see the "Quick setup" section of the Mailhandler 2.x INSTALL file.

Community documentation:

How to set up a hybridized mailing list / forum

How to set up a mailing list

Mailhandler handbook

Mailhandler Add-ons

Mail Comment - post comments by email

Media Link Command - extract video links from emails

Single Mailbox - use catch-all mailboxes

Send To Auth - authenticate users based on send-to address

History

Mailhandler was originally called "mail2web", and the 1.x branch was previously maintained by Ian Ward and moshe weitzman. Sponsorship has been provided by Praece.
Back to top

# data[].attributes.body.value
For Drupal 4.7 and Drupal 5: If you want full control over your member listings, I would advise to use usernode with views integration.

For Drupal 5 and 6: Here's a small introduction on how to create a user listing in views.

# data[].attributes.body.processed
For Drupal 4.7 and Drupal 5: If you want full control over your member listings, I would advise to use usernode with views integration.

For Drupal 5 and 6: Here's a small introduction on how to create a user listing in views.

# data[].attributes.body.value
The site neighboordhood is a collection of sites that is related to your site in some way. These sites can be tracked for changes, or can be fully syndicated.

# data[].attributes.body.processed
The site neighboordhood is a collection of sites that is related to your site in some way. These sites can be tracked for changes, or can be fully syndicated.

# data[].attributes.body.value
This module gives pleasant-looking DHTML CSS tooltips on Internet Explorer & Gecko browsers (Mozilla, Netscape 7, etc.)

It knows the difference between internal and external links (provided the internal ones are fully-qualified), and displays the URL of the page at the bottom of the tooltip for external links only.
Last release was 4.5

# data[].attributes.body.processed
This module gives pleasant-looking DHTML CSS tooltips on
Internet Explorer & Gecko browsers (Mozilla, Netscape 7, etc.)

It knows the difference between internal and external links
(provided the internal ones are fully-qualified), and displays
the URL of the page at the bottom of the tooltip for external
links only.

Last release was 4.5

# data[].attributes.body.value
Notify is a lightweight module for sending plain text email notifications about new nodes and comments posted on a Drupal web site. Users may subscribe to notifications about all new content, or only subscribe to specific content types. 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. The notifications are sent out in batches at a frequency determined by the administrator. The administrator also decides what content type(s) to make available for notification subscriptions. Ordinary users can turn notifications on and off, select what content type(s) to subscribe to and whether to also be notified about comments attached to subscribed content types.
Notify Views Integration (D7 only)
The Drupal 7 branch of the project contains a sub-module: Notify Views Integration, that tells the Views module about the Notify database so you can create listings of users by Notify subscriptions status for export or administration. The sub-module requires Views and CTools.
Bulk e-mail handling
The Drupal 7 branch of the project contained a built-in custom queue handler to split a batch over several cron run. This has been deprecated in the 2.0 branch. Instead, if you are sending out so many notifications that you experience time-out problems, install and configure Queue Mail to handle bulk e-mail.
Support Status
Reported bugs for the Drupal 7 and 10 branches will be fixed in a timely manner (provided the bug report describes how to reproduce the problem at will). Older versions are no longer supported, nor is Drupal 8/9. Community support in the form of patches are very welcome for both the Drupal 7 and Drupal 10 branches. Bug reports with patches will be given priority. For QA, the project needs community support in the form of reviews of patches, development versions and releases. The primary goal of the notify module is to remain a light-weight and simple alternative to the more comprehensive notification frameworks, (e.g.: Subscriptions/Notifications). This means that not all feature requests will be implemented, even if they are a good idea. Feature requests accompanied by patches are more likely to make it into a release. The maintainer hopes that the community is willing to help out by answering & closing support requests.
Seeking co-maintainer
We want to add another co-maintainer to the team, check out [#3302634] for details.
Similar projects

Admin Content Notification

DANSE Drupal - Audit - Notification - Subscription - Event

You may also want to explore these pages on Drupal.org and Groups.Drupal.org: Comparison of email newsletter oriented modules and Notifications via e-mail comparison, but unfortunately they look pretty outdated.
Maintainers

Matt Chapman is the project owner.

Gisle Hannemyr maintains all supported branches.

Past maintainers:

Kjartan Mannes created the project.

Rob Roy Barreca was a previous maintainer.

Larisse Amorim was a previous maintainer.

# data[].attributes.body.processed
Notify is a lightweight module for sending plain text email notifications about new nodes and comments posted on a Drupal web site.

Users may subscribe to notifications about all new content, or only subscribe to specific content types.

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.

The notifications are sent out in batches at a frequency determined by the administrator. The administrator also decides what content type(s) to make available for notification subscriptions.

Ordinary users can turn notifications on and off, select what content type(s) to subscribe to and whether to also be notified about comments attached to subscribed content types.
Back to top
Notify Views Integration (D7 only)

The Drupal 7 branch of the project contains a sub-module: Notify Views Integration, that tells the Views module about the Notify database so you can create listings of users by Notify subscriptions status for export or administration.

The sub-module requires Views and CTools.
Back to top
Bulk e-mail handling

The Drupal 7 branch of the project contained a built-in custom queue handler to split a batch over several cron run. This has been deprecated in the 2.0 branch. Instead, if you are sending out so many notifications that you experience time-out problems, install and configure Queue Mail to handle bulk e-mail.
Back to top
Support Status

Reported bugs for the Drupal 7 and 10 branches will be fixed in a timely manner (provided the bug report describes how to reproduce the problem at will).

Older versions are no longer supported, nor is Drupal 8/9.

Community support in the form of patches are very welcome for both the Drupal 7 and Drupal 10 branches. Bug reports with patches will be given priority. For QA, the project needs community support in the form of reviews of patches, development versions and releases.

The primary goal of the notify module is to remain a light-weight and simple alternative to the more comprehensive notification frameworks, (e.g.: Subscriptions/Notifications). This means that not all feature requests will be implemented, even if they are a good idea. Feature requests accompanied by patches are more likely to make it into a release.

The maintainer hopes that the community is willing to help out by answering & closing support requests.

Seeking co-maintainer

We want to add another co-maintainer to the team, check out [#3302634] for details.
Back to top
Similar projects

Admin Content Notification

DANSE Drupal - Audit - Notification - Subscription - Event

You may also want to explore these pages on Drupal.org and Groups.Drupal.org: Comparison of email newsletter oriented modules and Notifications via e-mail comparison, but unfortunately they look pretty outdated.
Back to top
Maintainers

Matt Chapman is the project owner.

Gisle Hannemyr maintains all supported branches.

Past maintainers:

Kjartan Mannes created the project.

Rob Roy Barreca was a previous maintainer.

Larisse Amorim was a previous maintainer.

Back to top

# data[].attributes.body.value
Exports site feed directory in OCS (Open Content Syndication) format.
Currently supports the feeds you have subscribed in your Drupal site.

# data[].attributes.body.processed
Exports site feed directory in OCS (Open Content Syndication) format.
Currently supports the feeds you have subscribed in your Drupal site.

# meta.omitted.detail
Some resources have been omitted because of insufficient authorization.

# meta.omitted.links.item--bkfULcO.meta.detail
The current user is not allowed to GET the selected resource.

# meta.omitted.links.item--csErw2F.meta.detail
The current user is not allowed to GET the selected resource.

# meta.omitted.links.item--202TLtZ.meta.detail
The current user is not allowed to GET the selected resource.

# meta.omitted.links.item--uwdb2lF.meta.detail
The current user is not allowed to GET the selected resource.

# meta.omitted.links.item--nZRibSf.meta.detail
The current user is not allowed to GET the selected resource.

# meta.omitted.links.item--jmYoUvf.meta.detail
The current user is not allowed to GET the selected resource.

# meta.omitted.links.item--5XtRtL5.meta.detail
The current user is not allowed to GET the selected resource.

# meta.omitted.links.item--ZZzAM0P.meta.detail
The current user is not allowed to GET the selected resource.

# meta.omitted.links.item--yqRGS8F.meta.detail
The current user is not allowed to GET the selected resource.

# meta.omitted.links.item--n5Wf9q6.meta.detail
The current user is not allowed to GET the selected resource.

# meta.omitted.links.item--t2Sf344.meta.detail
The current user is not allowed to GET the selected resource.