One Click Demo Import plugin review and common issues

XML import failures are typically resource limit issues. Increase these PHP settings via your hosting control panel or php.ini: max_execution_time = 300, memory_limit = 256M, upload_max_filesize = 64M, post_max_size = 64M. After adjusting limits, clear all caches and retry. If the import still fails at a specific post or media item, the demo XML may reference an external image that cannot be downloaded — try the import without media (most theme demos have an option to skip media import).

Incomplete demo appearance after import usually means: (1) the homepage needs to be set — go to Settings → Reading and set “A static page” with the imported homepage as “Homepage”; (2) Customizer settings may not have imported — go to Appearance → Customize and manually configure colors, fonts, and layout; (3) custom sliders (Revolution Slider, Smart Slider 3) are not included in the demo XML — import them separately following the theme documentation; (4) required plugins may not be active — install and activate all required and recommended plugins before re-importing.

The Import Demo Data menu item appears only when: (1) One Click Demo Import plugin is active AND (2) the active theme has registered demo import files using the plugin’s hook. If the menu is missing, check that your theme requires and properly uses One Click Demo Import — not all themes use it. If your theme documentation says to look for “Import Demo Data” but it is missing, verify the plugin is active and try deactivating and reactivating both the plugin and the theme.

After purchasing a ThemeForest theme and installing it on WordPress: (1) install all required plugins listed in the theme’s setup documentation (typically including One Click Demo Import and any premium plugins bundled with the theme); (2) go to Appearance → Import Demo Data; (3) select the demo variation that matches your desired site look; (4) click Import and wait for all steps to complete (content, widgets, Customizer); (5) after import, configure the homepage assignment in Settings → Reading, verify menus in Appearance → Menus, and add your own content to replace the demo content.

Install the plugin and use its filter to register your demo files. In your theme’s functions.php: add_filter(“pt-ocdi/import_files”, function() { return array(array(“import_file_name” => “Demo 1”, “local_import_file” => get_template_directory() . “/demo-content/demo.xml”, “local_import_widget_file” => get_template_directory() . “/demo-content/widgets.json”, “local_import_customizer_file” => get_template_directory() . “/demo-content/customizer.dat”, “import_preview_image_url” => get_template_directory_uri() . “/demo-content/preview.jpg”,)); }); Include your demo XML, widgets.json, and customizer.dat files in the theme package.

No — they serve different purposes. One Click Demo Import is a developer tool that theme authors use to provide demo import functionality in their themes. Starter Templates is an end-user tool with a built-in library of 200+ complete website designs. If your theme came with One Click Demo Import as a recommended plugin, you use it via Appearance → Import Demo Data to import that specific theme’s demo. If you want to browse a library of website designs independently of your theme purchase, Starter Templates is the appropriate tool.

Yes — multiple demo imports can be performed, but each import adds content on top of the existing content (it does not reset the site first). For best results, use One Click Demo Import on a fresh WordPress installation or immediately after installing a new theme before adding custom content. Using it multiple times on an existing site with content can result in duplicate posts, pages, and menus. A “reset WordPress” plugin (like WP Reset) can restore a clean state before attempting a different demo import.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.