WebP Converter for Media

Opis

Przyspiesz swoją witrynę wyświetlając obrazki WebP. Zastępując pliki w standardowych formatach JPEG, PNG oraz GIF formatem WebP, możesz zaoszczędzić ponad połowę wagi strony bez utraty jakości.

Po instalacji wtyczki nie musisz nic więcej robić. Twoje istniejące obrazki zostaną skonwertowane do nowego formatu. Gdy kompresowanie obrazków będzie zakończone, użytkownicy automatycznie otrzymają nowe, znacznie mniejsze obrazki niż oryginalne.

Obecnie ponad 90% użytkowników korzysta z przeglądarek obsługujących format WebP. Czas ładowania Twojej witryny zależy w dużej mierze od jej wagi. Teraz możesz ją przyspieszyć w kilka sekund bez większego wysiłku!

Będzie to korzyść zarówno dla Twoich użytkowników, którzy nie będą musieli pobierać tak dużej ilości danych, jak i dla mniej obciążonego serwera. Pamiętaj, że lepiej zoptymalizowana witryna wpływa również na Twój ranking w Google.

Wsparcie dla dodatkowych katalogów

Teraz możesz również optymalizować obrazki nie tylko z katalogu /uploads, ale także z katalogów /plugins oraz /themes . Pozwala to na pełną integrację z formatem WebP!

Jak to działa?

  • Dodając obrazy do biblioteki multimediów, są one automatycznie konwertowane i zapisywane w oddzielnym katalogu.
  • Jeśli właśnie zainstalowałeś wtyczkę, możesz jednym kliknięciem zoptymalizować wszystkie istniejące obrazki.
  • Jako WebP zobaczysz wszystkie obrazki dodane do biblioteki multimediów oraz innych wybranych katalogów.
  • Kiedy przeglądarka próbuje pobrać plik obrazu to serwer sprawdza, czy obsługuje pliki image/webp i czy plik istnieje.
  • Jeśli wszystko jest w porządku, zamiast oryginalnego obrazu przeglądarka otrzyma jego odpowiednik w formacie WebP.
  • W domyślnym trybie ładowania wtyczka nie zmienia adresów URL obrazków, więc nie ma problemów z zapisaniem kodu HTML strony do pamięci podręcznej i czas jego wygenerowania się nie wydłuża. Nie ma znaczenia, czy obraz wyświetlany jest jako znacznik HTML img lub użyty jest jako background-image. Działa zawsze!
  • Nazwa załadowanego obrazka nie zawiera rozszerzenia WebP. Tylko źródło załadowanego pliku zmienia się na plik WebP. W rezultacie zawsze masz jeden adres URL do pliku. Niezależnie od tego, czy przeglądarka obsługuje WebP, czy nie.
  • Adresy URL obrazków modyfikujemy za pomocą modułu mod_rewrite na serwerze, czyli tym samym, dzięki któremu możemy korzystać z przyjaznych linków w WordPress. Dodatkowo typ MIME wysyłanego pliku jest modyfikowany na image/webp.
  • W przypadku, gdy przepisywanie reguł z pliku .htaccess jest zablokowane, dostępny jest tryb, który ładuje obrazy poprzez plik PHP. Następnie zmieniane są adresy URL obrazków, ale logika działania jest taka sama, jak w przypadku trybu domyślnego.
  • W efekcie użytkownicy pobierają mniej niż połowę danych, a sama witryna ładuje się szybciej!

Obrazki w formacie WebP to przyszłość!

Optymalizuj obrazki i przenieś swoją stronę internetową na nowy poziom już teraz! Zainstaluj wtyczkę i ciesz się szybszym ładowaniem strony internetowej dzięki optymalizacji obrazków. Z pewnością Ty i Twoi użytkownicy to docenicie.

Wsparcie w rozwoju wtyczki

Spędzamy wiele godzin pracując nad rozwojem tej wtyczki. Wsparcie techniczne również wymaga dużo czasu, ale robimy to, ponieważ chcemy zaoferować Tobie najlepszą wtyczkę. Cieszymy się z każdej nowej instalacji wtyczki.

Jeśli chcesz to docenić, możesz postawić nam kawę. Gdyby każdy użytkownik kupił przynajmniej jedną, moglibyśmy pracować nad wtyczką 24 godziny na dobę!

Przeczytaj również poniższe FAQ. Dziękujemy, że jesteście z nami!

