Closed jeherve closed 1 month ago
cc @nateweller Since you had worked on #29842, I was wondering if you had ideas as to the turn of events that would lead to that error?
Thank you!
Interesting. My initial assumption is that Boost has the latest version of the Sync package, so it is being used by the autoloader (.../jetpack-boost/jetpack_vendor/automattic/jetpack-sync/...
).
Boost does not depend on the WAF package, and the Sync package only lists the WAF pack as a dev dependency to avoid loops/conflicts.
I'll look into this further, to see if we can configure things differently to avoid cases like this.
I ran into this error on a site running Jetpack Boost, Jetpack Protect, Jetpack Social, and Jetpack. The Protect module is enabled on the site.
The error appears to be triggered during a log in attempt.