I hired some developers to work on my WordPress site that has a Staging site. I have only used Toolset Views and the WordPress classic legacy editor, but to redesign my Home page, they decided to use the blocks editor. Everything was working fine but there are some issues now. FYI, Staging is still using WordPress 6.0.2 and the production site is using 6.1.1. We plan on updating Staging but are seeing some differences and want to verify those first.
1. Staging: The home page is displaying an error now after a long delay. Warning: exif_imagetype(): stream does not support seeking in /home/customer/www/staging2.txwinelover.com/public_html/wp-includes/functions.php on line 3265
The developer says if all the Toolset plugins are deactivated, that error will not appear. This appears to be part of the WordPress core functions.php.
2. Staging: Plugins page has the Toolset message: "Toolset plugin cannot connect to toolset.com". The Installer Support page in admin says hidden link response is "Site key not matching". I removed the site key and added a new one so it is set correctly. Not sure if this is affecting anything.
3. Production: When editing the Home page in admin, the error "This block has encountered an error and cannot be previewed." is displayed. From the developer: "The 'Fields and Text' field option is supported in staging, but in the live site not working. The "Fields and Text" field option I used multiple times." I saw https://toolset.com/errata/fields-and-text-block-broken-with-wordpress-6-1-update/ and it stated the new version of Toolset Blocks 1.6.4 fixes that. That would explain why the production site using WordPress 6.1.1 is failing and Staging with WP 6.0.2 is not showing it. I asked the developer to install the new Toolset Blocks 1.6.5 on Staging. It turns out Toolset Blocks was never installed and only Toolset Views was. That makes me wonder how the site was using Fields and Text if Toolset Blocks was not installed. He could not install both Toolset Blocks and Toolset Views since a message comes up that only one can be installed. Does Toolset Blocks include all the functionality of the legacy Toolset Views? Is that the fix for this issue?
Hello. Thank you for contacting the Toolset support.
1. Staging: The home page is displaying an error now after a long delay. Warning: exif_imagetype(): stream does not support seeking in /home/customer/www/staging2.txwinelover.com/public_html/wp-includes/functions.php on line 3265
The developer says if all the Toolset plugins are deactivated, that error will not appear. This appears to be part of the WordPress core functions.php.
==>
I'm not sure from where the origin of the issue. We will have to check further.
2. Staging: Plugins page has the Toolset message: "Toolset plugin cannot connect to toolset.com". The Installer Support page in admin says hidden link response is "Site key not matching". I removed the site key and added a new one so it is set correctly. Not sure if this is affecting anything.
==>
Could you please try again and check again.
3. Production: When editing the Home page in admin, the error "This block has encountered an error and cannot be previewed." is displayed. From the developer: "The 'Fields and Text' field option is supported in staging, but in the live site not working. The "Fields and Text" field option I used multiple times." I saw https://toolset.com/errata/fields-and-text-block-broken-with-wordpress-6-1-update/ and it stated the new version of Toolset Blocks 1.6.4 fixes that. That would explain why the production site using WordPress 6.1.1 is failing and Staging with WP 6.0.2 is not showing it. I asked the developer to install the new Toolset Blocks 1.6.5 on Staging. It turns out Toolset Blocks was never installed and only Toolset Views was. That makes me wonder how the site was using Fields and Text if Toolset Blocks was not installed. He could not install both Toolset Blocks and Toolset Views since a message comes up that only one can be installed. Does Toolset Blocks include all the functionality of the legacy Toolset Views? Is that the fix for this issue?
===>
Toolset Blocks and Toolset views are 1:1 copy of each other. That should help you to resolve your issue. But before doing anything on production site I would suggest you to check on staging site and once you see everything working there then you should update it on production site so in any case you will not broke the production site.
3. This is difficult to test since the problem is on production, not staging. I enabled Toolset Blocks and deactivated Toolset Views. It appears to work fine. I will have the developer see it from his end. If everything looks good, we'll try it on production.
2. This is now fixed. What did you do?
==>
I did nothing. Sometimes it could take few seconds/minutes to align everything in order.
3. This is difficult to test since the problem is on production, not staging. I enabled Toolset Blocks and deactivated Toolset Views. It appears to work fine. I will have the developer see it from his end. If everything looks good, we'll try it on production.
==>
Ok fine.
#3. The developer installed Toolset Blocks on production and deactivated Toolset Views. Everything is working fine now. I was able to update the Home page now that had the Fields and Text block.
I still see this message "This block contains unexpected or invalid content. Attempt Block Recovery" in some areas. It appears that is an okay message and it's safe to click the Attempt Block Recovery button. Is that correct?
#1. Are you still investigating? I am thinking now that production works with WordPress 6.1.1 and Toolset Blocks, perhaps the solution for #1 is to update Staging to WordPress 6.1.1 and the line error will go away?
#3. The developer installed Toolset Blocks on production and deactivated Toolset Views. Everything is working fine now. I was able to update the Home page now that had the Fields and Text block.
I still see this message "This block contains unexpected or invalid content. Attempt Block Recovery" in some areas. It appears that is an okay message and it's safe to click the Attempt Block Recovery button. Is that correct?
==>
Yes, you should try that but please note that do not perform any action on production. First check on staging and then and then perform such action on production to be at safer side.
#1. Are you still investigating? I am thinking now that production works with WordPress 6.1.1 and Toolset Blocks, perhaps the solution for #1 is to update Staging to WordPress 6.1.1 and the line error will go away?
==>
It could as we do not get any other reports yet with the same warning. I could not able to give any guarantee on this but we always recommend using latest Toolset and WordPress version.
Warning: exif_imagetype(): stream does not support seeking in /home/customer/www/staging2.txwinelover.com/public_html/wp-includes/functions.php on line 3265
