-
Notifications
You must be signed in to change notification settings - Fork 8
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
Duplicate slug names cause sections to fail grid layout #4
Comments
@fkxr-dev thanks for reporting! I just push a new version |
I can have a look later this week and will let you know. One related thing I noticed in the interim of testing this (on 1.0.7) was that when magnified/opened in the full-screen viewer, the exif-rotated portrait shots come out as squashed to their ‘original’ unrotated aspect ratio, the thumbnails are fine.
Thanks for the quick fixes!
…On Mon, Jan 1, 2024, at 1:01 PM, Linghua Zhang wrote:
@fkxr-dev <https://github.com/fkxr-dev> thanks for reporting! I just push a new version `v.1.08` to add a guard logic. Could you please take a look at it? I did a big refactoring and hope it didn't break anything. 😆
—
Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BEV5R2P45Y2JAZNY74DMGUTYMKJSNAVCNFSM6AAAAABBHXE4XCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZTGI3TOMBYGU>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
@fkxr-dev thanks!
I see. Let me check it when I got time later. BTW did you try to clear both the cache (.foto folder) of foto and the cache of browser? |
On the latest code (pulled from main) I'm now getting (correctly):
The squashed images in the enlarged view also seem to be resolved now; tried on a few different browsers and they all seem happy. |
@fkxr-dev Nice! Thanks for checking! |
Here's a weird one, obviously a user error here but I ran into a problem where one of my sections would refuse to appear in a grid layout. All the images would appear full-width in a one-wide list, if that makes sense. I tracked it down to the problem being a duplicated slug identifier for two sections in my TOML, renaming one of them caused the issue to go away.
Naturally slugs ought to be unique and this is technically a user error, maybe some error reporting during building would be enough to address this already, but I figured it's worth reporting here nonetheless.
So the reproduction steps as far as I can tell are:
layout.minColumn
or more images to each sectionLet me know if you'd need any further information!
The text was updated successfully, but these errors were encountered: