• Resolved orangedam

    (@orangedam)


    Hello,

    After upgrading to V4.3.6 images were not anymore loaded on my website.

    To fix this behavior I had to change the image loading from .htaccess to Pass Thru (and I had to convert some PNG files to JPEG in order to be displayed).

    Maybe something important happened, which could potentially cause bigger problems.

    My suggestion is to check.

    Regards,

    Orangedam

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Mateusz Gbiorczyk

    (@mateuszgbiorczyk)

    Hello @orangedam,

    Thanks for your message.

    What version of the plugin are you using before? What exactly happened after the update?

    Best,
    Mateusz

    Thread Starter orangedam

    (@orangedam)

    Hello Mateusz,

    First of all, thansk for your fast answer. Very professional.

    I’ve enabled the automatic update of the plugin, so it keeps up to date by itself.

    Looking more carefully at the version releases (dates and update contents), I think that the issue could have happened when the V4.3.5 has been updated (just one day before the V4.3.6 and that V4.3.5 it includes modification in access mode with .htaccess)

    The behavior is simple: all the images, intstead to be loaded, jost thow the small icon which indicate the unavailability of the image itself.

    I’ve also tried to show some image just using a direct url to it (i.e. https://www.xxxxx.com/wp-content/uploads/2022/05/image.jpg), and in that case I got a generic 500 error. The logfile was not of any help, and I had to involve the ISP because I can’t see all the Apache logs.

    Hope this helps you.

    Regards,

    Orangedam

    • This reply was modified 2 years, 9 months ago by orangedam.
    Plugin Author Mateusz Gbiorczyk

    (@mateuszgbiorczyk)

    @orangedam Can you send me the contents of the following files while error 500 occurs?
    – /wp-content/.htaccess
    – /wp-content/uploads/.htaccess
    – /wp-content/uploads-webpc/.htaccess

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Strange behavior after updating to 4.3.6’ is closed to new replies.