NO BUG: Update to Bricks 1.9.7. makes System buggy, error throwing, slow and unreliable in combination with Motion.Page Plugin

Hope this is the right place to post “possible” bugs in connection with other plugins.
Chrome: Version 122.0.6261.129 (Offizieller Build) (x86_64)
Brave: Version 1.63.169 Chromium: 122.0.6261.111 (Offizieller Build) (x86_64)
And other Browsers

OS: macOS 11.7.10 (20G1427)
URL: Local Dev Environment

Problem: Error throwing in combination with Motion.Page and Bricks Update 1.9.7.

After update to Bricks 1.9.7 I have added all the needed Code-Signatures and also the Echo Functions Name Filter. JS-Code is working fine afterwards.

BUT Motion.Page GSAP Animation Plugin seams to have a lot of problems with this Bricks-Update.

I got first a few Browser Errors in the Console Like:

Because your site has the Cross-Origin Embedder Policy (COEP) enabled, each embedded iframe must also specify this policy. This behavior protects private data from being exposed to untrusted third party sites.
To solve this, add one of following to the embedded frame’s HTML response header:
Cross-Origin-Embedder-Policy: require-corp
Cross-Origin-Embedder-Policy: credentialless (Chrome > 96)
1 request
Request	Parent Frame	Blocked Resource


Have solved it with 

function add_cross_origin_embedder_policy_header() {
//header(‘Cross-Origin-Embedder-Policy: require-corp’); // problems with other Tools > change to credentialless
header(‘Cross-Origin-Embedder-Policy: credentialless’);
add_action(‘send_headers’, ‘add_cross_origin_embedder_policy_header’);```

With this Action the first Error was solved. But there seams to start more problems imediatelly.

Problem in the Backend

Motion.Page is not usable in the Backend.
There are errors in the console about problem to load react-stuff.

Problem in the Frontend

Some ScrollTriggers are complettly lost.

Try and error to find a solution

I tried fix by fix. But at the and the hole system seams to be buggy, slow and unreliable.

Solution (but only useful for a very short time)

When I restored the ServerBackup (to the old version with Bricks, everything worked perfectly again. But Bricks is not updatable anymore!


  • Does anyone had similar problems and found a solution?
  • Is the problem already known and is a bugfix perhaps already in the works?
  • is there a bestPratice to prevent Bricks from creating sideeffects on other plugins.?

Unfortunatelly currently it makes no sense to update to Bricks 1.9.7. Motion.Page and the system is no longer usable. But so, Bricks become unsafe.

Looking forward to tips or help

Hi Martin,
Thanks so much for your report!

Could you move your installation to a server so that we can examine the problem? Please send the access data and a link to this thread to

Best regards,

Hey @timmse,
Thank you for your fast response.
Have send Link and access data to

Hope will help to find and fix the bug in combination with

Hi @timmse,
with a lot of try&error I found the reason for the shifted scroll-trigger triggering in
Has to do with Bricksable Plugin and the element «read-more» and it’s JS-Code.
Have done a bug-report there.

Sorry to ask obviously in the wrong forum for it. Was hard to grasp. Because all other Plugins I had disabled but have to have re-enabling the bricksable to see the section built with element from them. So I guess, there is no side-effect from other plugin. wrongly guessed. :slightly_frowning_face:

Not solved until today, but on the right track now (I guess :wink:)

Hey Martin,
Thanks for the feedback and sorry I haven’t gotten back to you yet as I basically had to look at how works first as I’ve never used it before.

I’m glad to hear it’s not a Bricks bug though :slight_smile: