I have a Plex server running on a VM with Linux Ubuntu. It picks up a network share to find media. In particular, I have a bunch of photos organized like this:
The base directory is a single library in Plex.
Base directory: /media/6tb_share/Pictures
YYYY-MM Vacation #1 Name
* Day 1
* Photo 1
* Photo 2
* Photo 3
* Day 2
* Photo 1
* Photo 2
* Photo 3
* Day 3
* Photo 1
* Photo 2
* Photo 3
* etc.
YYYY-MM Vacation #2 Name
* Day 1
* Day 2
* Day 3
* etc.
YYYY-MM Vacation #3 Name
* Day 1
* Day 2
* Day 3
* etc.
etc.
I had expected the top-level to show a folder for each vacation, and then subfolders for each day, and then photos inside each day.
What actually happened is much weirder. Sometimes that happened. For example, we have a directory with two subdirectories, and they both navigate exactly as expected.
But other times i puts the “day” directories at the top-level in the library.
And other times it puts individual photos at the top level in the library.
I’ve tried deleting and re-adding the library. I’ve also tried removing the vacation directories that are not working as expecting and re-adding. Neither seems to fix it.
The really frustrating issue is the inconsistency. If it was consistently odd then I might be able to find a work-around, but there doesn’t seem to be much logic to it.
I consider there’s a set of rules for media preparation same as for movies etc. – however apparently that description is currently not documented in Plex’ support section.
Usually Plex isn’t just following your folder structure but attempts to organize things logically based on metadata / tags etc.
I’ve just noticed this had happened to my collection where all my folders are at the to level as well. I’ll check what version of the server in running on Ubuntu later, but I only updated it the other day
Running plex server 1.10.1.4602
On Android 6.11.2.3107 the photos are a mess, and the options are to order by Timeline, Albums or Folders
On Windows PMP 3.20.6 or via the Web it looks fine but I can order by Photos, Timeline or Albums
So it looks like a problem with the Android app for me (It used to be fine)