Hi Motion.Page Community.
After I updated Bricks to version 1.9.7 there are a lot of Problems in Motion.Page Plugin. It thows Errors every-where.
System
Browser:
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 Plugin in Version 2.1.6 throws a lot of errors in the Browser-Dev-Console.
Like this :
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
?motionpage_iframe=true
https://localdev-bricks.local/wp-admin/admin.php?page=motionpage*/```
Have solved it with
Have fixed it with this code in functions.php
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 1.9.6.1), everything worked perfectly again. But Bricks is not updatable anymore!
Questions:
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 secure Motion.Page from sideeffects from other Plugins/Themes like Bricks Builder (update)?
Looking forward to tips or help
_____
_____
Have done also a Bug-Report in Bricks https://forum.bricksbuilder.io/t/update-to-bricks-1-9-7-makes-system-buggy-error-throwing-slow-and-unreliable-in-combination-with-motion-page-plugin/20813
And Post in Motion.Page FB-Group: https://www.facebook.com/groups/motion.page/permalink/917252306769357/