Hello
I have an error of " Something went wrong from fetching content from selected source. with a message: The JSON response is invalid. "
Here's the errors I'm getting to be more specific.
As a further debug process, I have found that there's a error with the shortcode structure with the itself with is resulting error 404 for the toolset block design.
Regards,
Vaibhav S.,
Developer, The CCD
GET hidden link; 404
[tb-dynamic%20provider='__current_post'%20post='current'%20source='toolset_custom_field%7Cfield-group-for-domains'%20field='domain-image'%20force-string='first'%20]:1 GET hidden link; 404
api-fetch.min.js:2 GET hidden link 520
I @ api-fetch.min.js:2
(anonymous) @ api-fetch.min.js:2
(anonymous) @ api-fetch.min.js:2
tryCatch @ wp-polyfill.min.js:1
invoke @ wp-polyfill.min.js:1
t.<computed> @ wp-polyfill.min.js:1
n @ api-fetch.min.js:2
a @ api-fetch.min.js:2
(anonymous) @ api-fetch.min.js:2
(anonymous) @ api-fetch.min.js:2
(anonymous) @ api-fetch.min.js:2
(anonymous) @ api-fetch.min.js:2
G @ api-fetch.min.js:2
(anonymous) @ api-fetch.min.js:2
p @ api-fetch.min.js:2
(anonymous) @ api-fetch.min.js:2
G @ api-fetch.min.js:2
(anonymous) @ api-fetch.min.js:2
(anonymous) @ api-fetch.min.js:2
p @ api-fetch.min.js:2
(anonymous) @ api-fetch.min.js:2
(anonymous) @ api-fetch.min.js:2
t @ api-fetch.min.js:2
(anonymous) @ api-fetch.min.js:2
C @ api-fetch.min.js:2
(anonymous) @ api-fetch.min.js:2
(anonymous) @ api-fetch.min.js:2
(anonymous) @ api-fetch.min.js:2
t @ api-fetch.min.js:2
(anonymous) @ api-fetch.min.js:2
t @ api-fetch.min.js:2
(anonymous) @ api-fetch.min.js:2
t @ api-fetch.min.js:2
(anonymous) @ api-fetch.min.js:2
(anonymous) @ wc-blocks-middleware.js:1
(anonymous) @ api-fetch.min.js:2
t @ api-fetch.min.js:2
(anonymous) @ api-fetch.min.js:2
t @ api-fetch.min.js:2
(anonymous) @ api-fetch.min.js:2
t @ api-fetch.min.js:2
(anonymous) @ api-fetch.min.js:2
eval @ api-fetch-redirect-middleware.js?5cfb:28
(anonymous) @ api-fetch.min.js:2
(anonymous) @ api-fetch.min.js:2
R @ api-fetch.min.js:2
(anonymous) @ index.js?ver=118000:1
tryCatch @ wp-polyfill.min.js:1
invoke @ wp-polyfill.min.js:1
t.<computed> @ wp-polyfill.min.js:1
p @ index.js?ver=118000:1
c @ index.js?ver=118000:1
(anonymous) @ index.js?ver=118000:1
(anonymous) @ index.js?ver=118000:1
(anonymous) @ index.js?ver=118000:1
(anonymous) @ index.js?ver=118000:1
tryCatch @ wp-polyfill.min.js:1
invoke @ wp-polyfill.min.js:1
t.<computed> @ wp-polyfill.min.js:1
rr @ index.js?ver=118000:1
c @ index.js?ver=118000:1
(anonymous) @ index.js?ver=118000:1
(anonymous) @ index.js?ver=118000:1
(anonymous) @ index.js?ver=118000:1
value @ index.js?ver=118000:1
(anonymous) @ hooks.min.js:2
(anonymous) @ index.js?ver=118000:1
e @ lodash.min.js:86
c @ lodash.min.js:87
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
u @ lodash.min.js:86
s @ lodash.min.js:87
(anonymous) @ index.js?ver=118000:1
(anonymous) @ hooks.min.js:2
(anonymous) @ index.js?ver=118000:1
(anonymous) @ hooks.min.js:2
(anonymous) @ view-editor.js?ver=3.3.2:1
Promise.then (async)
p @ view-editor.js?ver=3.3.2:1
(anonymous) @ view-editor.js?ver=3.3.2:1
setTimeout (async)
n.<computed> @ view-editor.js?ver=3.3.2:1
(anonymous) @ view-editor.js?ver=3.3.2:6
e @ lodash.min.js:86
c @ lodash.min.js:87
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
setTimeout (async)
Es @ lodash.min.js:115
f @ lodash.min.js:87
Show 40 more frames
[tb-dynamic%20provider='__current_post'%20post='current'%20source='media-featured-image-data'%20size='custom'%20width='300'%20height='300'%20crop='true'%20force-string='first'%20]:1 GET hidden link; 404
Hi,
Thank you for waiting, while I performed some troubleshooting and investigation around this.
Currently, "The JSON response is invalid" message is not showing on the homepage's content template edit screen, whether its your live website or your website's clone.
That error seems to appear, when there is a timeout error and the page's processing hasn't completed within the alloted time from the Cloudflare ( typically it is set to 100 seconds. ref: hidden link )
You'll find the steps to exclude the admin pages of WordPress from Cloudflare's features in the following guide. This should help in avoiding these timeout errors for the admin area pages:
hidden link
I hope this helps and please let me know how it goes.
regards,
Waqar
I have followed what you said. The instead of showing the error. Its crashing the whole server now.
Can we have a live session over which I can explain the issue.
Thanks for the update and I'm not seeing any website crashes on your website's clone on my server.
Are you seeing any new errors/warnings when the website crashes now?
I'm afraid, we can't have a live session, but if you haven't tried it already, it would be a good idea to test the website on a different server, to see if the crashes or timeouts are a result of the possible server contraints.
( if it helps and with your permission, I can upload your website's clone on my online test server, so that we both can work on it )
Sure,
You can upload the website on a test server. We can test this out together.
Thanks,
Vaibhav Singh
Developer, The CCD
Thank you for the confirmation
I'll get back to you with an online clone of the website, as soon as it is ready.
Thank you for waiting and I managed to deploy the clone on my server at:
hidden link
You can use the existing user account details to log in to the admin area.
Please let me know if you see any errors or crashes while editing the homepage's template.
If no issues are experienced here, it would mean that you'll need to work with your website's host to investigate the crashes and timeouts.
Hi,
I have tested the copy which you have updated over your server and the issue is remains the same. I'm still getting 404 Error on the toolset block short code. As far as I under stands the issue is that the toolset is directly requesting the images including the shortcode urls which is throwing 404 Error on the Frontend.
Rather than this the toolset should cover the shortcode into the actuall URLs of the Images and should get the URL instead of searching for the Shortcode URLs.
Also, this increases the server load and find the images until the images are found. Also, this is not instant the error comes after a while when we kept waiting for the images to load and to fetch the images properly.
I'm attaching the Screenshots for you to better understand this.
Regards,
Vaibhav Singh
Developer, The CCD.
Hi Vaibhav,
Thank you for the screenshots.
This ticket was started with a report of a different error, which is now no longer seems to be showing.
( Something went wrong from fetching content from a selected source. with a message: The JSON response is invalid )
I can see the 404 errors from the screenshots when editing the homepage's content template in the back-end, but not when visiting the front-end. It is the same for my locally hosted copy, my online copy ( hidden link ), and your actual website ( hidden link ).
And on the back-end, this is happening because of unnecessary nesting on content templates in the blocks editor, which is not supported.
Have you considered cleaning up this homepage content template from the unnecessary nested elements, as explained in my other reply?
( ref: https://toolset.com/forums/topic/conflict-after-updates-where-blocks-are-not-editable/page/2/#post-1818503 )
When the same page's content is passed through multiple nested content templates, it is processed again and again and changes its original form. It may work on the front-end, but the back-end preview area is not able to process it correctly.
For cases, where the nesting of views and content templates is absolutely required, you'll need to design your content template using the classic/legacy editor and not the blocks editor.
regards,
Waqar
