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

Changing the size of an image doesn't update it upon saving. #3501

Open
ILikeOrangeJuice opened this issue Apr 1, 2024 · 1 comment
Open

Comments

@ILikeOrangeJuice
Copy link

Describe the issue

Basically if you insert an image (idk about local, I only used external ones from imgur), you adjust the image size, press save, click the image again, the size is what you typed in, but as soon as you update/post the post, the image is in a different format (I assume the original size), if you edit the post and check the image, it always resets the size of it to 1200w 350h, even tho the image is clearly not that size.

NamelessMC Version

2.1.0

To Reproduce

Create a new post
Insert image via link (or local idk about that one)
Adjust the size
save the image popup > click again to confirm the values are correct.
post your post
image is in different size (I believe in the original size)
edit post > check image >values will be 1200w 350h

Expected Behaviour

I expect it to work and resize the input image/link correctly.

Screenshots

Before changing: https://prnt.sc/cyhs8obKGOSE
Changed to the said values and pressing safe: https://prnt.sc/HJpNteaA5yd7
then it looks like this, which for sure is not the input size: https://prnt.sc/bUia8GYS8WCy
If I then edit the post again and check the image size it is back to 1200w and 350h https://prnt.sc/sq_y4uULa1ok

Additional Information

I could only pick 2.1.0 in version but it is Version 2.1.2.

@samerton
Copy link
Member

samerton commented Jun 8, 2024

I've not been able to reproduce this one either in the forum or on a custom page - the size is correctly saving for me (using latest development code). Perhaps it has been fixed since 2.1.2, meaning 2.2.0 will resolve this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants