Hello Iberezansky,
I appreciate your understanding and acknowledge your expertise. As I mentioned earlier, the challenge I’m facing doesn’t seem to be related to the plugin order.
I’ve previously asked for an email address to share a video demonstrating that the compatibility issue lies with the FlyingPress cache plugin. Unfortunately, it seems providing an email address is currently not an option. Therefore, I’ve included the video link here for your convenience:
https://www.veed.io/view/bcc2d34c-0f61-4cf5-a30f-16160637bdd8?panel=share
To reiterate, we’ve conducted tests in a staging environment, utilizing plugins like Plugin Load Order to ensure 3dFlipBook is prioritized. Despite this, activating FlyingPress afterward still results in the persisting error. Deactivating FlyingPress allows everything to function seamlessly. It’s crucial to note that FlyingPress does not impact the plugin order.
I kindly request that we explore alternative possibilities together, acknowledging the time and effort already invested in resolving this matter. I’ve been grappling with this issue for several months, and your patience and expertise are immensely appreciated.
It appears there might be an incompatibility with the FlyingPress plugin.
Thank you for your understanding and collaborative spirit.
Best regards,
álex