Accusoft

Seems like a good idea. We’ll add this to our backlog and see if we can get it included. Maybe make the request of nextgen to include us in their plugin?

Thanks for your feedback.

Tom

We’ll look at adding the ability to reprocess with a different setting like you describe. Thanks for the feedback.

Tom

By design, bulk processing does not retry any images that have already been reduced. You can force reprocessing for an individual image by clicking on “Rerun Prizm Image” for each image shown in the media library.

Stephen

It appears to me that WordPress adds the dash when uploading media. If I go to the Upload New Media page and select a file that has a space in the name, when the file is saved to the wordpress\wp-content\uploads directory, the filename has the space replaced by a dash. However, on the Media Library page, the name contains a space.

In my testing, Prizm Image handles this situation fine. It successfully processes an image that has a space in the name on the Media Library page, but has a dash in the actual file name.

In your case, does the file on disk have a space or dash in the file name?

Stephen

Regarding the error message “Could not find /home/*****/public_html/wp-content/uploads/2013/03/business-final.jpg”. This message will occur if the image does not exist in your wordpress content area. In this specific case, it appears that the file business-final.jpg does not exist in the folder /home/*****/public_html/wp-content/uploads/2013/03/. The plugin does not delete files. Have you somehow deleted this file? Did you check to see if it is present in the specified folder?

Regarding the error message: “An unexpected PICTools error was returned from the PICTools libraries.” This is an error message returned by PrizmImage, but it is clearly not helpful. We will be improving the error messages to provide more helpful information. This particular messages means that this specific image could not be reduced further.

Thanks for your feedback,

Stephen

We have not seen this problem in our testing. We will continue testing to see if we can recreate this situation. Thanks for reporting it to us.

Stephen

Hello,

Yes you are correct that we recently released a new version of our service that requires use of a new API. This new API requires you to obtain a license key to use the service. Support for this was added in Version 2.0 of the plugin. I assume you are using the latest version of the plugin, but if not, please make sure to get the latest version.

Could you please provide the link that is giving you an error page. Also, where in the plugin or on our see do you see this link that is causing the problem.

The correct link to obtain a license key is: https://www.prizmimage.com/Home/Login

Thanks,

Stephen

Hi Jezweb,

As the product owner, I do feel comfortable sharing some of our thoughts on this. We are currently experimenting with this market and trying to understand the needs (is image compression a real, valuable need for the WordPress community? Sure seems to be judging by the interest we’ve seen). We don’t know exactly what we will do, as we are still learning about the market. But it may involve some kind of premium model for features or unlimited volume or some other way to differentiate the free service.

Would love to hear some feedback from you and other users.

Best regards,

Tom

Hello Nicolas P.

We have not seen this error before. Is this still happening for you?

Thanks,

Stephen

Hi jezweb,

When you stay “stuck” do you mean that a response is never received for a given image and no further images are processed?

Does it always happen on the same image or the same type of image (jpeg, png, or gif)?

Thanks,

Stephen

Hi jezweb

Yes, the same key can be used for multiple sites.

As you can probably guess, we don’t typically discuss future product direction in public settings. But we certainly appreciate your interest.

Thanks,

Stephen

Hello jezweb,

As you have noticed, if the browser page is closed or the connection drops, then bulk compression will not keep running. The next time you run bulk compression, it knows which images have already been compressed and will not reprocess them. Effectively, it will start where it left off.

Thanks,

Stephen

Hello jezweb,

As you have noticed, if the browser page is closed or the connection drops, then bulk compression will not keep running. The next time you run bulk compression, it knows which images have already been compressed and will not reprocess them. Effectively, it will start where it left off.

Thanks,

Stephen

Hello jezweb,

You can certainly increase the timeout to any value that you wish. 600 seconds is not too long, but if a single operation is taking that long, there may be a problem with the file that is taking that long.

Thanks,

Stephen

Marking this problem as resolved.