WordPress Hosting Error Codes and Fixes in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

Sparkforge WordPress Hosting surfaces three import-related errors: File Corrupted, Plugin Issue, and Unknown Error (both). Delete the offending file or plugin and retry the import.

Sparkforge WordPress Hosting reports three errors that are unique to the platform. Each one is tied to the import process and resolves with the same pattern: remove the corrupted asset and retry.

File Corrupted

The import file is unusable. Corruption can occur in either the current WordPress installation or the source installation that exported it.

Fix: Delete the file from the installation and run the import again with a fresh export.

Plugin Issue

A specific plugin is corrupted. The error message names it directly — for example: Plugin named "yith-topbar-countdown" is corrupted.

The fault may be in the destination WordPress install or in the source install that produced the export.

Fix: Delete the named plugin and retry the import.

Unknown Error (file and plugin both corrupted)

When both a file and a plugin are corrupted, Sparkforge surfaces the plugin error first. Resolve the plugin error, then retry.

If the file is also corrupted, the error message will change to the File Corrupted message after the plugin fix. Delete the file and retry to complete the import.

Frequently Asked Questions

What causes File Corrupted on WordPress import?
The export archive is unreadable. It can come from the source WordPress install (export-time corruption) or from the destination install if the upload was interrupted.
Do I need to delete the plugin everywhere?
Delete it from whichever WordPress install is reporting the error. If the source export is the issue, regenerate the export after removing the plugin from the source.
Why do I only see one error at a time when both are corrupted?
Sparkforge surfaces the plugin error first. Resolving it lets the file error appear so you can fix that next.
Can Sparkforge auto-repair corrupted plugins?
No. Corrupted plugins must be deleted manually because automatic repair could leave inconsistent data behind.

Was this article helpful?