Common issues and solutions for the current FE CSV Import & Export implementation.
- Enable
WP_DEBUGandWP_DEBUG_LOG - Check the browser console for JavaScript errors
- Test with a small CSV first
- Confirm your CSV headers match the expected format
- Confirm you are using Tools → FE CSV Import & Export
Check the following:
- The CSV includes an
IDcolumn - The first row contains headers
- The file is a valid CSV
- The selected post type is correct
- Nonce or capability checks are not being blocked by custom code
If you are creating new posts:
- Keep the
IDcolumn present - Leave the
IDvalue empty for new rows - Do not use dummy numeric IDs for new posts
For updates:
- Use a real existing WordPress post ID
- Enable the update-existing option in the import UI
- Confirm the selected post type matches the existing post
Check the following:
- Custom field headers start with
cf_ - Multi-value custom fields use
| - CSV values are quoted correctly when they contain commas
Check the following:
- Hierarchical taxonomy values use
> - Multiple taxonomy values use
| - The taxonomy exists for the selected post type
Check the following:
- Admin JavaScript loaded correctly
- Browser console has no fatal errors
- AJAX requests are completing successfully (check browser developer tools > Network tab > admin-ajax.php for errors)
- Do not navigate away from the page before export/import processing completes
FE CSV Import & Export already uses automatic batch processing.
If processing is still slow:
- Test with a smaller dataset first
- Check server memory and execution limits (PHP's max_execution_time and memory_limit)
- Reduce the export limit if you only need a subset
- Use dry run to validate import files before full processing
Check the following:
- Save the CSV as UTF-8
- Confirm
mbstringis enabled - Confirm WordPress/database charset is
utf8mb4 - Confirm translation files are present if localized UI text is expected
Check the following:
- Both Free and Pro versions are installed (Free and Pro versions work together)
- FE CSV Import & Export Pro is installed/activated
- Pro version license authentication is complete (license keys can be obtained from the sales site's my account page)
Add to wp-config.php if needed:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );Useful checks:
wp core version
php -v
wp plugin status fe-csv-import-export
tail -f wp-content/debug.log | grep "FE CSV Import & Export"Include:
- WordPress version
- PHP version
- FE CSV Import & Export version
- Browser and version
- Exact error messages
- A small sample CSV when possible
- Whether the issue occurs on import, export, or both