I am working on a new site and I have a new installation of Toolset on it.
I am seeing a problem when adding dynamic images in the block editor which I have never seen on my other installation.
I am trying to add a custom size to the image block so that all the images in the loop have the same dimensions but I am getting the following error: "Zero size image string passed". Please see attachment.
Do you know what this means and why it is happening?
Thanks for your fast reply. I had a look through the thread that you sent me.
I know the plugin in question but I don't have it installed on this WP installation.
1. I created a duplicate site and tried deactivating all plugins, except toolset plugins. This didn't work.
2. I'm using Astra with a custom child theme, so I switched to the Astra parent theme. This didn't work.
3. I switched to Twenty Twenty-Two. This didn't work.
4. I turned off all Toolset plugins except for the Block Editor and Types. This didn't work.
Not sure where to go from here. Any ideas?
Perhaps I need to point out that all of this is being done on staging sites, created through the Softaculous WordPress Manager. Could this be the issue?
In the template that you mentioned, I found an image block nested deep inside that is broken, because it is trying to get an image from seeming a non-existent field (author-profile-picture).
( screenshot: hidden link )
Can you please try removing that block and then test by adding a new image block?
I just clicked the attempt block recovery button and it recovers without a problem. But this doesn't fix the problem.
Bear in mind that this problem is happening on every content template / page. You can create a brand new page and add a Toolset Image block with a dynamic source and it won't let you resize it.
Your website is using the "HTTPS", but in the "WordPress Address (URL)" and "Site Address (URL)" fields, the address with "HTTP" is being used.
( at WP Admin -> Settings -> General )
Please update those fields to use "https" values and then check the image resizing again.
In case the issue persists, I'll need your permission to download a clone/snapshot of your website, to test this on a different server.
Thanks for the update and glad that it is sorted now.
I saw some errors and warnings in the browser's console, which led to that conclusion.
WordPress uses these fields for the based URL and when there is a change in the protocol (HTTPS or HTTP), the generated URLs are treated as external links or links from a different website/domain.