Bjoern

That’s way too much memory. Maybe there is a bug in reading the mo files (that’s when streams.php gets involved). Does this error happen while activating or after activation? And which plugins are installed?

Not yet, but I plan to implement more/better debugging and logging. I am currently restructuring the plugin internals which will (hopefully) make that easier to implement.

Cachify shoudln’t be the cause. It only caches front end pages. So if there would be any issues, it shouldn’t break the options page.

Is that bug reproducable? Does this always happen, when you follow the steps you describe?

What do you mean by “no load”? The Settings page doesn’t load (blank page?) or the images don’t load?

I remember you posted that. I can’t Image why that happend, especially why it worked after installing Regenerate Thumbnails. I hope this time everything works right from the start.

I’d say the image handling improvements are safe and you shouldn’t loose any images (you had problems with uploading Images on your other site, correct?). WPPP doesn’t alter or delete the original images.

I reworking some of the image code so uploads get handled another (better) way. Main reason (next to more elegant code and maybe improved plugin compatibility) is to keep dynamic image resizing working, when editing Images via media library. Right now this would generate intermediate images regardless of WPPP settings.

The back end is the admin area / dashboard. Front end is the site itself, what your visitors get to see.

Also, you have to compare the plugin runtime to core runtime before and after activating WPPP. Before activating, translation is done from WP core, when activated, WPPP takes over translating. So depending on the amount of translations there is much time spent in WPPP code.

And as already said, it would be helpful to see a detailed breakdown to tell more about the cause (especially real runtime, not only percentages).

I don’t think a special transients cache is needed. If you have a persistent object cache installed transients will already use that.

The next release of WPPP will feature CDN support for images. I’m working on that feature at the Moment and plan a first release this or next week.

The next “big” feature will be “selective plugin loading”. (Actually I had planed to implement that before the dynamic image resizing feature) Plugins to to that already exist, but they don’t work quite as I would like it to work.

Also on my to do list: Improved image handling for multisite and sites without pretty permalinks.

Apart from that suggestions for new features are always welcome – I know I turned down all your suggestions so far, but don’t let that keep you from comig up with other ones ??

I couldn’t reproduce that error here. Maybe some plugin conflicts. Any other (media related) plugins activated and if so, which ones? Or maybe I just tried it the wrong way. How did you upload the image(s), and how may?

This should be fixed in 1.6.6.

As far as I can tell it shouldn’t interfere with WPPP, as it is no object cache.

Improved Image handling didn’t do anything on multisite installations even before 1.6.1, it just didn’t tell you so. Though you could activate it, internally it wouldn’t get used. It doesn’t matter if you install it network wide or individual. Sorry.

But I’m going to try to implement dynamic image resizing for WPMU.

I’ll look into the AJAX Thumbnail Rebuild issue.

And it’s nice to hear you like the plugin ??

Please test version 1.6.5 if it fixes your issues.

Thanks, everything works fine now.

Integration of EWWW IO into WPPP is also almost finished. Required a bit more work, due to SHORTINIT startup.