Hi,
I am having some problems with accessing cloud templates. After few seconds it shows red error ‘Failed to contact the templates API server’.
Theme is activated and licensed properly.
Weird thing is:
– on the same hosting server I have another domain without activated theme just for testing purposes and there cloud templates are opening fine
What could be the issue here?
Best regards!
Hello,
First, make sure you have added the limit also in your wp-config.php file, in config is WP_MEMORY_LIMIT not PHP Memory Limit (there is a typo, sorry) check this: https://www.screencast.com/t/88pK5QXpC –> https://forum.tagdiv.com/requirements-for-newspaper/
Also, make sure that you do not have a plugin conflict with untested plugins, please deactivate all non-theme/tested plugins, also if you are using a child theme, clear all cache and try again.
The footer templates do not have the button to be edited with tagDiv Composer in the backend. Please check this guide:https://forum.tagdiv.com/footer-templates/
The footer template can be edited only from the frontend if it is assigned, edit a page/post template with tagDiv Composer and go down to the footer. => https://www.screencast.com/t/rpfNhfyrF
Thank you!
For those who encounter this bug despite of a well configured theme and server, you can circumvent it by increasing the timeout of the get_all request sent by your server to the cloud API.
It does the trick for me to increase it from 12 seconds to 90 seconds. It seems that my hosting provider’s servers maybe busy some times and need more time to get responses from the API.
To increase this timeout, edit those files :
//file path 'www/wp-content/plugins/td-cloud-library/tdb_ajax.php'
//line 557
$api_response = wp_remote_post($api_url . '/' . $cloud_end_point, array (
'method' => 'POST',
'body' => $cloud_post,
'timeout' => 12 //INCREASE THIS
));
// file path 'www/wp-content/td-composer/tdb_ajax.php'
//line 210
$api_response = wp_remote_post($api_url . '/' . $cloud_end_point, array (
'method' => 'POST',
'body' => $cloud_post,
'timeout' => 12 //INCREASE THIS
));
For me, 90s is enough to make it works properly, even when my hosting provider’s connectivity is overloaded.