Hendridev

HDEV Import / Export Post lets you move posts between WordPress sites without losing their images. Export a post type to a single portable JSON file, then import that file on a local server or another production site.
During import, every featured image, in-content image and post attachment is downloaded from the source site into the destination site’s own media library, and the image URLs inside the post content are rewritten to point at the newly downloaded copies. Nothing keeps pointing back at the old site.
Re-importing the same file is safe: existing posts are updated in place instead of duplicated, and media that was already downloaded is reused instead of downloaded again.
Both export and import run in small batches with a live progress bar, so large jobs do not time out and you always see what is happening.
Export features:
<ul>
<li>Export any public post type (Posts, Pages and custom post types)</li>
<li>Filter by post status (published, draft, pending, private, scheduled or all)</li>
<li>Filter by date range — the month list is detected automatically from the existing content of the selected post type and refreshes when you switch post types</li>
<li>Filter by author — the dropdown lists only users who have actually authored content on the site</li>
<li>Optionally include the media attached to each post</li>
<li>Single portable JSON file — easy to move between sites</li>
<li>Live progress bar while the export runs, then the file downloads automatically</li>
</ul>
Import features:
<ul>
<li>Featured images, in-content images and post attachments are downloaded into the destination site’s media library</li>
<li>In-content image URLs are automatically rewritten to the new local URLs</li>
<li>Update existing posts instead of creating duplicates — posts are matched by slug and post type, so the same file can be imported again safely</li>
<li>Already-downloaded media is detected and reused, so re-imports never fill the media library with copies</li>
<li>Works between local development sites (Local, <code>.local</code> / <code>.test</code> domains) as well as production domains</li>
<li>Taxonomy terms (categories, tags and custom taxonomies) and post meta are preserved</li>
<li>Missing categories are created automatically, including the full parent/child hierarchy</li>
<li>Assign every imported post to a user of your choice, or keep the original author when a matching username exists</li>
<li>Optional: import all posts as drafts</li>
<li>Live progress bar with a per-post log — successful posts, reused/downloaded media counts, and clear warnings when a media download fails</li>
</ul>
General:
<ul>
<li>No new database tables — uses the standard WordPress APIs</li>
<li>Admin-only: every action requires the <code>manage_options</code> capability and is protected by nonces</li>
</ul>

HDEV Import / Export Post

Export posts to a JSON file and import them elsewhere, downloading featured images, content images and attachments to the destination site.

Steveorevo

ServerPress

SpectrOMTech

Dave Jesch

Since version 4.2, WordPress has been detecting the MySQL version and if it’s version 5.5.3 or greater, automatically selecting the ‘utf8mb4_unicode_520_ci’ Collation Algorithm. This works well until you need to migrate your database to an older version of MySQL that does not support the utf8mb4 algorithms. Then, you run into the error message: “#1273 – Unknown collation: ‘utf8mb4_unicode_520_ci'” when importing your database.
With the WordPress 5.7 update and WooCommerce 5.1, some users are reporting an error: “SQLSTATE[HY000]: General error: 1267 Illegal mix of collations (utf8mb4_unicode_520_ci,IMPLICIT) and (utf8mb4_unicode_ci,IMPLICIT)”. The Database Collation Fix tool also fixes this issue by changing the collation of all columns in your database to use the same algorithm, removing the “mix” of collations.
Usage Scenarios:
While the plugin will work in any WordPress install: local, staging or live, it is specially designed to work with DesktopServer. Its process will be triggered and change the collation types on all database tables during any DesktopServer Create Site, Copy Site, Move Site, Import and Export operations. This allows you to import and export sites in the most compatible ways during deployments. If you would like to use this with DesktopServer as a Design Time plugin, you can install this in your /xampplite/ds-plugins/ directory and it can then be automatically activated and used with all of your local development web sites.
Alternatively, you can install this as a regular WordPress plugin on any site. Once activated, all of your database tables will be updated to use the more portable Collation Algorithm. If you are migrating your web site, you can install and activate the plugin then perform your database export. Once you have migrated your site, you can deactivate and remove the plugin as it would be no longer needed. If you will be exporting and/or migrating your site repeatedly, such as when using it on a test or staging install, you can leave the plugin active indefinitely and it will continue to monitor and update your database tables automatically, allowing you to perform migrations at any time. This is ideal in situations where you are installing or testing plugins that may create their own database tables, as these tables may be created with the newer Collation Algorithms that are not as portable.
How it Works:
The Database Collation Fix tool converts database tables using ‘utf8mb4_unicode_520_ci’ or ‘utf8_unicode_520_ci’ Collation Algorithms to a more portable ‘utf8mb4_unicode_ci’ collation on a once daily basis. It also modifies any column-specific collation statements, not just the default table collation. This means that you can install this plugin and it will continue to monitor all of your database tables and convert them to the more portable Collation Algorithm automatically.
This tool will convert your database tables and columns to use the ‘utf8mb4_unicode_ci’ Collation Algorithm. This can be modified to any other Collation Algorithm you wish by updating your <code>wp-config.php</code> file and adding or changing the following setting:
<blockquote>
<code>define('DB_COLLATE', 'utf8_general_ci');</code>
</blockquote>
You can use ‘utf8_general_ci’ or ‘utf8’ or any other Collation Algorithm supported by your database. See <a href="https://dev.mysql.com/doc/refman/5.7/en/charset-mysql.html" rel="nofollow ugc">https://dev.mysql.com/doc/refman/5.7/en/charset-mysql.html</a> for a full description of MySQL’s Character Set and Collation Algorithm selections.
Support:
<blockquote>
Support Details: We are happy to provide support and help troubleshoot issues. Visit our Contact page at <a href="http://davejesch.com/contact/" rel="nofollow ugc">http://davejesch.com/contact/</a> or submit a support request on the WordPress plugin page.
</blockquote>
We are not responsible for any loss of data that may occur as a result of using this tool. We strongly recommend performing a site and database backup before testing and using this tool. However, should you experience such an issue, we want to know about it right away.

Database Collation Fix


This plugin helped me to convert a database with a wild mix of collations to utf8mb4_unicode_ci.



Thanks!


Great plugin

Convert tables using utf8mb4_unicode_520_ci or utf8_unicode_520_ci collation to a more portable Collation Algorithm.

HDEV Import / Export Post vs Database Collation Fix