Archivarix External Images Importer vs Keyring Social Importers

Archivarix External Images Importer scans your posts and pages for external URLs in src/srcset attributes of all img tags. Based on configured settings, the plugin can: Download images from their original external sources Download images from Internet Archive (Wayback Machine) Try to download from original source first, then from Internet Archive if failed Try to download from Internet Archive first, then from original source if failed Restore missing local images (404) from Web Archive You can choose what to do with images that could not be downloaded: Keep image unchanged Remove image from post completely Replace with 1×1 pixel placeholder Key Features Full compatibility with WordPress 7.0 AI-ready: WordPress Abilities API / MCP integration (WordPress 7.0+) so AI agents can scan and import images Modern AJAX interface with real-time progress Background processing – you can close the browser while processing continues Detailed import statistics and logs with CSV export Custom filename patterns support Automatic restoration of missing local images srcset attribute support Custom post types support Invalid URL detection and handling Improved error handling and logging Responsive design for all devices Available in English, Russian (Русский), Spanish (Español), French (Français), Portuguese (Português), and German (Deutsch). For more information, visit the plugin documentation.

Please read about each importer before running this plugin. This package of social importers provide you with the ability to pull in your content that gets created on other sites, and re-publish it on your own WordPress site. Rather than leaving others in control of everything you’ve put time and effort into, why not host it yourself on your one true, home-on-the-web, WordPress? Read more about this technique/approach to data ownership. After an initial import, all of these importers can also optionally check each hour and automatically download new content as well, keeping things in sync over time. They all currently import as Posts, with specific Post Formats, depending on the content type. Importers included currently: Delicious Fitbit Flickr Foursquare/Swarm Instagram Instapaper Jetpack/WordPress.com Moves Nest Cameras Pinterest Pocket Strava TripIt Twitter You can potentially write your own importers as well, using the base class included. Importers Common Features If you select to ‘auto-import new content’, all importers will check once per hour for new content. All posts created by the importers are associated with a taxonomy called keyring_service, which allows you to filter/select them. Appears in wp-admin as “Imported From” under the Posts menu. Every attempt is made to download/store as much data as possible, and use it intelligently (e.g. tags). Raw import data is stored in a custom field (raw_import_data) as a json_encode()ed string. Delicious Every bookmark from your Delicious account is imported as a post. All imported posts are marked with the ‘link’ Post Format. delicious_id and the href/link itself are saved as custom fields. Tags used on Delicious are used in WordPress. Fitbit Very basic for now, just imports your data and creates a simple summary post. Summary post only contains a statement about how many steps you took that day. Flickr Every photo in your Flickr account is downloaded (the actual, original image) and imported into your Media Library. For every photo, a Post is created and published, containing that one image (and it is attached within WordPress). Posts are marked with the ‘image’ Post Format. Posts are created with the publish date matching the ‘Taken’ date of the photo. The modified date (of the Post) is set to the ‘Upload’ date from Flickr. There is no support/handling of Galleries, Sets or anything else in Flickr, just one Post per photo. Tags used on Flickr are used on WordPress. If available, geo data is downloaded and stored per the WordPress Geodata guidelines. flickr_id and the full URL to the photo page are stored as custom fields. Foursquare Imports each check-in on Foursquare as a separate Post. Marks those Posts with the ‘status’ Post Format. foursquare_id plus geo lat/long are stored as separate custom fields, per the WordPress Geodata guidelines. Instagram Each photo on your Instagram account is downloaded and imported into your Media Library. For every photo, a Post is created and published, containing that one image (and it is attached within WordPress). Posts are marked with the ‘image’ Post Format. The name of the filter used is stored as instagram_filter, the URL to the photo page is stored as instagram_url. Instapaper Imports your Archived links and creates a post for each of them (with post format of Link). Uses the title from the document in Instapaper, if there is a description associated then it uses that as well. NEW: Downloads the full content of the article using Instapaper’s API, and stores that in the post content, so that you can search it later. Disable it by creating a stub plugin, or dropping this in your theme’s functions.php; add_filter( ‘keyring_instapaper_download_article_texts’, ‘__return_false’ ); Jetpack/WordPress.com Import posts from either self-hosted, or hosted copies of WordPress, via the Jetpack/WordPress.com API. Post author is always overridden. Tags, content, title, excerpt are all carried over. Moves Imports your data daily. Creates a summary post, which is a bulleted list detailing each category of activity for the day. Stores raw and summary data for further processing. Nest (Camera) Allows you to pick hours of the day to take snapshots from your cameras. You can pick anything between no snapshots, or one every hour, per camera. Each snapshot will be downloaded directly into your Media Library. Each snapshot will also be published as a Post (with post type of “image”) using the Author/Category/Tag options you select. If you click the “Check For New Content Now” button, when configured for auto-import, then all cameras with at least one scheduled snapshot will take one right now, regardless of what time they’re scheduled (good for verifying that things work, or taking a specific snapshot for whatever reason). Does not require a Nest Aware subscription, since the relatively infrequent snapshots are under request limits. Pinterest NEW: This is a new addition, and is pretty rough still. Not recommended for production sites. Imports every individual pin as a post (can be a LOT), with a Post Format of “image”. Stores the image for each pin in your Media Library. Pocket Imports links and creates a post for each of them, with the Link post format. Uses as many details (e.g. title) as possible from Pocket. Strava Activities are imported as new Posts. * Activity type is stored as post meta for easier querying. GPS data is stored as an encoded polyline if available. [https://github.com/emcconville/google-map-polyline-encoding-tool](Google Maps Polyline Encoding Tool) has been tested to work well with the data. Stores raw and summary data for further processing. Currently does NOT download any media or support People & Places. TripIt Trips are imported, with flights mapped and posted as Status-format posts. Geo data is stored using something resembling the WordPress Geodata guidelines. Posts are tagged using airport codes and city names. Now supports paging through the API to avoid timeouts on accounts with lots of trip data. Twitter Every tweet will be downloaded as an individual Post. Posts are marked with the ‘aside’ Post Format. If available, geo data is downloaded and stored per the WordPress Geodata guidelines. Twitter_id and twitter_permalink are stored. If your tweet contains #hashtags, they are applied as tags within WordPress. “Entities” are expanded (URLs are not t.co, they are the real/final URLs).