[Resolved] Conflict after updates where blocks are not editable

[Author]

Posts

[itaiP]

Check the production Site. The Block plugin is not updated and showing the images correctly.

You can check the difference for both at hidden link (Production) , hidden link

[Waqar]

Hi,

Thank you for sharing your findings and I'll be resuming on this ticket.

During troubleshooting, I noticed that the staging website ( hidden link ) is having difficulty in connecting to the REST API in general, which is also needed for features like the Blocks/Gutenberg editor for views and content templates.

If you'll go to WP Admin -> Tools -> Site Health, you'll see this critical issue along with the others.
( screenshot: hidden link )

"The REST API request failed due to an error.
Error: cURL error 28: Operation timed out after 10002 milliseconds with 0 bytes received (http_request_failed)"

All the 3 critical issues shown in there, point out to the website's server configuration and you'll find some useful information about its fix from this guide:
hidden link
( you can also consult your web host to investigate these points for you )

Important note: During the course of this investigation, I'll strongly recommend disabling Cloudflare from the website, so that it is easier to narrow down at which point the REST API connection is failing. Once everything is updated and working normally, you can connect Cloudflare again.

Once the main issue of Views and Content template editing has been fixed, we can move to the investigation of the missing featured images on the homepage.

regards,
Waqar

[itaiP]

Hi,
Thankyou for letting me. I'm looking into this. Meanwhile can you send me which php modules is required by toolset and which is not ?

[itaiP]

I have fixed the issues. Still the images are not loading on frontend for few content blocks.

[itaiP]

I want you to switch between Toolset Block 1.1.3 and Toolset Block Version 1.3.1 and check the homepage of the site different with both the plugins.

You will better understand.

[itaiP]

Here I have put both the version on the staging site.

[Waqar]

Hi,

Thank you for waiting.

> Meanwhile can you send me which php modules is required by toolset and which is not ?
- You'll find the Toolset server requirements at https://toolset.com/toolset-requirements/

> I want you to switch between Toolset Block 1.1.3 and Toolset Block Version 1.3.1 and check the homepage of the site different with both the plugins.
- While, I can see the issue with the featured images on your staging website, I couldn't reproduce this with the same settings, blocks, views, and content template on my test website.

This suggests that there is something specific to this website involved.

For the course of this troubleshooting on this staging website, can you please disable all plugins other than the Toolset ones and switch to a default theme like Twenty Twenty?

And as requested earlier, it would also be a good idea to disable Cloudflare. I'll also need your permission to download a fresh clone/snapshot of the website if needed.
( ref: https://toolset.com/faq/provide-supporters-copy-site/ )

regards,
Waqar

[itaiP]

In the previous conversation I have disabled and tested each and every thing you have mentioned. With 2020 also the issue is same.

If you're unable to fix your plugin issue let me know. It's wasting our time too. Till version 1.1.3 everything is working fine and one update suddenly breaking the whole site.

Do let me know if you can fix this. If not, say it.

[itaiP]

Also, I have already sent the clone & database of the site.
Do check in previous thread.

[Waqar]

Hi,

I've managed to successfully deploy your staging website's clone on my test server.

I'll be performing some further tests to investigate this issue deeper and will share my findings as soon as this testing completes.

Thank you for your patience.

regards,
Waqar

[Waqar]

Hi,

Thank you for waiting.

Just wanted to update that I've shared the cleaned down version of your website's clone ( where the issue can be seen with only Toolset plugins and the Twenty Twenty theme ), with the concerned team for further investigation.

I'll keep you updated on this ticket and I'll hear back from them.

regards,
Waqar

[itaiP]

Hi, Do you have any update regarding the fix? It's really being impossible to edit on site with that issue.

[Waqar]

Hi,

Thank you for waiting and I've heard back from the development team, regarding this complex issue.

A shorter explanation is that this may be affected by an issue identified for the Toolset Blocks 1.3:
https://toolset.com/errata/featured-image-as-dynamic-source-in-output-of-a-view-missing-on-front-end-if-not-first-view-on-the-page/

This is expected to be fixed in the next major update for Blocks (not the minor hotfix just released). I'll update you on this ticket once it is released and this particular issue should resolve on its own.

But there is a broader issue, which is the way the website has been constructed, which makes excessive use of a hierarchy of templates and nested Views that is inefficient and raises the likelihood of something going wrong.

We see no good reason why a content template should be created with all of the content for the home page and then assign it to the home page, rather than simply adding the content directly to the home page, for example.

And likewise, the nesting of Views via content templates is not only cumbersome, but unnecessary.

The template for the home page includes a View “Home v2 Latest Post” which queries the “Domains – Blog Posts” intermediary post type. This is used to output a featured image from the related “Blog Post” post, and a custom image field from the related “Domain” post.

The correct way to do that is to insert Image Blocks directly into the output of the View, and in Dynamic Sources specify that the source for the featured image is the Related: Blog Post and the source for the custom image field is the Related: Domain post.

But how it is done instead is, that a View has been inserted to query related Blog Posts and it outputs the featured image, and a view has been inserted to query related Domain posts and it outputs the custom image field. And, in both cases, the views haven't been inserted directly, but have been inserted through Content Templates. We assume it was done to bypass the limitation that nested Views are not supported, but in this case they are entirely unnecessary. The Dynamic Sources option could have been set to use the related posts as a source, and that's it.

But! One final point, which may explain why you have gone to these lengths. For some reason on this site the Dynamic Source for featured images isn’t working correctly and you cannot choose featured image as a source of the Image Block when the origin post is set to be the Blog Posts post, while it should be. To bypass that, you'll need to go to Toolset > Post Types to edit the intermediate post type and enable featured image support for it, then it should all work.

So summing this up, you can wait and see if the next update fixes the problem or, even better can update the site's structure to eliminate the unnecessary nested Views and Content Templates as described above.

regards,
Waqar

[itaiP]

Can you make this ticket open till the next plugin open. Thanks

[Waqar]

Hi,

I'd like to update that the issue involving the Image Block's output for the featured image has been fixed in the Toolset Blocks 1.3.3.
( ref: https://toolset.com/errata/featured-image-as-dynamic-source-in-output-of-a-view-missing-on-front-end-if-not-first-view-on-the-page/ )

regards,
Waqar