• Resolved fondanalys

    (@fondanalys)


    Hi

    After updating to 3.7.3 the pictures do not show up.
    After going back to version 3.7.2 fixed the problem.

    Br

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hi @fondanalys!

    I tried to replicate the issue but the images are displayed as expected on my test instances. Please try to clear the cache and check if the images reappear. If they don’t, could you please provide us the feed so we can take a better look at it?

    Thank you and have a nice day!

    I’m experiencing this same issue. Rolling back to 3.7.2 fixes the issue for me too.

    I’ve updated it again to 3.7.3 to demonstrate the issue here:
    https://www1.sunybroome.edu/feedzy-test/

    The feed on this page is pulling from
    https://news.sunybroome.edu/buzz/feed
    Which is a valid feed, and at the top of the sample page above I’ve included where the error could be coming from.

    The following characters are missing from the end of the style attribute in the span tag that displays the image:

    ‘);”

    (would probably be fine without the semi colon)

    When I use Safari’s inspector to add in those characters and a space before the following class attribute, it fixes it.

    Is this something that could be fixed in the plugin?

    Same problem here. No featured images due to corrupted URL. Reverting to 3.7.2 fixes the problem. All caches cleared.

    This is the feed being read:
    http://lpcwest.com/feed/?post_type=news

    In 3.7.3, it looks like the scraper is not recognizing the closing quote, so a bunch of other meta tags are being included in the URL.

    Best,
    Brian

    I need to roll mine back to 3.7.2 for the time being. This will “fix” the example I shared in my previous post, but I’ll leave the image with the highlighted code block on the sample page I shared.

    Plugin Support Vytis

    (@bvytis)

    Hi everyone,

    Thank you for reporting the issue and apologies for the inconvenience.

    Our development team already identified the issue and a fix will be included in the next release.

    Thank you for your patience.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.