-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[xExtension-ImageProxy] Duplicate images in articles #206
Comments
I suspect you're talking about the same thing as FreshRSS/FreshRSS#4999 |
I investigated it a bit. Here are some insights, that roots are in ImageProxy extension:
(check it with the "show source" in your browser, not with the inspect tool) In the last new versions of FreshRSS a new feature was implemented that prevent showing duplicated images from the articles as attachment based on the image source. The imageProxy extension exchanges the If you manipulated
$img->setAttribute('data-proxy-src', $newSrc); than there are no duplicated images anymore and the data-proxy-src is set correctly.
(I do not have any solution for it right now) (P.S.: To have a better testing: enable the |
That's unavoidable. But it's supposed to do something like |
…d image In reply to <FreshRSS#206 (comment)>. With special thanks to this comment: <https://www.php.net/manual/en/domdocument.savehtml.php#119767>
…d image (#212) In reply to <#206 (comment)>. With special thanks to this comment: <https://www.php.net/manual/en/domdocument.savehtml.php#119767>
Have this problem as well. In the default FreshRSS release feed I get two avatar images: One from my proxy, and another directly linking to github. :/ |
Same here: double images, the original and the one from the proxy. |
With the proxy enabled, every article that has an image in it, has its first (or only) image duplicated, with the duplicate image being located at the end of the article, and checking the image URLs reveals the duplicate is at the end is the original non-proxied link, while all other images links are proxied.
The text was updated successfully, but these errors were encountered: