I have updated WP to 6.5 and strangely enough I can no longer call up or customise the template in the backend that I created in the block editor with Toolset.
In other words, I can see the page in the frontend, i.e. the search form created with Toolset and the grid created below it. In the backend, however, I only see a white page when I want to edit it in the Gutenberg Editor. How can that be?
Can I share sensitive data here, then someone from support could look at it themselves in the backend?
We didn't come across this in our testing of WordPress 6.5, we'll need to check your site. A staging server would be preferable, and it may be the case that we need to copy your site for more thorough testing if we cannot determine the problem on your server.
Let me mark your next reply as private so that we can get log-in credentials from you—you may want to create a temporary admin user for us to use that you can later delete. And be sure to have a current backup of your site.
Can you also confirm the template we should check?
Thanks for that. I logged in to the site and I can see that there are JS errors in the console when trying to load those pages.
I spent some time looking into possible causes and I have isolated the problem and reproduced it.
Specifically, the template and page you are having problems with both contain a core Image block that uses Toolset dynamic sources to display the featured image.
I've escalated this to the developers, who can hopefully identify the root cause and propose a solution before too long.
If you need to be able to edit the template or page in the meantime, there is no alternative but to downgrade WordPress to a previous version (e.g. 6.4.3). You could, then, edit the template and page and replace the core Image block with a Toolset Image block. Were you to do so it should then be possible to upgrade to WP 6.5.
In any case, I'll let you know when we have a solution available.
I have now downgraded back to WP 6.4.3 as I have a presentation next week. So everything works again. It really seems to be due to WP 6.5. that there is a conflict. Do you have any news about this?
I'm speaking with the developers each morning, and this remains their main focus. It is proving a tricky problem to fix (the solution can't break sites that haven't upgraded to WordPress 6.5).
As soon as there is a fix available I'll let you know.
The developers have a solution and are preparing an update. It sometimes takes a little while for the update to be available, our systems team need to facilitate the release and the documentation team need to document it.
But I intend to make a version available directly to those clients who are currently affected. I should have that available either at the end of the day, or early tomorrow, so I will be in touch again soon.
Hi, I've had too much other web development work and won't be able to test whether the update works until next week. I'll definitely get back to you when I know!
