wpazleen

Thank you for taking the time to share this detailed feedback and for the kind words about the plugin.

We really appreciate you documenting the issue and the workaround you used. Based on your description, it sounds like there may be edge cases around inline image size references and upload path handling during the image import process. We’ll dig into this on our end and try to reproduce the behavior. If we can confirm the issue, we’ll work on implementing a proper fix in a future update.

Feedback like this is incredibly valuable and helps us continue improving the plugin for everyone. Thanks again for bringing it to our attention, and we’re glad to hear the plugin has been working well for you overall.

Hi,

Thank you for reporting this.

We have manually reviewed the plugin codebase, performed extensive testing on our end, and also checked the plugin using WordPress’s official Plugin Check (PCP) tool. So far, we have not encountered any security issues, malware detections, or suspicious files that would explain the behavior you experienced.

Based on our review, we believe the SiteGround malware alert may have been a false positive. One possible cause is the use of the fread() function within the plugin’s file download handler, as some automated security scanners can occasionally flag legitimate file handling operations as suspicious. However, we have not found any actual malware or malicious code within the plugin.

The plugin is currently being used by many users for website migrations across a wide range of hosting providers and environments. This is the first report we have received of a malware-related detection, which makes us believe this is very likely a false positive. Nevertheless, we would like to review the exact details from SiteGround to fully understand what triggered the alert and ensure there are no compatibility issues with their scanner.

Would it be possible for you to contact SiteGround support and request the exact details of the detection? In particular, it would be very helpful if they could provide:

• The exact file name that was flagged.
• The malware/security signature or rule that triggered the detection.
• Any scan logs, screenshots, or error messages related to the issue.

You mentioned that the file name may have contained “handler”, which gives us a starting point, but we would need the complete details to properly investigate.

Thank you for bringing this to our attention, and we look forward to your update.

• This reply was modified 2 weeks, 4 days ago by wpazleen.
• This reply was modified 2 weeks, 4 days ago by wpazleen.

Thank you for the valuable suggestion regarding JSON-based media import/export.

After reviewing the issues you mentioned, we’d like to clarify that media export already includes structured JSON metadata. When exporting media, the system generates a ZIP file that contains:

• All media files
• A media_metadata.json file with complete attachment data

So technically, JSON support is already part of the process.

If you’re working with a large website (thousands of posts/media files), you may experience timeouts during import or export. This is usually caused by server limitations – not the file format itself.

We’re have plan and actively working on introducing batch-based (chunked) export and import processing. This enhancement is designed specifically to support large websites with more than thousands of posts or heavy media libraries.

For now, you can update these limits in one of the following ways, depending on your hosting setup.

Immediate Workarounds You Can Try:

✅ Option 1: Contact Your Hosting Provider (Recommended)

This is the safest and most reliable method.

Send your hosting support team this message:

Please increase my PHP limits to the following values:

max_execution_time = 600
max_input_time = 600
memory_limit = 512M
upload_max_filesize = 500M
post_max_size = 500M

Most hosting providers can apply this within minutes.

✅ Option 2: Update .htaccess (Apache Servers Only)

If your server uses Apache, you can try adding this to your .htaccess file:

1. Open public_html
2. Edit .htaccess
3. Add:

php_value max_execution_time 600
php_value max_input_time 600
php_value memory_limit 512M
php_value upload_max_filesize 500M
php_value post_max_size 500M

✅ Option 3: Update wp-config.php (Memory Only)

You can increase memory via WordPress:

1. Open wp-config.php
2. Add above the line:
   /* That's all, stop editing! */

define('WP_MEMORY_LIMIT', '512M');
define('WP_MAX_MEMORY_LIMIT', '512M');

Important: This only affects memory limit. It does NOT change execution time or upload size.

🔍 How to Verify Changes. Use the Built-in System Test (Before Changing Anything). You can find it directly below the Post & Media Import/Export section.

This tool automatically checks your server configuration and shows whether your environment is suitable for large import/export operations.