Hi,
Something must have changed if it worked previously and now it does not. Please send us an email at contact@tagdiv.com and provide admin login, also FTP and cPanel if possible.
Mention in what circumstances this issue happens. Include a link to this topic in the email.
Thanks
I believe our developer team identified some possible causes for this to happen, these will be tested along some other fixes.
I can’t provide an update release date unfortunately, they are working to try and fix it as fast as possible.
The Cloud library plugin is still in beta, so issues with it may be expected. We are sorry for the inconvenience.
Hi,
That issue does still appear for some users, however very few. In 8.8.1 and 8.8.2 there were improvements made for the Cloud library plugin. These fixed the issue for most users as far as we know. But still it seems to happen for some. We are sorry for the inconvenience. The plugin is still in development (beta) and will be improved more for a better stability in the future.
In some cases even plugins caused that error to appear. You could try and find out if that is the case for you. Sorry again.
Thanks
Deactivated all plugins except of Tagdiv’s
Invalid reply from server endpoint Error is Still There
Even Reinstalled WordPress itself with brand new copy of Newspaper9
Invalid reply from server endpoint Error is Still There
Now Switching back to Using Visual composer Permanently…
Overall my experience with TagDiv Composer etc was Very frustrating.
Why did you people built TagDiv Composer in the first place, what value does this adds to a theme that was running well enough on Visual composer.
Hi,
Sorry to hear that, there would always be some exceptions no matter how much we try. We will keep improving the plugin however.
That would be the case in general if you think about it. Take another plugin for example, the same plugin will probably not work for all the users who install it. That can be caused by many factors.
The tagDiv composer is built by us from scratch. The question would be why not? Why not provide a page builder of our own, add functionality for it which would not be possible with WPBakery as a base.
What would happen if for some reason WPBakery page builder is not updated anymore or maybe discontinued? Now there is an alternative.
Users are free to choose which page builder they will use, we recommend the tagDiv composer.
Thanks
My Point is…
You should also make 2 versions of demos,
One version based on TdComposer and
Second version based on WpBakery Pagebuilder
That way..when one faces errors using TDComposer their work wont suffer as they will have Visual composer to fall back upon.
If that makes sense…
That is all I want to say…
Hi,
@BlogMickey and @Cavaldini It could be caused by insufficient or incorrectly configured system status
– https://forum.tagdiv.com/requirements-for-newspaper/
Could also be caused by a security plugin if you use one or a server firewall, there were some cases. Maybe try and check that as well.