This is easier to view than it is to explain. I have a site that is built with Elementor. When I try to clone that site the new site is completely broken.
This is what the site should look like:
This is what the site looks like after a full clone
Here is the video showing the whole process.
Note, that's long, but if you want to skip past the cloning process then after 1:21 skip to 10:15 in the video.
I have a lot of questions about this, but that brings up one. That entire site is less than 20 MB - why does it take 9 minutes to clone a site that small?
You can see from the video that as soon as the cloning process starts there is an error. I don't know what its referring to. PHP log shows _many_ errors that happen during the cloning process. I can provide the debug.log file that demonstrates these if you can tell me how to share it privately.
Many of today's page builders store data as serialized or json string in the wp_options table when needed to render the page. According to some of the PHP errors it seems that the additional tables are not being found that would be necessary for the cloned site to render correctly. Example:
PHP Notice: Undefined variable: additional_tables in /var/www/html/wp-content/plugins/cloner/admin/cloner-admin-clone-site.php on line 429
[03-May-2018 22:33:56 UTC] WordPress database error Table 'toursoft.wp_16_options' doesn't exist for query SELECT option_value FROM wp_16_options WHERE option_name = 'db_version' LIMIT 1 made by require_once('wp-admin/network/admin.php'), require_once('wp-admin/admin.php'), do_action('load-index_page_clone_site'), WP_Hook->do_action, WP_Hook->apply_filters, WPMUDEV_Cloner_Admin_Clone_Site->sanitize_clone_form, WPMUDEV_Cloner_Admin_Clone_Site->pre_clone_actions, WPMUDEV_Cloner_Admin_Clone_Site->create_empty_blog, switch_to_blog, do_action('switch_blog'), WP_Hook->do_action, WP_Hook->apply_filters, WooCommerce->wpdb_table_fix, get_option
You have been granted admin access to the site to look around if necessary.
** note this is specifically about Elementor, but as I suggested in the title, we're having similar issues with other builders like Divi and Cornerstone who also use wp_options for json and serialized data stores.