randompenguin

@hoergen Pages and Groups are just different types of Friendica accounts that are not People.

Seiten und Gruppen sind nur verschiedene Arten von Friendica-Konten, die keine Menschen sind. (Auto-übersetzt)

News Pages: dir.friendica.social/news
Org Pages: dir.friendica.social/organizat…
Public Groups: dir.friendica.social/group

@heluecht @capitan What's specifically bad about it is that there is no way to manage the files. If you accidentally upload the wrong video you can't delete it if you're a regular user. You'd have to ask the server admin to delete it for you. There's no way to set permissions on the files. It also has a tendency to fail on upload with larger files, even when they're under the file limit set by the server admin.

I spent a while digging through the code trying to add a button to the file browser so at least users could delete a file, and while I think the code to do that exists on the backend, I could never figure out how to access it and gave up.

@utzer I think I fixed it! The screenshots below are from the Release Candidate (2026.08-rc). One of the changes to masonry layout is that if there's an odd number of images the last one now spans both columns.

As I said, by the time the array of images was getting to the masonry layout they were already in the wrong order, even though they are still in the correct order in the stored post content. It's because the functions to get the images don't go by the post content, they do a relational database search of the "post-media" table looking for rows that match the post UID number. And that is how the array of images is constructed.

Except it isn't given any sorting parameters. I couldn't figure out what the default sorting actually is, but it should be in ascending order of media ID number - because that is the same as the order the attachments are in the post body content. So I simply added those sorting parameters to the database query and now the images are in the correct order.

I'll be submitting a PR for this tomorrow to fix it in the Release Candidate.

@utzer I don't know, I can't find any rhyme or reason for what order it puts things in.

Here is how my Dev Server running Friendica stable (2026.05) arranged them:

Which is different from the order you got for the same images.

And here is how my Dev Server running Friendica Release Candidate (2026.08-rc) arranged them:

But if I got to "Edit" either of those all of the images are attached in the correct upload order. If I preview it in the Release Candidate my jQuery masonry simulation shows them in the correct order.

If I purposely disable masonry layout to make it use "Grid" layout they are, again, displayed in the wrong order! This is because the "Post Media Collection" array used by either masonry or grid layout has already had the order altered before it ever gets there. I've traced it back through several other files and it's already in the wrong order.

As I said, I have no clue yet WHERE it is changing the order or WHY.

When the post is federated to another platform that other platform is working from the order the images are attached to the post body, which is not getting changed by Friendica. Like I said, if you go to edit it, if you quote share it, on Friendica the order will be correct. It's only be altered when it displays the published post in Friendica.

I'll keep poking around in the code and hopefully I can find and fix it, but right now I'm not sure where else to look.

@utzer I don't think it has anything to do with the original filenames, or for that matter the order you uploaded them. They are supposed to appear in the order you attach them to your post.

But that is not happening. If you go to edit the post you'll see they are attached in your preferred order, they just aren't getting displayed that way in Friendica. And it's not the masonry layout function that's changing the order. The "Post Media Collection" array is already re-ordered before it ever gets to the masonry layout code. It's actually getting changed somewhere before the PostMedia code too. But I can't figure out where the order is being changed or why.

In the Release Candidate I added code to the post composer preview to show the masonry layout, but it has to use jQuery on the frontend, not the actual masonry code from the backend. Ironically my "simulation" of the masonry layout for the preview shows the images in the correct order while, after publishing, the actual masonry code does not.

@utzer On my end it looks the same as your screencap:

So it's not just on your server, it's coming through to the one I'm on that way too.

The quote share in your post above, however, doesn't use the masonry layout and shows the images in a linear column in what you said was the upload order.