Volkmar Kantor

Hi, the plugin do NOT support any CDN out of the box. It provides plenty of hooks/actions so an interoperation with CDN-plugins is possible if anyone is willing to code a connector. For example, if the new crop is saved, an CDN-plugin may use the action crop_thumbnails_after_save_new_thumb
to implement custom code to upload the new image to S3.

If you are a programmer, you may have a look on the hooks/actions that are documented on the github-page of the plugin. https://github.com/vollyimnetz/crop-thumbnails

Hi, i am sorry about you Problem but i guess i cant help with this one. Seem you have an more complex server setup.

Thinks that might cause the problem:

• the usage of cloudeflare
• a custom server side routing
• a wrong cross-origin setting

This problem ist caused by a security policy that all browsers have to follow.
An image from your subdomain has to send a header when it is requested from your main page in order to work properly (as the image is processed by Javascript).

The images from your subdomain have to send an “access-control-allow-origin” header with your main domain. This can be done i.e. with an rule in your .htaccess file (if you are using the apache webserver).

• This reply was modified 1 year, 9 months ago by Volkmar Kantor.

Cropping an image which is to small is possible with the plugin (but there is an warning as the image will be scaled up).

WordPress itself does not support crop on initial upload if the image is to small (and the plugin will not fix this as this is in the realm of wordpress).

@ptravassos thank you for sharing.

I will have a look if this may be possible in the future without setting the header.

The plugin do generally do not support CDN usecases.
Where did you get the error – php or js?

Then you should add the access-control-allow-origin header on S3 i guess.

@vixperth thank you for reporting. Will be fixed in 1.7.2 – please test.

There was no change in the way the images or data are requested. But the image is now loaded into an canvas element. That may cause this issue.
To make sure this is the issue, can you please manual download and install the version 1.5.0 on your current installation? If this is not the problem, than the error would be visible also in 1.5.0.

Beside, if you have an access-control-allow-origin error message you try to load an image from another domain/subdomain than the admin-page you run the script/plugin on. There should be no difference as this is a sign of an incorrect or customized installed wordpress. You may also add the access-controll-allow-origin header for your images with the help of ie. an htaccess file.

Should be fixed in 1.7.1 – let me know if its working.

Hi there, thank you for reporting – i will have a look on that problem. Sorry for the inconvenience.

After i posted the comment i got something working – has to refinded and tested though.

Hi @takuyoshi,

sorry i didn’t even know that the old crop library had keyboard functionality. Today i tried to make something happen, but the new crop-library i used in the plugin did not support this out of the box and may also have an error in these regard.

This has to be some kind of plugin incompatibility. To check what causes the problem:

• deactivate all plugins and use the standard theme
• reactivate the plugins one by one and check what causes the problem
• reactivate your theme

Please review with the current version. I have improved quite a lot of things that may have caused this issue.