I'm fighting a bit with your plugin. I'm coming to realise that it doesn't play nicely with Ewww.
I get background image Ken Burns, text animates on opening and closing sequence. What I don't get are image layers transitioning in or out, nor do they react to any parallax settings.
This happens when I force alternative webp rewriting. According to the author that employs `output buffering and libxml functionality from PHP`. Due to using nginx, I can't use the traditional method of rewriting via .htaccess.
Any ideas how to resolve it, or do I need to forget about webp?
The problem is the following, this plugin could integrate itself to the WP core functions and swap out the image URLs by using filter hooks.
But instead it changes the generated source code entirely, without any regards to custom attributes, causing this issue and interfering with LayerSlider or any other WP plugin.
Unfortunately we cannot solve this from our end, only the author of this plugin is able to adjust this behavior, to prevent problems like this.
Thanks for coming back to me. I have just received a similar answer from another plugin maker whose plugin was hampered by similar issue. Apparently the EWWW author will be working on a fix, but it might be a few weeks.
Hi,
I'm fighting a bit with your plugin. I'm coming to realise that it doesn't play nicely with Ewww.
I get background image Ken Burns, text animates on opening and closing sequence. What I don't get are image layers transitioning in or out, nor do they react to any parallax settings.
This happens when I force alternative webp rewriting. According to the author that employs `output buffering and libxml functionality from PHP`. Due to using nginx, I can't use the traditional method of rewriting via .htaccess.
Any ideas how to resolve it, or do I need to forget about webp?
Thanks,
Petr
Hello Petr,
The problem is the following, this plugin could integrate itself to the WP core functions and swap out the image URLs by using filter hooks.
But instead it changes the generated source code entirely, without any regards to custom attributes, causing this issue and interfering with LayerSlider or any other WP plugin.
Unfortunately we cannot solve this from our end, only the author of this plugin is able to adjust this behavior, to prevent problems like this.
Hi Attila,
Thanks for coming back to me. I have just received a similar answer from another plugin maker whose plugin was hampered by similar issue. Apparently the EWWW author will be working on a fix, but it might be a few weeks.
For the time being, I'll live without webp.
Many thanks.
Kind regards,
Petr
Thank you for the feedback, if you need further assistance please let us know.