Troubleshooting Plumbit demo imports

Troubleshoot a Plumbit demo import by identifying the first failed layer. Separate importer progress from WordPress, plugin, hosting, media, and remote-source problems before retrying.

Record the first failure#

Record the selected demo, step, visible message, URL, time, and browser state.
Check whether the importer reported completion or stopped part way through.
Note whether the problem affects content, media, widgets, Customizer settings, menu assignments, or the frontend.
Collect only a short redacted log excerpt when support needs evidence.

Do not send passwords, tokens, license keys, payment data, complete logs, database exports, or full backups.

Common failure patterns#

The import times out or stalls

Check the server memory, upload, execution-time, and request limits. Identify the first failed request or importer stage before deciding whether a controlled retry is appropriate.

Imported media is missing

A completed Plumbit demo import normally adds demo media to the WordPress Media Library, while some imported layout images may continue to load from external Stronghold-hosted URLs. If expected Media Library items are absent, first confirm the importer completed without an error, then check the first failed importer, network, or server request before retrying. Do not repeatedly run the importer on the same populated site; restore a clean pre-import state before a controlled retry.

A visible frontend image is missing

Identify whether the image is a local Media Library attachment, an external Stronghold-hosted URL, an empty Elementor image field, or a stale cached URL. Diagnose the source before changing theme settings. Confirm the first failed request and its response, and do not assume a missing image is a theme defect.

Menus or assignments are incomplete

Review the imported pages, menu records, theme locations, homepage, posts page, widgets, and relevant settings. An incomplete assignment can be separate from a successful content import.

The second import created duplicates

Stop repeated imports. Use a clean installation or restore a verified pre-import backup instead of deleting content or database tables. Another import can add more media and content, so review both local Media Library assets and externally referenced layout images before retrying.

Use focused recovery steps#

Confirm the source content and importer state.
Check the owning plugin or WordPress layer.
Clear only the relevant cache after the source and asset requests are correct.
Refresh rewrite rules only when valid imported routes return rewrite-related 404 errors.
Use Elementor's own tool only when Elementor-generated styling is stale.
Escalate with a short redacted evidence set when the first failed layer remains reproducible.

Do not manually delete Elementor-generated CSS, delete .htaccess, or run direct SQL cleanup as a routine import fix.

Expected result#

The failed layer, selected demo, import stage, and evidence are clear. The next action is a controlled repair, verified restore, or support escalation rather than a blind repeated import.

Related guidance#

Review How to import a Plumbit demo or Getting support.

Record the first failure#

Common failure patterns#

Use focused recovery steps#

Expected result#

Related guidance#

Related articles

How to import a Plumbit demo

Troubleshooting common Plumbit installation issues

Understanding the Plumbit download package

Plumbit system requirements and recommended hosting settings