Wayback Submit to Archive.org

You're producing high quality work and you'd like to keep a public record of it on Archive.org.

The Wayback Submit module will submit all your url's to The Wayback Machine at Archive.org.

Thus you should be able to prove that you came up with some great idea first. Or, if your research is taken offline for political reasons, you'll still be able to point to it at The Wayback Machine.

The Wayback Submit module enables you to save your entire site to The Wayback Machine

• nodes
• views
• terms
• manual URLs (any URL you care to type in)

With nodes you get to choose which content types to automatically save to The Wayback Machine and how often.

Caution

his module will spill all your secrets to the Wayback Machine if you are not careful. Spend some time deciding which node types should be submitted before you turn on submission to The Wayback Machine.
If you're a security through obscurity kinda guy, you should probably not install this module.

Setup

• Install the module.
• Grant permissions at People > Permissions.
• Configure it at Configuration > Search and meta data > Wayback Submit.
• Turn on submission to The Wayback Machine

Configuration

By default the Wayback Submit module will submit all node types on schedule, meaning that a number will be submitted on cron with a predetermined interval set to 30 days.
But you can select settings for individual content types and fiddle with the time between submissions.

The options for the individual node type are

• Never: don't submit the node to Archive.org.
• On submit: submit the node immediately when saved (and published).
• On submit, then on schedule: as above, but change status to On schedule when done.
• On schedule: submit the node with the frequency set in the global settings.

The Wayback Submit Node submodule has an additional setting under each node type: Allow individual overrides. Checking this will allow for speedier submission of individual nodes.

Example: if Allow individual overrides is checked for node type Article each and every node of type Article you edit will have an option to submit the node to The Wayback Machine immediately after editing it. This setting can be found in the accordion part of the node editing form.

Submission frequency

Archive.org isn't blitz fast when registering the submitted URLs and the submission also includes the rendering time for the relevant Drupal page, so it's recommended that you don't submit too many pages too often. Also Archive.org may have some flooding scheme running, which you may bump into.
If you do the submissions manually on save, you have no problems, but when using the scheduled submit functions and cron, limit the number of entities to something reasonable. Since this module looks at a number of entities in each cron run, but doesn't necessarily submit them all, a number around 100 nodes seems to work well. The module takes a tenth this number of terms and views, since these are typically fewer and take longer to render.
You can adjust the number of nodes depending on your site's size and how often you run cron.
You want to make sure that the combination of the number of nodes, the submit frequency and the cron frequency adds up to that all entities actually do get checked at least once for every submission period. The default settings should work well for most sites, unless you run cron really rarely - like only once a day.

Logging

You'll find a delightfully detailed Wayback Submit Log under Reports.
Individual entries will link to the archived page at Archive.org and offer you a button called "Submit right now". This will submit the node (or view or term) to The Wayback Machine instantly.

Help

Look at the pictures here at drupal.org to get an idea of how to configure it properly. There's also some advanced help available.

Known bugs/TODO

Support of Multilingual sites might be spotty.
The user interface needs an overhaul.