-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Support for webp files (LiteSpeed Cache) #357
Comments
Hi @afonseca08, I think it's not something we can find generic solution, we have add support plugin by plugin. So we will try to include support for webp generated by ShortPixel inside of the existing compatibility for ShortPixel. |
Hi @alimuzzaman, thank you for following-up. I am already using the LiteSpeed Cache for WP plugin: Would you be able to look into LiteSpeed Cache plugin compatibility? |
@afonseca08 |
Hi @afonseca08 to test LiteSpeed do I have to install LiteSpeed server? |
Hi @afonseca08 |
@alimuzzaman Sure, I just sent you an e-mail. You don't need LiteSpeed server to use the plugin. |
@alimuzzaman Can you let me know what is the status of this issue? |
@antonkorotkov Here is the response:
|
Now webp will be synced on manual sync also.
@afonseca08 https://github.com/wpCloud/wp-stateless/tree/5751b06f2d38a9ffa3a973d0f1d51c7995086f17 |
Compatibility for ShortPixel Image Optimizer will be handle in separate issue #364. |
@alimuzzaman Can you explain how to test |
@antonkorotkov |
Hi, unfortunately this is not working for me, I just have the original files uploaded, none of then has webp version.
Someone can provide me some assistance? |
Although not yet a native WordPress format, several image conversion plugins support webp as well as caching plugins. Webp support is growing around the web and supported by modern browsers today. Those looking to optimize loading times are leveraging this new format as well as CDN technology so adding support for webp in wp-stateless would be beneficial.
The text was updated successfully, but these errors were encountered: