Hi,

By now disable "Lazy Load" in SPPB 3.x and wait for stable SPPB 5.0.x - where all should be OK.

yes, SPPB 5.x get back-end editor.

As usual, bullshit. You don't respect who buy your products. If a bug appears, you don't take the opportunity to improve the code. "Disable lazy load..." is the recommendation you make. Don't care about the cost of it. "wait for stable SPPB 5.0.x - where all should be OK.". That's it: maybe, perhaps, possibly, perchance. Never one: sure, solved, problem identified and solved... Just troll.

I upgraded to SPPB 4.0.10 and the problem remains. What can make me believe that in 5.0.x it will be solved? Has anyone checked the specific situation? Instead of getting it fixed right away, you keep putting it off.

It only reinforces the decision: Never start developing a website using SPPB. There is no seriousness here.

For anyone having the same problem:

Place

error_reporting(0);

at the beginning of components/com_sppagebuilder/parser/addons.php

keep "lazy load" on and every time you upgrade SPPB, change it again in addons.php.

Goodbye forever! Perhaps.

error_reporting(0);

is a temporary solution, easier is hide showing errors in Global Configuration. As I said I informed our developer about that issue and will be fixed in stable SPPB 5.0.x update, so I don't understand your anger.

It's not a popular error becuase we would have more topics about that. This, of course, is not an excuse.

Paul Frankowski:

"As I said I informed our developer about that issue and will be fixed in stable SPPB 5.0.x update".

Two statements: The first is a lie, the second is true.

You didn't say you informed your developer.

The danger of the half-truth is that the liar means exactly half that is a lie.

Mixing the truth with the lie - this is something to which I dedicate my deepest repudiation.

The suggestion to hide error messages in the global configuration is great, and it eliminates the need to change PHP code with each update. Thanks!