• Resolved ptravassos

    (@ptravassos)


    Hi,
    In versions >= 1.6.0, I get an error:

    https://ibb.co/rbFSTJB

    Probably there was a change in the XMLHTTP request of the image in the main.js. Now, the request is not sending the access-control-allow-origin header. The main.js presented in the preview is from this plugin.

    Works great until, 1.5.0.

    Thank you.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Volkmar Kantor

    (@volkmar-kantor)

    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.

    Thread Starter ptravassos

    (@ptravassos)

    “Works great until, 1.5.0.”. Yes i manually installed the 1.5.0 to have it working correctly. The installation have de media stored on S3 and distributed with cloudflare. I said that because it’s an error that only apear from your v1.6+

    Thank you.

    Plugin Author Volkmar Kantor

    (@volkmar-kantor)

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

    Thread Starter ptravassos

    (@ptravassos)

    Adding the header solved the problem. If anyone found the same problem here is the link to add header on S3.

    https://repost.aws/knowledge-center/s3-configure-cors

    Thanks

    Plugin Author Volkmar Kantor

    (@volkmar-kantor)

    @ptravassos thank you for sharing.

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

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘XMLHTTP request (missing header on version >=1.6.0)’ is closed to new replies.