Bjoern

I’ve just released version 2.3. This version lets you use the internal 404 handler of WordPress as method to create intermediate image sizes. This method is a bit slower, but it should work “out of the box” with IIS without adding any rewrite rules.

I’m marking this issue as resolved, so if you test the new method and any issues occur please start a new topic.

Please try version 2.2.6. This should fix your problem if the cause was what I suspected it to be.

Do you have access to the server logs? The cause might be the test for native gettext support. I’ll try to improve the error handling but to be sure the error logs would help.

2.2.5 is now available and should fix this.

You are absolutely right. Don’t known how the PLURAL_SEP slipped in as it doesn’t make any sense to use it there. Luckily it doesn’t break anything, except for the notice. I’ll fix this with the next update.

That will be the reason it is not working. Currently WPPP only supports htaccess files. I’ll look into that. Try to use the following rule to make ist work (I couldn’t test it, so I don’t know if it will word. Have to set up an IIS test environment first):

<rule name="WordPress:WPPP" stopProcessing="true">
  <match url="^(.*)-([0-9]+)x([0-9]+)?\.((?i)jpeg|jpg|png|gif)"  />
  <conditions>
    <add input="{REQUEST_FILENAME}" matchType="IsFile" ignoreCase="false" negate="true" />
  </conditions>
  <action type="Rewrite" url="//test/wp-content/plugins/wp-performance-pack/modules/dynamic_images/serve-dynamic-images.php"  appendQueryString="true" />
</rule>

Do you get any errors displayed when you enter the URL of an intermediate image directly into your browser? Are any errors logged in the webservers error logs?

Hi wimsjohn,

the bug is found and fixed in version 2.2.4.

Before WPPP saves an intermediate image it test whether the image is a valid attachment (in order to update attachment meta data if necessary and also to prevent misusing of WPPP). This tests didn’t account for scaled images which caused the image to get created but not saved. I’ll have to check if this can also occur with other editing of images within WordPress.

P.S.: Your support is much appreciated. I’ll use it to treat myself with some fine craft beer. Cheers und viele Grü?e von der Küste in die Berge.

Should also be fixed in version 2.2.4

Forgot to mark as resolved…

Hi Luca,

rewrite rules now get deleted when disabling WPPP. Update to version 2.2.4.
And it’s nice knowing the work is appreciated ?? Also it’s great to get feedback, even about bugs as most will just dismiss a plugin as bad if they encounter an error without making the effort of posting a bug report.

I checked and found the cause. I’ll fix it with the next version. For now you can just comment out line 332 in wp-performance-pack/modules/dynamic_images/class.wppp_server_image.php
(it says
$this->check_cache_headers();
which is calling apache request headers).

• This reply was modified 5 years, 1 month ago by Bjoern.

Hi and thanks for the hint. Testing and reworking disabling and uninstalling WPPP are already on my todo list as I already know of some issues. I’m adding rewrite rules to it. I’ll look into it and hope to add the fixes in the next release.

So the basic issue with WebP is, that it generates .htaccess files in subdirectories thus overriding WPPPs rewrite rules. So accessing a not existing image size no longer redirects to WPPPs dynamic image creation routine.

Version 2.2.3 includes the option to add “RewriteOptions InheritDownBefore” to the rewrite rules wich basically forces all .htaccess files in subdirectories to also use WPPPs rewrite rules. So when enabled the first access to an intermediate image size, that doesn’t exist, will be redirected to WPPP and all subsequent request will be handled by WebP Express.

You can’t use WPPPs option to save intermediate images into a different folder than the original, because then WebP Express won’t find the original.

BTW: Now that I’ve seen how its done, I’m considering to add creation of intermediate images in WebP format directly into WPPP, including dynamic redirection for browsers not supporting WebP. Kind of a “WebP Express Lite”, as I would only integrate conversion using GD or Imagick.

Hi,

maybe the rewrite rules weren’t set correctly. Opening the permalink settings will force WordPress to regenerate them. Also the just released version 2.2.3 contains some fixes with writing rewrite rules.