WebP Converter for Media

Beskrivelse

Speed up your website by serving WebP images. By replacing files in standard JPEG, PNG and GIF formats with WebP format, you can save over a half of the page weight without losing quality.

When installing a plugin you do not have to do anything more. Your current images will be converted into a new format. Users will automatically receive new, much lighter images than the original ones.

As of today, nearly 80% of users use browsers that support the WebP format. The loading time of your website depends to a large extent on its weight. Now you can speed up it in a few seconds without much effort!

This will be a profit both for your users who will not have to download so much data, but also for a server that will be less loaded. Remember that a better optimized website also affects your Google ranking.

New feature

Now you can also convert files from the /uploads directory into WebP and generated by other plugins! It allows full integration with the WebP format!

How does this work?

  • By adding images to your Media Library, they are automatically converted and saved in a separate directory.
  • If you have just installed the plugin, you can convert all existing images with one click.
  • Converting to WebP format works for all image sizes. As WebP you will see all the images added to the Media Library.
  • Images are converted using PHP GD or Imagick extension (you can modify the compression level).
  • When the browser tries to download an image file, the server verifies if it supports image/webp files and if the file exists.
  • If everything is OK, instead of the original image, the browser will receive its equivalent in WebP format.
  • The plugin does not change image URLs, so there are no problems with saving the HTML code of website to the cache and time of its generation does not increase. It does not matter if the image display as an img HTML tag or you use background-image. It works always!
  • The name of the loaded image does not contain the WebP extension. Only the source of the loaded file changes to a WebP file. As a result, you always have one URL to a file. Regardless of whether the browser supports WebP or not.
  • Image URLs are modified using the module mod_rewrite on the server, i.e. the same, and thanks to this we can use friendly links in WordPress. Additionally, the MIME type of the sent file is modified to image/webp.
  • When you try to save the image to disk (e.g. by clicking Save as…) the original image will be saved. WebP is only used for browser loading.
  • The final result is that your users download less than half of the data, and the website itself loads faster!

Support for additional directories

You can also manually convert images from the /plugins and /themes directories, as well as other images from the /uploads directory that are not in the Media Library (which are e.g. generated by other plugins). It allows full integration with the WebP format and maximum acceleration of your website.

WebP images are the future!

Raise your website to a new level now! Install the plugin and enjoy the website that loads faster. Surely you and your users will appreciate it.

Support to the development of plugin

We spend hours working on the development of this plugin. Technical support also requires a lot of time, but we do it because we want to offer you the best plugin. We enjoy every new plugin installation.

If you would like to appreciate it, you can provide us a coffee. If every user bought at least one, we could work on the plugin 24 hours a day!

Please also read the FAQ below. Thank you for being with us!

Skjermskudd

  • Screenshot of the options panel
  • Screenshot when regenerating images

Installasjon

  1. Upload the plugin files to /wp-content/plugins/webp-converter-for-media directory, or install plugin through the WordPress plugins screen directly.
  2. Activate plugin through Plugins screen in WordPress Admin Panel.
  3. Use Settings -> Settings -> WebP Converter screen to configure the plugin.
  4. Click on the button Regenerate All.
  5. Check if everything works fine.

That’s all! Your website is already loading faster!

FAQ

How to get technical support? (before you ask for help)

Please always adding your thread, read all other questions in the FAQ of plugin and other threads in support forum first. Perhaps someone had a similar problem and it has been resolved.

When adding a thread, follow these steps and reply to each of them:

1. Do you have any error on the plugin settings page? If so, which one? Have you consulted your server administrator or developer? If not, please do it first.

2. URL of your website. If your site is not publicly available, add it to test environment.

3. Does your server meet the technical requirements described in the FAQ? Please send configuration of your server (link to it can be found on the settings page of plugin in the section «We are waiting for your message») – please take a screenshot of the ENTIRE page and send it to me.

4. Do you use CDN? If so, please see the question «Does the plugin support CDN?» in plugin FAQ.

5. Check if in /wp-content/uploads-webpc directory are all files that should be converted.

