DocumentCloud WordPress plugin
- Upload the contents of the plugin to
- Activate the plugin through the "Plugins" menu
- In your posts, embed documents, pages, or notes using the DocumentCloud button or the
- Optional: Set a default width/height for all DocumentCloud embeds (which can be overridden on a per-embed basis with the
height/widthattributes) at Settings > DocumentCloud. (This default width will only be used if you set
responsive="false"on an embed.)
Upgrading from Navis DocumentCloud: If you're currently using the Navis DocumentCloud plugin (from which this plugin was built), you'll want to deactivate or delete it before installing this plugin.
This plugin allows you to embed DocumentCloud resources using either the raw URL on its own line:
Here's something you should really take a look at: https://www.documentcloud.org/documents/282753-lefler-thesis.html Isn't that interesting?
Or a custom shortcode:
When you save, WordPress fetches and stores the actual embed code HTML from the DocumentCloud servers using oEmbed. You can freely toggle between visual and HTML mode without mangling embed code, and your embed will always be up to date with the latest embed code.
By default, documents will have a responsive width (it will narrow and widen as necessary to fill available content area) and use the theme's default height. If you want to override this, you can either set
responsive="false" or explicitly set a
[documentcloud url="https://www.documentcloud.org/documents/282753-lefler-thesis.html" width="600"]
You can set your own defaults in Settings > DocumentCloud, but default widths will be ignored unless
responsive is disabled:
[documentcloud url="https://www.documentcloud.org/documents/282753-lefler-thesis.html" responsive="false"]
To embed a single page, use any page-specific URL. Pages ignore
width/height and always act responsively:
To embed a note, use any note-specific URL. Notes ignore
width/height and always act responsively:
Here's the full list of embed options you can pass via shortcode attributes; some are specific to the type of resource you're embedding.
url(required, string): Full URL of the DocumentCloud resource.
container(string): ID of element to insert the embed into; if excluded, embedder will create its own container.
height(integer): Height (in pixels) of the embed.
width(integer): Width (in pixels) of the embed. If used, will implicitly set
responsive(boolean): Use responsive layout, which dynamically adjusts width to fill content area. Defaults
responsive_offset(integer): Distance (in pixels) to vertically offset the viewer for some responsive embeds.
page(integer): Page number to have the document scroll to by default.
note(integer): ID of the note that the document should highlight by default.
notes(boolean): Hide or show notes.
search(boolean): Hide or show search form.
sidebar(boolean): Hide or show sidebar.
text(boolean): Hide or show text tab.
zoom(boolean): Hide or show zoom slider.
format(string): Indicate to the theme that this is a wide asset by setting this to
You can read more about publishing and embedding DocumentCloud resources on https://www.documentcloud.org/help/publishing.
How the oEmbed endpoint is discovered
To make a resource discoverable by oEmbed consumers, you can include a
<link> tag that specifies the oEmbed endpoint URL. So in one version of reality, once you tell WordPress "this resource is oEmbeddable", WordPress would cURL the resource URL, look for the oEmbed link tag in its header, pluck out the oEmbed endpoint from the
href, and then hit that endpoint for the embed code. In our actual reality, that's considered a waste of a cURL, so we have to actually describe the format of our oEmbed endpoint within WordPress itself.
Ideally, when WordPress hits our oEmbed service to fetch the embed code, it would obey the
cache_age we return. Despite conversation around this, it doesn't seem to.
Instead, it lets us choose between no cache at all (so every pageload triggers a call to our oEmbed service to get the embed code) or a supposed 24-hour cache stored in the
postmeta table. Unfortunately, our tests seem to show this cache is never expired, which means we can choose between no cache (thus possibly DDOSing ourselves) or a permanent cache (thus possibly having stale embed codes). We've chosen the latter; hopefully this cache does eventually expire, and our embed codes shouldn't change that often anyway.
If you find yourself absolutely needing to expire the cache, though, you have two choices:
- Delete the appropriate
_oembed_*rows from your
- Modify the shortcode attributes for the embed, since this is recognized as a new embed by WordPress.
- Separate the oEmbed config options (provided as params to the endpoint) from the embed config options (encoded as params on the
default_noteoptions back to
- Recognize Unicode document slugs (#37)
- Conform syntax to WordPress VIP plugin requirements (#30) (@bcampeau)
- Fixed: Bare URLs now get default parameters (#35)
- Fixed: Pages/notes on docs with uppercase slugs now embeddable (#36)
- Support embedding pages (#28)
- Support embedding raw contextual page/note URLs (#29)
- Check for existence of things to stop triggering PHP notices (#27)
- Add DocumentCloud logo for plugin (#26)
- Fix ability to specify a container in the shortcode
- Improve embeddable resource pattern recognition
- Remove unused TinyMCE components
- Resolve CVE-2015-2807 reported by dxw Security at https://security.dxw.com/advisories/publicly-exploitable-xss-in-wordpress-plugin-navis-documentcloud/
- Implement a few best practice security measures
- Check for old (Navis) plugin and warn admins of conflict
- Add note about raw URLs to README
- Stop storing shortcode attributes in the
- Add support for embedding notes.
- Default to responsive.
- Enable caching.
- Fetch embed code via oEmbed instead of generating statically.
- Add new options:
idattribute. It's still usable, but support may drop in the future. Use
- Initial release.
License and History
The DocumentCloud WordPress plugin is GPLv2. Initial development of this plugin by Chris Amico (@eyeseast) supported by NPR as part of the StateImpact project. Development continued by Justin Reese (@reefdog) at DocumentCloud.