Piwigo 16 adds two new derivatives: 3xlarge and 4xlarge. The pwg.images.getIngo API method returned their dimensions as strings instead of integers. Here is an excerpt of the returned JSON:
If you go on page [Administration > Configuration > Options > tab Photo Sizes], change anything and save, is it still strings?
(I'm trying to understand when the width/height become integers instead of strings)
Is it a new install or on an updated install (from 15.x or earlier, when 3XL/4XL did not exist)
I don't have that on my test install.
If you go on page [Administration > Configuration > Options > tab Photo Sizes], change anything and save, is it still strings?
(I'm trying to understand when the width/height become integers instead of strings)
Is it a new install or on an updated install (from 15.x or earlier, when 3XL/4XL did not exist)
<!-- github-comment-id:3654731929 -->
I went on the admin page, changed the image quality to 90% and saved => still strings for 3XL/4XL.
I then enabled the crop option of 4XL, saved => still strings for 3XL/4XL.
I then disabled 4XL, saved => still strings for 3XL/4XL.
I then called pwg.images.getInfo for another image ID => integer for 3XL/4XL
I then called pwg.images.getInfo for the previous image ID => back to strings for 3XL/4XL.
I have used the database of a 15.7 site when I installed the 16.0RC3 version (database updated at first launch). I then updated it to 16.0 and then 16.1.
- I went on the admin page, changed the image quality to 90% and saved => still strings for 3XL/4XL.
- I then enabled the crop option of 4XL, saved => still strings for 3XL/4XL.
- I then disabled 4XL, saved => still strings for 3XL/4XL.
- I then called `pwg.images.getInfo` for another image ID => integer for 3XL/4XL
- I then called `pwg.images.getInfo` for the previous image ID => back to strings for 3XL/4XL.
I have used the database of a 15.7 site when I installed the 16.0RC3 version (database updated at first launch). I then updated it to 16.0 and then 16.1.
<!-- github-comment-id:3657816140 -->
OK, we can reproduce the problem. When the size is bigger than your original photo, then the URL is the original and you have strings for width/height. We can reproduce this bug on Piwigo 15. Nothing new in version 16. It's just more visible because 3XL and 4XL are really big and more often bigger than original photos.
OK, we can reproduce the problem. When the size is bigger than your original photo, then the URL is the original and you have strings for width/height. We can reproduce this bug on Piwigo 15. Nothing new in version 16. It's just more visible because 3XL and 4XL are really big and more often bigger than original photos.
<!-- github-comment-id:3681472990 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Piwigo 16 adds two new derivatives:
3xlargeand4xlarge. Thepwg.images.getIngoAPI method returned their dimensions as strings instead of integers. Here is an excerpt of the returned JSON:I don't have that on my test install.
If you go on page [Administration > Configuration > Options > tab Photo Sizes], change anything and save, is it still strings?
(I'm trying to understand when the width/height become integers instead of strings)
Is it a new install or on an updated install (from 15.x or earlier, when 3XL/4XL did not exist)
pwg.images.getInfofor another image ID => integer for 3XL/4XLpwg.images.getInfofor the previous image ID => back to strings for 3XL/4XL.I have used the database of a 15.7 site when I installed the 16.0RC3 version (database updated at first launch). I then updated it to 16.0 and then 16.1.
OK, we can reproduce the problem. When the size is bigger than your original photo, then the URL is the original and you have strings for width/height. We can reproduce this bug on Piwigo 15. Nothing new in version 16. It's just more visible because 3XL and 4XL are really big and more often bigger than original photos.