Zrzuty ekranów

  • How to start using plugin few moments?
  • Screenshot of the options panel
  • Screenshot when regenerating images

Instalacja

  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? Please read this thread if you have any errors.

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

3. 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. Settings of plugin – please take a screenshot of the ENTIRE page and send it to me.

5. 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.

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

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

8. 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 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. Please read this thread for more information.

Server configuration error on Cloudflare

For Cloudflare servers, a recurring problem is the error code rewrites_cached. To solve this problem, you need to disable the cache for the website from the server.

Please follow the steps below:
– Enter Cloudflare management panel and then to Page Rules Tab.
– Click Create page rule button.
– Enter your domain name.
– Choose Cache Level option, set Bypass value and click Save button.
– Click Save and Deploy button.

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.

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 in default loading mode (via .htaccess) 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. In default loading mode (via .htaccess) it 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.

When such a situation occurs, a file in .webp.deleted format will be created. This avoids re-converting images that were larger than original after converting to WebP. If the option of forced conversion of all images is checked, this image will also be re-converted.

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.

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_site_root', function( $path ) {
    return ABSPATH;
} );

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

add_filter( 'webpc_dir_name', function( $path, $directory ) {
    if ( $directory !== 'uploads' ) {
        return $path;
    }
    return 'wp-content/uploads';
}, 10, 2 );

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

add_filter( 'webpc_dir_name', function( $path, $directory ) {
    if ( $directory !== 'webp' ) {
        return $path;
    }
    return 'wp-content/uploads-webpc';
}, 10, 2 );

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_site_root', function( $path ) {
    return 'C:/WAMP/www/project/webp'; // your valid path to root
} );
add_filter( 'webpc_dir_name', function( $path, $directory ) {
    if ( $directory !== 'uploads' ) {
        return $path;
    }
    return 'app/uploads';
}, 10, 2 );
add_filter( 'webpc_dir_name', function( $path, $directory ) {
    if ( $directory !== 'webp' ) {
        return $path;
    }
    return 'app/uploads-webpc';
}, 10, 2 );
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?

Domyślnie wszystkie obrazki są konwertowane po kliknięciu przycisku Konwertuj wszystkie. Ponadto konwertowanie jest automatycznie wykonywane po przesłaniu nowych plików do biblioteki multimediów.

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', $post_id );

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_files_paths', function( $paths, $skip_exists ) {
    return $paths;
}, 10, 2 );

Argument $paths is array of absolute server paths and $skip_exists means whether to skip converted images.

You can also modify the list of image paths for an attachment, e.g. to exclude one image size. To do this, use the following filter:

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

Argument $paths is array of absolute server paths and $attachment_id 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.

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 Apache

In the case of Apache, when saving the settings, .htaccess files will be generated automatically in the following locations:
/wp-content/.htaccess
/wp-content/uploads/.htaccess
/wp-content/uploads-webpc/.htaccess

If these files are missing or empty, try disabling and re-enabling the plugin or saving the plugin settings again. Also check the write permissions of the directories where these files are located.

If your server is a combination of Apache and Nginx, remember that the image files must be supported by Apache. Only then will the redirections in the .htaccess file work properly. Alternatively, you can use the configuration for Nginx.

Configuration for Nginx

Please edit the configuration file:
/etc/nginx/mime.types

and add this code line:

types {
    # ...
    image/webp webp;
}

Then find the configuration file in one of the paths (remember to select configuration file used by your vhost):
/etc/nginx/sites-enabled/
/etc/nginx/conf.d/

and add below code in this file (add these lines to very beginning of file if possible – if they will be at the bottom, other rules may block the rules for WebP from working):

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;
    }
    # ...
}

After making changes, remember to restart the machine: systemctl restart nginx.

Configuration for Multisite Network

Multisite Network mode works fine but requires adding configuration manually.

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:no-cache,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:no-cache,L]
    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:no-cache,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!

Recenzje

15 maja 2021
Mi ha alleggerito di tanto il sito compattando le immagini. è un plugin che fa quello che promette.
14 maja 2021
used in different configurations with LiteSpeed Cache and Swift Performance - works as it should, with Swift Performance you need to copy its rewrites from .htaccess to settings/general/tweaks/Custom Htaccess
14 maja 2021
Hi 👋 I like your plugin, but can you please add a mode with HTML <picture>, eg replace standard <img /> to <picture> <source srcset="img/awesomeWebPImage.webp" type="image/webp"> <img src="img/creakyOldJPEG.jpg" alt="Alt Text!"> </picture> It would be fantastic
Przeczytaj 299 recenzji

