Bjoern

Image improvements can cause your website to slow down if you have deactivated the saving of intermediate images, as this causes the Images to be recreated at every request. If you want to use that option, you have to use either (a big) cache or a CDN to keep your site fast. Else just leave “don’t save intermediate images” turned off. Then the first visit to your site may seem slow, as images are created then. Subsequent visits should be fast again.

If it stays slow, let me know and I’ll have a look into it, while it is turned on.

I am very sorry the plugin broke your site. Using the “Restore static URLs” button in advanced view should fix your Problem or at least give hints as to why the automatic restore at plugin deactivation didn’t work.

Version 1.9 won’t do any changes to your posts content anymore. Using dynamic Image links with URL substitution (which caused your problem) is now optional and turned off by default.

Is it still slow or have you deactivaed the plugin / image improvements? I just visited your website and it didn’t seem to be very slow.

Sorry for the late reply. Your problem is caused by the dynamic image links feature. “Restore static URLs” in advanced view (or deactivating and reactivating the plugin) should fix this.

I’m about to release version 1.9 of WPPP which doesn’t alter post content by default anymore, so you won’t get this issue with the new version.

@khromov: You are absolutely right – hadn’t thought about it that way (also because I reused onld code for that feature). I’ll change the behaviour in the next release to completely dynamic as default with substitution for faster URL replacement as an optional feature.

What PHP version are you using? Might be a problem with a version older than 5.3, which is required for WPPP.

Error should be fixed in version 1.8.7.

I’ll try to fix that as fast as possible. How did it mess up your site? One workaround would be to use the manual URL restore via advanced view and then delete the plugin using ftp.

The reason is that yu are using a pre 5.3 version of PHP. This is being tested on activation, but while refactoring the code this usage of static must have slipped through and is now used before the version test.

I will fix that with the next release, but activation will then fail for you because the PHP requirements for WPPP aren’t met. When I finished reworking the code, I might change the behaviour so those parts of WPPP, which don’t require PHP 5.3 or later will work. But for now you would have to upgrade PHP. Sorry.

Thanks for the hint. Fixed in v1.8.6.

I just commited version 1.8.3 which includes multisite support for dynamic images. WPPP Needs to be network activated. Give it a try. Though it works fine with my test setup be careful trying it.

My plugin WPPP has gone a long way since I first added the dynamic image feature, so I just wanted to keep you updated:

I’m using (overriding) WP_Image_Editor so intermediate images won’t get created even if you edit them directly in WP (with Dynamic Image Resizer creation of intermediate images is suppressed only on upload). This also allows usage of image optimizers like EWWWIO.

Crop settings are no issue anymore. WPPP first checks if the requested (original) image exists in WPs database and then serves the requested size using the image meta data (not registered sizes don’t get served as a security feature to prevent unwanted creation of images).

Other new features include usage of EXIF thumbs, adjustable image quality, not saving intermediate images at all or using WP object cache or CDN for Images.

Any feedback is welcome.

I just tested it and the button work with JIT activated here. Maybe it’s another plugin that conflicts with JIT localize.

I don’t know about uWSGI Object Cache but WPPP should work with any object cache as it uses WPs Cache API. Which one would be the best depends on your hoster (e.g. if APC, Memcache or others are supported). File based object caches always work but don’t offer that much performance gain.

Sounds strange, but if you don’t need any translations, changing the default language is the best option. Though it would have been interesting to knwo what the cause was.