If not, please enable WP_DEBUG_LOG in your wp-config.php (more about debugging: https://codex.wordpress.org/WP_DEBUG). That’s what you should have in this file:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

Then follow these steps:

  1. Go to administration panel and go to plugin settings page.
  2. Run Google Chrome and enable Dev Tools (F12).
  3. Go to the Network tab and select filtering for XHR (XHR and Fetch).
  4. Click button Regenerate All on the plugin settings page (do not close the console during this time).
  5. Go to Dev Tools and find request that is marked in red. Click on them and go to Preview tab.
  6. Take screenshot of all information presented there.
  7. Please check also if you have any errors in /wp-content/debug.log?

Send a screenshot from console if an error occurred while converting images. Of you have errors in /wp-content/debug.log send their?

6. If in the previous step it turned out that you have files, please do the test, which is described in the FAQ in question How to check if plugin works?. Please send a screenshot of Devtools with test results.

7. Content of your .htaccess files from directories /wp-content, /wp-content/uploads and /wp-content/uploads-webpc (pasting the code using the CODE shortcode in the editor).

8. Do you use any plugin filters or actions from this FAQ? If so, list them all.

9. What plugin version are you using? If it is not the latest then update and check everything again.

10. Used WordPress version.

11. A list of all the plugins you use. Have you tried checking the plugin operation by turning off all others and activating the default theme? If not, please try whenever possible. This is very important because other plugins or themes can cause problems. Therefore, we recommend disabling all necessary plugins and enabling the default theme.

Please remember to include the answers for all 11 questions by adding a thread. It is much easier and accelerate the solution of your problem.

Error on plugin settings screen?

If you have an error on the plugin settings screen, first of all please read it carefully. They are displayed when there is a problem with the configuration of your server or website.

The messages are designed to reduce the number of support requests that are repeated. It saves your and our time. If you have information in the message that you should contact the administrator of your server, please do so.

When contacting the administrator, give him all the information available in the message. If you still cannot solve the problem, please contact us.

We want to solve as many similar problems as possible automatically. This eliminates the need to wait for our response and you can try to solve the problem alone. This is very important for us.

Error while converting?

You can get several types of errors when converting. First of all, carefully read their content. For the most part, you can solve this problem yourself. Try to do this or contact the server administrator.

If you get an error: File "%s" does not exist. Please check file path. means that the file_exists() function in PHP returned false using the file path given in the error message. Check this path and make sure it is correct.

If you get an error: File "%s" is unreadable. Please check file permissions. means that the is_readable() function in PHP returned false using the file path given in the error message. Check the permissions for the file and the directory in which the file is located.

If you get an error: "%s" is not a valid image file. means that the file is damaged in some way. Download the file to disk, save it again using any graphics program and add again to the page. If the error applies to individual images then you can ignore it – just the original images will load, not WebP.

If you get an error: "%s" converted to WebP is larger than original and has been deleted. means the original image weighed less than WebP. This happens when images have been compressed before. Disable the «Automatic removal of WebP files larger than original» option in plugin settings to force always using WebP.

In the case of the above problems, contacting the support forum will be useless. Unfortunately, we are unable to help you if your files are damaged. You have to fix it yourself. If you have previously used other tools that changed the original files and damaged them, you will do nothing more.

Remember that it happens that other plugins can cause problems with accessing files or the REST API. Please try to disable all other plugins and set the default theme to make sure that it is not one of them that causes these types of problems.

What are requirements of plugin?

Practically every hosting meets these requirements. You must use PHP at least 7.0 and have the GD or Imagick extension installed. The extension must support WebP format. If you have an error saying that the GD or Imagick library are not installed, but you have it installed then they are probably incorrectly configured and do not have WebP support.

They are required native PHP extensions, used among others by WordPress to generate thumbnails. Your server must also have the modules mod_mime, mod_rewrite and mod_expires enabled.

An example of the correct server configuration can be found here. Link to your current configuration can be found in the administration panel, on the management plugin page in the section «We are waiting for your message» (or using the URL path: /wp-admin/options-general.php?page=webpc_admin_page&action=server).

Note the items marked in red. If the values marked in red do not appear in your case, it means that your server does not meet the technical requirements. Pay attention to the WebP Support value for the GD library and WEBP in the list of supported extensions for the Imagick library.

In a situation where your server does not meet the technical requirements, please contact your server Administrator. We are not able to help you. Please do not contact us about this matter, because this is a server configuration problem, not a plugin.

Also REST API must be enabled and work without additional restrictions. If you have a problem with it, please contact the Developer who created your website. He should easily find the issue with the REST API not working.

What are restrictions?

The size of the image is a limited. Its resolution cannot be bigger than 8192 x 8192px. This is due to the limitations of the PHP library.

Please remember that Safari and Internet Explorer do not support the WebP format. Therefore, using these browsers you will receive original images.

You can find more about WebP support by browsers here.

Damaged images on iOS or other browsers

The plugin uses rules in the .htaccess file to redirect from the original image to an image in WebP format. Verifies whether the WebP file exists and whether your browser supports the WebP format. It does this every time you try to load an image.

When you enter from a WebP supporting device, it will redirect. However, when someone uses a browser that does not support WebP, the redirection will not work and you get the original file.

However, if you see corrupted images on browsers that do not support WebP, it means that your server uses cache for rewrites from the .htaccess file. Then the plugin will not work properly because the server instead of reading the rules from the .htaccess file every time uses its cache and does the redirection automatically.

How can you check it? When you turn off the plugin, the rewrites from the .htaccess file are removed, which means you should see the original images on every browser. If this is not the case and you see forced redirects to WebP files, it means that your server remembers the redirects you made earlier and uses cache.

In this situation, please contact your server administrator. Each configuration is different. It can be e.g. module mod_pagespeed or other similar. This functionality must be turned off so that the server reads and executes the rules from the .htaccess file each time the images are loaded. This cannot be ignored because it will cause problems.

What to do after installing plugin?

After installing the plugin, you should convert all existing images.

In the WordPress admin panel, on the Settings -> WebP Converter subpage there is a module that allows you to process all your images.

It uses the WordPress REST API by downloading addresses of all images and converting all files gradually.

This process may take few or more than ten minutes depending on the number of files.

It should be done once after installing the plugin. New images from the Media Library will be converted automatically. For other images, e.g. from the /themes directory, you must start manual conversion after adding new images.

How to check if plugin works?

When you have installed plugin and converted all images, follow these steps:

  1. Run Google Chrome and enable Dev Tools (F12).
  2. Go to the Network tab and select filtering for Img (Images).
  3. Refresh your website page.
  4. Check list of loaded images. Note Type column.
  5. If value of webp is there, then everything works fine.
  6. Remember that this plugin does not change URLs. This means that e.g. link will have path to .jpg file, but .jpg.webp file will be loaded instead of original .jpg.
  7. In addition, you can check weight of website before and after using plugin. The difference will be huge!
  8. More information: here

Please remember that URLs will remain unchanged. When you open the image in a new tab or look at its URL, you’ll see the original URL. When you try to save the image to disk (e.g. by clicking Save as…) the original image will be saved.

WebP is only used when loading a image on a website. This is done by the rules from the .htaccess file, on the server side, without the visible URL change to the image. Yes, it can be called magic 🙂

That is why the plugin should be tested in Dev Tools. If the Type of file is WebP, then everything is working properly. You can also turn off the plugin for a moment and check the weight of your website, then turn it on and test again. The difference should be visible.

The operation of the plugin for non-advanced users may sometimes be less understood, but everything is fine. Thanks to this, regardless of whether your browser supports WebP or not, everything works without problems.

Only images from the /uploads directory are automatically converted. If you use other plugins that also save images in the /uploads directory then this may not work. Therefore, check the plugin settings and try converting all images again.

Why are some images not in WebP?

If the converted image in WebP format is larger than the original, the browser will use the original file. This converted file will be deleted. Therefore, you can also see files other than WebP on the list. When this happens, you will receive information in debug.log.

If you want to force the use of WebP files, uncheck the Automatic removal of WebP files larger than original option in the plugin settings. Then click on the Regenerate All button to convert all images again.

Remember that this plugin supports images from the /wp-content directory, e.g. files downloaded from the Media Library. Redirections will not work if your images are downloaded from another domain, i.e. from an external service.

When checking the operation of the plugin, e.g. in Dev Tools, pay attention to the path from which the files are downloaded and which directories you have enabled in the settings of plugin.

Where are converted images stored?

All WebP images are stored in the /wp-content/uploads-webpc/ directory. Inside the directory there is the same structure as in the original /wp-content directory. The files have original extensions in the name along with the new .webp.

In case the location of the original file is as follows: /wp-content/uploads/2019/06/example.jpg then its converted version will be in the following location: /wp-content/uploads-webpc/uploads/2019/06/example.jpg.webp.

In case the location of the original file is as follows: /wp-content/themes/my-theme/public/img/example.jpg then its converted version will be in the following location: /wp-content/uploads-webpc/themes/my-theme/public/img/example.jpg.webp.

Original images are not changed. If you remove plugins, only WebP files will be deleted. Your images are not changed in any way.

How to change path to uploads?

This is possible using the following types of filters to change default paths. It is a solution for advanced users. If you are not, please skip this question.

Path to the root installation directory of WordPress (ABSPATH by default):

add_filter('webpc_uploads_root', function($path) {
  return ABSPATH;
});

Path to /uploads directory (relative to the root directory):

add_filter('webpc_uploads_path', function($path) {
  return 'wp-content/uploads';
});

Directory path with converted WebP files (relative to the root directory):

add_filter('webpc_uploads_webp', function($path) {
  return 'wp-content/uploads-webpc';
});

Note that the /uploads-webpc directory must be at the same nesting level as the /uploads, /plugins and /themes directories.

Prefix in URL of /wp-content/ directory or equivalent (used in .htaccess):

add_filter('webpc_uploads_prefix', function($prefix) {
  return '/';
});

For the following sample custom WordPress structure:

...
├── web
    ...
    ├── app
    │   ├── mu-plugins
    │   ├── plugins
    │   ├── themes
    │   └── uploads
    ├── wp-config.php
    ...

Use the following filters:

add_filter('webpc_uploads_root', function($path) {
  return 'C:/WAMP/www/project/webp'; // your valid path
});
add_filter('webpc_uploads_path', function($path) {
  return 'app/uploads';
});
add_filter('webpc_uploads_webp', function($path) {
  return 'app/uploads-webpc';
});
add_filter('webpc_uploads_prefix', function($prefix) {
  return '/';
});

After setting the filters go to Settings -> WebP Converter in the admin panel and click the Save Changes button. .htaccess files with appropriate rules should be created in the directories /uploads and /uploads-webpc.

How to run manually conversion?

By default, all images are converted when you click on the Regenerate All button. In addition, conversion is automatic when you add new files to your Media Library.

Remember that our plugin takes into account images generated by WordPress. There are many plugins that generate, for example, images of a different size or in a different version.

If you would like to integrate with your plugin, which generates images by yourself, you can do it. Our plugin provides the possibility of this type of integration. This works for all images in the /wp-content directory.

It is a solution for advanced users. If you would like to integrate with another plugin, it’s best to contact the author of that plugin and give him information about the actions available in our plugin. This will help you find a solution faster.

You can automatically run the option to regenerate all new images. This is useful when you use external plugins that generate images themselves. To do this, use the following code:

do_action('webpc_regenerate_all', $paths);

Below is an example of how to use this action to automatically regenerate images after changing the theme:

add_action('init', function()
{
  do_action('webpc_regenerate_all');
});

To manually start converting selected files, you can use the action to which you will pass an array with a list of paths (they must be absolute server paths):

do_action('webpc_convert_paths', $paths);

An alternative method is to manually start converting the selected attachment by passing the post ID from the Media Library. Remember to run this action after registering all image sizes (i.e. after running the add_image_size function):

do_action('webpc_convert_attachment', $postId);

In addition, you can edit the list of files that will be converted. For example, to add some to the exceptions. To do this, use the following filter, which by default returns a list of all paths:

add_filter('webpc_attachment_paths', function($paths, $attachmentId) {
  return $paths;
}, 10, 2);

Argument $paths is array of absolute server paths and $attachmentId is the post ID of attachment, added to the Media Library.

To delete manually converted files, use the following action, providing as an argument an array of absolute server paths to the files (this will delete manually converted files):

do_action('webpc_delete_paths', $paths);

How to change .htaccess rules?

Manually editing the rules in the .htaccess file is a task only for experienced developers. Remember that the wrong rules can cause your website to stop working.

Below is a list of filters that allow you to modify all rules. Remember that it’s best to use your own rule set rather than edit parts of exists. This will ensure greater failure-free after plugin update.

Returning an empty string will delete these rules the next time you save the plugin settings. You must do this after each filter edit.

Rules for redirects: (returns rules for mod_rewrite module):

add_filter('webpc_htaccess_mod_rewrite', function($rules, $path) {
  return '';
}, 10, 2);

Argument $path is absolute server path for .htaccess file (/wp-content/.htaccess or /wp-content/uploads/.htaccess).

Rules for image/webp MIME type: (returns rules for mod_mime module):

add_filter('webpc_htaccess_mod_mime', function($rules) {
  return '';
});

Rules for Browser Caching: (returns rules for mod_expires module):

add_filter('webpc_htaccess_mod_expires', function($rules) {
  return '';
});

All rules from the files /wp-content/.htaccess, /wp-content/uploads/.htaccess and /wp-content/uploads-webpc/.htaccess: (returns rules for modules: mod_rewrite, mod_mime and mod_expires):

add_filter('webpc_htaccess_rules', function($rules, $path) {
  return '';
}, 10, 2);

Argument $path is absolute server path for .htaccess file.

What is Browser Caching?

This option allows you to speed up page loading time for returning users because they do not need to re-download files from the server. The plugin allows this by using the module mod_expires.

It is enabled by default. If you do not want to use this functionality, you can turn it off at any time.

Does plugin support CDN?

Unfortunately not. This is due to the logic of the plugin’s operation. Plugins that enable integration with the CDN servers modify the HTML of the website, changing URLs for media files. This plugin does not modify URLs. Replacing URLs in the HTML code is not an optimal solution.

The main problem when changing URLs is cache. When we modify the image URL for WebP supporting browser, then use the browser without WebP support, it will still have the URL address of an image in .webp format, because it will be in the cache.

While in the case of the img tag you can solve this problem, in the case of background-image it is possible. We wanted full support so that all images would be supported – no matter how they are displayed on the website.

Therefore in this plugin for browsers supporting the WebP format, only the source of the file is replaced by using the mod_rewrite module on the server. The URL for image remains the same. This solves the whole problem, but it is impossible to do when the files are stored on the CDN server.

If you are using a CDN server, find one that automatically converts images to WebP format and properly sends the correct image format to the browser.

Configuration for Nginx

Please edit the configuration file:

/etc/nginx/mime.types

and add this code:

types {
  # ...

  image/webp webp;
}

Then please find your configuration file in the path (default is default file):

/etc/nginx/sites-available/

and add below code in this file:

server {
  # ...

  location ~ /wp-content/(?<path>.+)\.(?<ext>jpe?g|png|gif)$ {
    if ($http_accept !~* "image/webp") {
      break;
    }
    add_header Vary Accept;
    expires 365d;
    try_files /wp-content/uploads-webpc/$path.$ext.webp $uri =404;
  }
}

Configuration for Multisite Network

Yes, with one exception. In this mode it is not possible to automatically generate the contents of .htaccess files.

Please manually paste the following code at the beginning of .htaccess file in the /wp-content directory:

# BEGIN WebP Converter
# ! --- DO NOT EDIT PREVIOUS LINE --- !
<IfModule mod_rewrite.c>
  RewriteEngine On
  RewriteCond %{HTTP_ACCEPT} image/webp
  RewriteCond %{DOCUMENT_ROOT}/wp-content/uploads-webpc/$1.jpg.webp -f
  RewriteRule (.+)\.jpg$ /wp-content/uploads-webpc/$1.jpg.webp [NC,T=image/webp,E=cache-control:private,L]
  RewriteCond %{HTTP_ACCEPT} image/webp
  RewriteCond %{DOCUMENT_ROOT}/wp-content/uploads-webpc/$1.jpeg.webp -f
  RewriteRule (.+)\.jpeg$ /wp-content/uploads-webpc/$1.jpeg.webp [NC,T=image/webp,E=cache-control:private,Lp]
  RewriteCond %{HTTP_ACCEPT} image/webp
  RewriteCond %{DOCUMENT_ROOT}/wp-content/uploads-webpc/$1.png.webp -f
  RewriteRule (.+)\.png$ /wp-content/uploads-webpc/$1.png.webp [NC,T=image/webp,E=cache-control:private,L]
</IfModule>
# ! --- DO NOT EDIT NEXT LINE --- !
# END WebP Converter

And the following code at the beginning of .htaccess file in the /wp-content/uploads-webpc directory:

# BEGIN WebP Converter
# ! --- DO NOT EDIT PREVIOUS LINE --- !
<IfModule mod_mime.c>
  AddType image/webp .webp
</IfModule>
<IfModule mod_expires.c>
  ExpiresActive On
  ExpiresByType image/webp "access plus 1 year"
</IfModule>
# ! --- DO NOT EDIT NEXT LINE --- !
# END WebP Converter

Is the plugin completely free?

Yes. The plugin is completely free.

However, working on plugins and technical support requires many hours of work. If you want to appreciate it, you can provide us a coffee. Thanks everyone!

Thank you for all the ratings and reviews.

If you are satisfied with this plugin, please recommend it to your friends. Every new person using our plugin is valuable to us.

This is all very important to us and allows us to do even better things for you!

Vurderinger

12. august, 2020
It did just as expected except but for one thing and it's probably a simple solution and/or reason "not a valid file image" (jpg)? Not sure what that means but so far everything is working as it should
11. august, 2020
This plugin actually works. Many thanks for this. Great work. I've checked that it works using the Dev Tools, thanks a lot.
Les alle 120 vurderinger

Bidragsytere og utviklere

“WebP Converter for Media” er programvare med åpen kildekode. Følgende personer har bidratt til denne utvidelsen.

Bidragsytere

“WebP Converter for Media” har blitt oversatt til 7 språk. Takk til oversetterne for deres bidrag.

Oversett “WebP Converter for Media” til ditt språk.

Interessert i utvikling?

Bla gjennom koden, sjekk ut SVN-repositoriet, eller abonner på utviklingsloggen med RSS.

Endringslogg

1.4.0 (2020-08-13)

  • [Removed] Filter webpc_notice_url
  • [Changed] Error messages for server requirements
  • [Changed] Loading CSS and JS files only on plugin settings page
  • [Changed] Minor changes for plugin settings page
  • [Changed] Validation of saved settings values for security
  • [Added] Blocking redirects to WebP when displaying images on other domains
  • [Added] Cron to automatically regenerate new images outside of Media Library
  • [Added] Filter webpc_cron_interval to change cron interval
  • [Added] Error message for incorrect plugin settings
  • [Added] Error when converting when WebP file is larger than original and has been deleted
  • [Added] Notice after plugin installation with description of first steps
  • [Added] Option to log errors while converting to debug.log file
  • [Added] Option to preserve metadata for WebP files (available for Imagick library)
  • [Added] Value of ABSPATH in Server configuration tab

1.3.1 (2020-07-03)

  • [Fixed] Text Domain for Internationalization

1.3.0 (2020-06-12)

  • [Removed] Ability to skip converting existing images when Regenerate All
  • [Fixed] Creating /uploads-webpc directory webpc after re-activation plugin
  • [Fixed] Error message about not supporting old PHP version
  • [Fixed] Ignoring case sensitivity when verifying image extensions
  • [Changed] Error messages when converting images
  • [Changed] New argument for filter webpc_htaccess_mod_rewrite and support for multiple .htaccess files
  • [Added] Converting all images from /uploads directory (also other than from Media Library).
  • [Added] Converting images from /plugins directory
  • [Added] Converting images from /themes directory
  • [Added] Information about used filters in Server configuration tab
  • [Added] Option to force all images to be converted again when Regenerate All

1.2.7 (2020-06-11)

  • [Changed] Moving converted WebP files to /uploads-webpc/uploads directory from /uploads-webpc directory (required manual configuration change for Nginx and WordPress Multisite)
  • [Changed] Validation when converting images

1.2.6 (2020-05-28)

  • [Fixed] Removal of WebP files larger than original during upload

1.2.5 (2020-05-10)

  • [Removed] Link to plugin settings on Network Admin Screen for WordPress Multisite
  • [Fixed] Path in RewriteRule for WordPress Multisite
  • [Changed] Error messages in administration panel
  • [Added] Support for disable_functions setting for using set_time_limit function
  • [Added] Support for blocked function file_get_contents

1.2.4 (2020-04-24)

  • [Changed] Error messages in administration panel
  • [Added] Action webpc_delete_paths to delete images by paths

1.2.3 (2020-04-15)

  • [Added] Blocking server cache for rewrite rules
  • [Added] Detecting whether requests to images are processed by server bypassing Apache

1.2.2 (2020-04-08)

  • [Changed] Moving rules for modules mod_mime and mod_expires to /uploads-webpc/.htaccess file
  • [Changed] New argument for filter webpc_htaccess_rules with server path of file

1.2.1 (2020-04-07)

  • [Removed] Filter webpc_option_disabled
  • [Fixed] Converting images multiple times when uploading to Media Library
  • [Added] Action webpc_convert_paths to convert images by paths
  • [Added] Action webpc_convert_attachment to convert images by Post ID

1.2.0 (2020-04-05)

  • [Changed] Moving rules from .htaccess file in root directory of WordPress to /wp-content/uploads directory
  • [Added] Ability to disable automatic removal of WebP files larger than original
  • [Added] Error validation for a non-writable .htaccess file
  • [Added] Filter webpc_uploads_root to change path for root installation directory of WordPress

1.1.2 (2020-03-03)

  • [Added] Zero padding at end for odd-sized WebP files using GD library

1.1.1 (2020-02-13)

  • [Changed] Unknown error handling when converting images
  • [Added] Ability to skip converting existing images when Regenerate All
  • [Added] Button for simple checking of server configuration

1.1.0 (2020-02-10)

  • [Fixed] Support for WordPress installation in subdirectory
  • [Fixed] Error detecting WebP support by Imagick

1.0.9 (2020-01-03)

  • [Added] Limit of maximum image resolution limit using GD library

1.0.8 (2019-12-19)

  • [Fixed] File deletion for custom paths with converted WebP files
  • [Changed] Rules management in .htaccess file when activating or deactivating plugin
  • [Added] Error detection system in server configuration
  • [Added] Blocking image conversion when GD or Imagick libraries are unavailable

1.0.7 (2019-12-17)

  • [Changed] Rewrite rules in .htaccess file
  • [Added] Custom path support for original uploads files
  • [Added] Custom path support for saving converted WebP files
  • [Added] Filter webpc_uploads_path to change path for original uploads files
  • [Added] Filter webpc_uploads_webp to change path for saving converted WebP files

1.0.6 (2019-11-06)

  • [Changed] Way of generating file path (without ABSPATH)
  • [Added] Automatic deletion of converted files larger than original

1.0.5 (2019-09-16)

  • [Added] Information on available FAQ

1.0.4 (2019-07-11)

  • [Changed] Limits of maximum execution time

1.0.3 (2019-06-26)

  • [Added] Additional security rules

1.0.2 (2019-06-25)

  • [Changed] Error messages
  • [Added] Tab in Settings page about server configuration

1.0.1 (2019-06-23)

  • [Changed] Securing access to REST API
  • [Added] Error handler for undefined GD extension

1.0.0 (2019-06-16)

  • The first stable release