[Resolved] Receiving PHP Error views/invalidator(.)php on line 274'

[Author]

Posts

[haseebA]

Hi,

I've enabled SSH.

Thank you.

[Mateus Getulio]

I apologize for the back and forth.

I can confirm I'm able to access the SSH prompt for and password.

However, like the sFTP, I'm getting a wrong user/password error.

I tried using multiple combinations of the information you shared, between username and password but I'm unable to find a valid match so far.

Can you please review if those details are working on your end?

I enabled the private fields once more for you to share new data if needed.

Thank you for your patience.

With the SSH access I can get a dump of the DB and a zipped version of the site very quickly. With both files I can start debugging the issue locally and eventually escalate it to 2nd tier support among the package of the site.

[Mateus Getulio]

Hello there,

The SSH access worked and it allowed me to move on with the debugging.

This is a brief note to let you know that the work on the site continues.

I'll keep you updated.

[Mateus Getulio]

Hello there,

It looks like the issue is related to the new WordPress version 6.7.

In my local copy I downgraded it to version 6.6.2 and I'm no longer able to reproduce the issue.

We have a similar issue reported and investigated by our developers: https://toolset.com/errata/image-block-displays-wrong-image-size-with-wordpress-6-7/

For the time being, I'm afraid the only workaround is to downgrade to 6.6.2. Can you please confirm that the issue is not happening if you downgrade to the previous WordPress version?

I'll keep you updated regarding any news from our development team for a permanent fix.

[haseebA]

Please help me understand, following to issues are appearing way before the release of 6.7, how it can be related?

2. My Block Editor is also not working with CPTs.

2. I asked my hosting provider to me provide me with the list of most resource exhausting scripts and here they are,

269 toolset-blocks
219 cred-frontend-editor
177 elementor
143 site-reviews
73 types

[Mateus Getulio]

Hello there,

I can see in the debug info that WordPress was in version 6.6.2 when we started, but initially we were debugging the issues with the cached views. It looks like by the time you reported the issue with blocks, the WordPress was in version 6.7.

For example, I see that in the staging site the version is 6.6.2. It is the same setup I have locally. I made a few tests there and I can't replicate the issue. I'm able to use blocks for CPTs without triggering the error.

Can you please confirm that the issue is not happening in the staging?

If it is, can you share the steps to replicate the error or a quick video using loom.com or similar so that I can confirm we're debugging the same issue?

Thank you!

[haseebA]

I've checked the staging.

1. Block Editor for CPTs working fine.
2. Image uploading without error.

What next? Please advise.

Thank you.

[Mateus Getulio]

Thank you for your updates.

Our developers identified the issue and they're working actively to release a hotfix for this issue as soon as possible. A new release is expected within the next few days.

I'll let you know here in the ticket when a patch is available.

We apologize for the inconveniente and thank you for your patience.

[haseebA]

Hi,

What should I do next,

1. Push the staging (with older WP version) to live and wait for the fix and then update both.
2. Delete the staging, live with the current buggy version but with updated WP, wait for the fix.

Please advise.

[Mateus Getulio]

I would like to inform you that:

- we just released hotfix version for Toolset Blocks 1.6.18.
- We also released hotfix version for Toolset Access 2.9.2.

This will help you to fix the save/publish/update button misplaced and address the issue with the images size.

You can download it from your account's download page:
- https://toolset.com/account/downloads/

*** Please make a FULL BACKUP of your database and website.***
Can you please update All Toolset plugins to it's latest official version and I hope this will resolve your issues.

[haseebA]

Thank you for the support