Skip to content
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

[BUG] After Upgrading a Site to 2sxc v19.03, Image Paste Fails for PNG Files #3566

Open
jeremy-farrance opened this issue Jan 27, 2025 · 2 comments
Assignees

Comments

@jeremy-farrance
Copy link

Bug Affects...

[x] edit experience / UI
[x] admin experience UI

Current Behavior / Expected Behavior

With the Patron feature enabled so you can paste images in the Edit UI, this feature stopped working in recent versions. Not sure when, but I noticed it right after upgrading from v18.6.1 to v19.3.0.

Things that still work:

  • I also tried downloading the image to a file on my local machine and then drag n drop. That worked. So this is specific to pasting an image from the copy (buffer).
  • I also tried the same thing as in the video, copied a JPG. That worked. So this is specific to PNG files.

To Reproduce (Steps, Videos, Screenshots, Apps)

I included a video to carefully demo the steps to see the problem.
https://accuraty-my.sharepoint.com/:v:/p/jfarrance/EX-rpwdWaw1LspX8r994KEsBL5_rkOfjBOHuc62cNnze-A?e=vHZeVU

The error makes it look like the problem might be ImageFlow, but that is not the case, instead, 2sxc is writing a 0 byte image as you can see here (multiple attempts shown:
Image

Your environment

  • 2sxc version(s): 19.03.00
  • Browser: all/any
  • DNN / Oqtane: Dnn 9.13.07 / have not tried Oqtane
  • Hosting platform: IIS
  • Ui Languages: any/all
@jeremy-farrance
Copy link
Author

jeremy-farrance commented Jan 27, 2025

UPDATE: I found another site running 2sxc v18.6.1 on DNN v9.13.07 with the Patron feature enabled, and the problem is on that version also. So its been like this since at least 18.6.1 and possibly earlier.

@iJungleboy
Copy link
Contributor

so it does need patrons enabled...
...but it does sound like something is broken, but I believe we didn't do any changes related to this.
we'll research, thanks for the report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

2 participants