Demo Content Import Fail
When i try to import the demo data on my HeartInternet hosted site i get the following error
WordPress function wp_remote_get() test failed. Looks like your server is not fully compatible with WordPress. Contact your hosting provider.
Error: Failure when receiving data from the peer
Never had this problem with Avada, X-Theme or Bridge ???
Any advice or way round this issue ?
Thanks
WordPress function wp_remote_get() test failed. Looks like your server is not fully compatible with WordPress. Contact your hosting provider.
Error: Failure when receiving data from the peer
Never had this problem with Avada, X-Theme or Bridge ???
Any advice or way round this issue ?
Thanks
Comments
you may not had this problem with other themes because they do not have so many pre-made layouts as we have so it's pointless to compare BeTheme to other themes. Also, please notice that wp_remote_get() is default WP function. This function uses loopbacks and this could be the reason why you are unable to import full demo. So or you will contact with your admin and ask him if he can remove those limits for you or you must import demo with errors and then import muffin options manually.
More details about similar issue you can read on http://forum.muffingroup.com/betheme/discussion/12103/wp-remote-get-demo-download-no-header-menu-of-footer-settings where a problem was a little bit different but the solution may work for you as well.
Thanks!
massivesolution.com [Mon Apr 11 12:52:29 2016] [error] [client 5.148.15.50:56120] AH01215: PHP Fatal error: Cannot use object of type WP_Error as array in /home/sites/massivesolution.com/public_html/cor/wp-content/themes/betheme/functions/importer/import.php on line 496: /home/sites/massivesolution.com/public_html/cor/wp-admin/themes.php
This is unfortunately not supported on shared hosting.
Our servers prevent scripts making HTTP (port 80) connections back to the same server that they're running on, as policy.
This is done to prevent the possibility that mis-configured scripts could enter, essentially, an "infinite loop", making call-backs to themselves. Such a situation is extremely detrimental to server performance, and would negatively impact other users also on this shared server.
Unfortunately we are not able to lift this block on a per-site or per-script basis, so you will need to see if you are able to reconfigure the script (or contact the script authors for assistance doing this), or use an alternative script that doesn't require HTTP requests to its own server.
It may be possible to add the below line to your wp-config file:
define('DISABLE_WP_CRON', true);
This may allow for this to work but I cannot confirm.
In reference to cron, in our opinion this won't change anything but you can try yourself of course if you want.