Kontrybutorzy i deweloperzy

„WebP Converter for Media” jest oprogramowaniem open source. Poniższe osoby miały wkład w rozwój wtyczki.

Zaangażowani

Wtyczka “WebP Converter for Media” została przetłumaczona na 9 języków. Podziękuj tłumaczom za ich wkład.

Przetłumacz wtyczkę “WebP Converter for Media” na swój język.

Interesuje cię rozwój wtyczki?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Log zmian

3.0.1 (2021-05-09)

  • [Fixed] Filters using for change server paths
  • [Added] Excluding directories when uploading images to Media Library

3.0.0 (2021-05-02)

  • [Removed] Filter webpc_get_values
  • [Removed] Filter webpc_get_options
  • [Removed] Filter webpc_get_methods
  • [Changed] Error messages on plugin settings page
  • [Added] Conversion of images to multiple output formats
  • [Added] Compatibility with NextGEN Gallery plugin
  • [Added] Data displayed on „Server configuration” tab on plugin settings page
  • [Added] Changes to improve performance of plugin
  • [Added] Changes to improve security of plugin

2.4.0 (2021-02-28)

  • [Fixed] Error detection of redirects without .png as supported file extension
  • [Fixed] Pass Thru loading mode for servers not supporting getallheaders() function
  • [Changed] Level of error for cached redirects of images to WebP files
  • [Added] Skip re-converting images that were larger than original after converting to WebP

2.3.0 (2021-01-31)

  • [Fixed] Encoding paths to files
  • [Fixed] Retaining PNG transparency using Gd method
  • [Added] Cron to convert images uploaded to Media Library

2.2.0 (2021-01-13)

  • [Added] Support for WordPress Multisite

2.1.3 (2020-12-28)

  • [Fixed] Regex for Pass Thru loading mode

2.1.2 (2020-12-27)

  • [Fixed] Converting images using Imagick method

2.1.1 (2020-12-21)

  • [Fixed] Modal when deactivating plugin

2.1.0 (2020-12-21)

  • [Changed] Structure of conversion methods
  • [Changed] Structure of error detection methods

2.0.1 (2020-12-16)

  • [Fixed] Actions initiated after plugin update

2.0.0 (2020-12-16)

  • [Removed] Filter webpc_uploads_path
  • [Removed] Filter webpc_uploads_webp
  • [Removed] Filter webpc_uploads_dir
  • [Removed] Filter webpc_uploads_root
  • [Changed] Error messages in administration panel
  • [Added] Image loading mode: Pass Thru (without rewrites in .htacces files or Nginx configuration)
  • [Added] Filter webpc_dir_name to change default directory paths
  • [Added] Filter webpc_site_root to change path for root installation directory of WordPress
  • [Added] Filter webpc_site_url to change Site URL of WordPress

1.6.0 (2020-12-12)

  • [Added] Escaping functions for translated phrases
  • [Added] Error codes in error messages on plugin settings page
  • [Added] Modal when deactivating plugin

1.5.1 (2020-11-02)

  • [Changed] Error messages related to non-working redirects from .htaccess file

1.5.0 (2020-10-28)

  • [Added] Filter webpc_files_paths to modify paths of images to be converted
  • [Added] Filter webpc_convert_error to management of errors content displayed during conversion
  • [Added] Filter webpc_convert_errors to management of errors displayed during conversion

1.4.6 (2020-10-23)

  • [Fixed] Error detection of non-working redirects without .png as supported file extension

1.4.5 (2020-10-19)

  • [Fixed] Content for translations

1.4.4 (2020-10-18)

  • [Changed] Information after conversion process is completed

1.4.3 (2020-09-30)

  • [Changed] Directory for error detection of non-working redirects of images to WebP files
  • [Changed] Button for Server configuration tab
  • [Added] Information about error detection in Server configuration tab

1.4.2 (2020-08-24)

  • [Fixed] Cache-Control for redirects of images to WebP files
  • [Added] Error detection of cached redirects of images to WebP files

1.4.1 (2020-08-19)

  • [Changed] Error detection method on plugin settings page
  • [Added] Error detection of non-working redirects of images to WebP files

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