Sorry about Friday. I was getting frustrated, I know it doesn’t excuse my actions but there it is.
The source of my problem arises from the re-structuring of my blueprints.
Broken pages/album.yml
# TABS
tabs:
# TAB: Photos
tabPhotos:
label:
en: Photos
de: Photos
icon: image
# SECTIONS
sections:
# SECTION: Photos
photos:
type: fields
fields:
# images
images:
type: files
label:
en: Files
de: Files
template: photo
image:
cover: true
ratio: 5/4
info: "{{ file.dimensions }}"
layout: cards
min: 3
required: true
size: small
Working page/album.yml
# TABS
tabs:
# TAB: Photos
tabPhotos:
label:
en: Photos
de: Photos
icon: image
# SECTIONS
sections:
# images
images:
type: files
label:
en: Files
de: Files
template: photo
image:
cover: true
ratio: 5/4
info: "{{ file.dimensions }}"
layout: cards
min: 3
required: true
size: small
The problem was that files were ignoring the file blueprint and when saving an album, it would simply write the images in their order on the album.txt file and not store the sort order on the image.txt file.
After removing the section called photos that has a type of fields and making images the section with a type of files, everything works as expected.
If someone could shed some light on why / what’s wrong that would be great - I’m assuming I should be able to put type: files
in a section of type: fields
? If yes, i’m assuming that I should expect the same behaviour no matter where I put my type: files
whether it be it’s own section or nested in another one.