Snapshot is a drupal module for making clean snapshot of drupal website. Website, media and database are snapshot. For now, just Mysql with MyIsam engine is supported. Different snapshot method can be used, total or incremental.

The FeedAPI Language Filter is a simple add-on for the FeedAPI Item Filter module that allows incoming feed items to be fil

Subscribers Counter displays a number of site's feed subscribers in a block with link to main feed.

This module creates a CCK field that accepts RSS urls.

The Save to FTP module allows for saving a node as a .html file on a FTP Server.

After a node has been saved, and a path is given, if the user has been given the "Save to FTP" permission a form is added on the node edit page which is activated by selecting the "Publish to FTP" button.

How SaveToFTP compares to other Contributed Modules

SaveToFTP has one main purpose, export nodes as .html files to a FTP Server. In my use case, the FTP Server is also a web server, so I use this module to export static .html to a web server that doesn't have PHP on it. This way I have a static version of the site without the overhead of PHP/Drupal, but can still use Drupal for the content management.

[Server with Drupal] ----> [FTP/Web Server]

Please see the Import / Export wiki page for a full comparison of import/export modules similar to this one.

7.x-1.x release

This is the initial release of the 7.x. branch. It has been used on a clean install of Drupal 7 and found to work.

To Dos: Add tests and features
Seeking sponsorship to create a Save to S3 option

6.x-2.x releases

The module automatically handles all html, css, and js.

5.x releases

5.x is deprecated. If you still want a 5.x. release you can find it here: http://drupal.org/node/433922/release

This project includes a client-server set of modules designed to implemenet centralized activity logging from client drupal site(s) to a master server.

Note: this model works for IPhone in conjunction with Drupal Notifier.

Module Drupal Notifier provides information on the status of installed and active modules for IPhone App Drupal Notifier.
With every request from IPhone App Drupal Notifier the website sends another request to update.drupal.org service and provides information in xml format.
This programm reflects status by modules for your website. It tells you which modules need to be updated and what new versions are available.

A collection of modules to provide an API to integrate with GeoNames webservices. The modules in this package enable access to all information provided by the XML-based Services from GeoNames.

This project is maintained by lyricnz and SeroSero.

Supported GeoNames Services Include:

• GeoNames Fulltext Search (search)
• Reverse Geocoding
  • Country Subdivision (countrysubdivision)
  • Find nearby (findnearby)
  • Find nearby Place Name (nearbyplace)
  • Find nearby Postal Codes (nearbypostalcodes)
  • Find nearby Wikipedia Entries (nearbywikipedia)
• Place Hierarchy
  • Neighbours (neighbours)
  • Siblings (siblings)
  • Hierarchy (hierarchy)
  • Children (children)
• Postal Code Country Info (postalcodecountryinfo)
• Postal Code Search (postalcodesearch)
• Country Code (reverse geocoding) (countrycode)
• Country Info (Bounding Box, Capital, Area in square km, Population) (countryinfo)
• Timezone (timezone)
• Wikipedia Articles from Bounding Box (wikipediabbox)

This module provides an easy way to import previously exported Views definitions.

This module provides single sign-in and user database integration for MediaWiki as slave of Drupal. It is set up so that users sign in to the Drupal site, and as a result they automatically become logged in to the wiki. User entries are still created in the wiki's user table and are kept up to date on each login with email and real name. This does not include content exchange or wiki parsing, for that, see the Mediawiki module.

This module provides an easy way to import previously exported CCK definitions.

This module is an auxiliary parser module for feedapi. It is intended to be used with one of the other parsers. It will parse out all of the fields in the feed, regardless of namespace. May times feeds will have extra fields that are not part of the atom, or rss spec, often in there own namespace (such as using dc:creator instead of original author). The default parser will not parse that data, FeedAPI Exhaustive Parser will pull out those fields.

I think the best way to understand is to use try it, with feed Element Mapper.
Hit a NYtimes feed like http://feeds.nytimes.com/nyt/rss/Business, and when you go to map the fields you will see that the feed has lots of fields (like media:credit, media:description, dc:creator) that are not available with the standard parser.

FeedAPI Exhaustive Parser makes those fields available. It also make all elements of the feed itself available. In the nytimes example you will see the language and the copyright are listed on the feed but not the individual items, if you wanted to store copyright in a cck field on each node, this would allow that.

It parses all elements of the feed items and places them in the options->all feed object of feedapi.

Pretty much every import/export module for Drupal (and there are some) has a tendency to implement their own hooks for retrieving information about node fields, and the CCK support that comes with them. Also, pretty much all of these solutions have a tendency to tie their hooks and field discovery to their module in some kind of way.

If you are a module developer and want to retrieve information about which kinds of stuff exists in a node, and what you can do with it... where do you get that information? Drupal core does not provide a registry for all node properties, let alone additional information like schema information or a standardized way to retrieve or set that data. CCK covers only a part of the whole node, disregarding the more fundamental properties like node author or creation date.

under construction

Module is abandoned, no development will be done

This module is unmaintained.

Sorry folks. Since I left my previous (Drupal-related) company, I haven't found time to work on this module, and without a strong time commitment I don't believe this is going to go somewhere. The good news is that the number and quality of other import/export modules has increased, so you'll likely find something that suits your needs. (See the next point.) The other good news is that a new module called Rules Transformers takes many of the ideas from this module and sets out to implement them on top of the magnificent Rules module, starting from Drupal 7.x and with an entirely new code base.

Good luck with your quest for the perfect data transformation module!

Upfront note for people researching modules.
There are a multitude of different import and export modules in existence to handle the complex task of getting data from other systems into Drupal. A wiki page has been created in an attempt to focus the efforts of the module developers and provide a handy guide for users looking to make a decision.

The HTPasswd Sync module let you synchronize a htpasswd and a htgroup file with drupal user database.

This module assists you in writing help texts suitable for use with the Advanced Help module by allowing you to write your help texts in Drupal books. Once you've written the help texts you can inject help icons into any page, form or form item, linking them to the book page that should later appear. The final step is to export all of the help texts as well as the injection data into a new module consisting of Advanced Help files and a simple generated module. The module has all of the information needed to inject the help icons into the right pages, forms, and form elements. The new generated module is ready for distribution as a standalone project or a submodule in a larger project.

Workflow and Use Cases

Advanced Help Injection and Export addresses four workflows where help texts need to be written:

1. You want to document a website and the help texts are in flux. Write your texts in a Drupal book, inject the context sensitive help icons throughout the website, and let the Help Inject module provide the end-user the help icons.
2. You want to document a website and the help texts are finished. Write your texts in a Drupal book, inject the context sensitive help icons throughout the website, and export the module. That module is now the complete documentation for a particular website.
3. You want to document a module. Write your texts in a Drupal book, inject the context sensitive help icons into the pages and forms that your module supplies, and export the new generated help module. Distribute the new generated help module as a sub module with your module.
4. You want to document a larger project, such as Drupal core. Write your texts in a Drupal book, inject context sensitive help icons throughout the larger project, and export the new generated help module. Distribute the new generated help module as a module with your larger project.

The Advanced Help Injection and Export module has the following benefits to help writers and module maintainers:

1. Help writers can use web based tools that they're familiar with, and which are collaboration friendly (Drupal books).
2. Module maintainers don't need to pollute their code with theme() calls to inject the help icons.
3. Help texts can easily be distributed as they are just a collection of HTML files.
4. Help texts are not part of the site's content (so you don't have to worry about help texts showing up in Views, or on the front page).
5. Thanks to the coolness of Advanced Help, help texts are searchable.

The workflow for using this module is:

1. Create your documentation in a book structure.
2. Enable the helpinject module
3. Using the (+) icons that now appear everywhere, "inject" your help into the pages and forms by linking (+) icons to book pages.
4. Export the help to a new module at admin/build/helpinject
5. Move the generated module (found in your files directory) to your sites/all/modules directory.
6. Disable helpinject and enable the module you generated.

The help that you wrote in the Drupal books is now available as advanced help files and gets injected into the right forms and pages.

Uploads and attached files

Files attached to book nodes using the upload module, filefield, imagefield, and any other module that populates node->files, will be copied into the exported help distribution. Furthermore, references to those files in the body text of your book nodes will be updated to that the paths to the files are portable. This makes writing help texts with image or video content a breeze.

Translations

If you have translated your help texts using Drupal's locale and content translation modules, the HelpInject module will export the Advanced Help files and their translations.

Auto-generates HILCC (Hierarchical Interface to the Library of Congress Classification) taxonomy terms for nodes that have LCC call numbers (library-assigned numbers like "QA 76.73 .P224 2005"). This can help you build a Drupal site that auto-organizes by a hierarchic subject tree.

For instance, items with different call numbers like QA76.73 and QA75 would be clustered under the Drupal category Engineering & Applied Sciences > Computer Science. The taxonomy terms are generated during node creation and update, and now optionally during cron runs and using node batch operations (from admin/content/node).

Possible uses are:

• Subject-based search, for instance using the Apache Solr module
• Subject-based breadcrumb, using the Taxonomy Breadcrumb module.

(For an example that uses all these modules, see the links to the demo below).

At one step you create node with translations. Taxonomy and other cck
fields bind to these translations too.

LangsAtOnce creates additional title, body fields for selected languages. So
when you go "create node" page you face with normal fields and
title/body areas. These additional ares will be added as translations.

Utility functions for scholarly publications/content, e.g.

• search, download, and attach PDF according to node title (+ field authors) or from field URL linking to PDF
• rename attached PDFs according to title (+ other fields, e.g. year, author)
• normalize concatenated author list field (lots of diverse variants to consistent Surname, Forname; Sur...)
• split/join authors from/to concatenated/multiple field

Currently, you find the functionality in admin/content/node in the drop down list as well as partly in the menu next to 'edit'; also see admin/settings/scholarly

Related modules

• createfromweb
• citationcounts
• biblio, but biblio_facet won't be available for D6 -- new SoC
• oai2forcck

cck content type definition for import (enable module content copy) via admin/content/types/import available, see cvs

Subscribe users to organic groups.

Existing user can be subscribed to an Organic Group by filling in an autocomplete field with their username.

In development: New and existing users can be mass subscribed to an Organic Group by importing data from a CSV file.

Adds Twitter search functionality to the Twitter module.

This module has been deprecated.

Based on the core aggregator module, makes it possible to "promote" hand-picked items to nodes of the admin's choosing. There are numerous fine node based aggregator modules.