@AYAPOV: How did you do the breadcrumbs in your current pages? Manually?
The problem here is that X3 can't really get "labels" from all directories in the path. For example, if you have /pathA/pathB/pathC/pathD/, X3 would have to loop through all those directories, load page.json, get label, repeat. Instead, we will need to depend on the actual folder names to create breadcrumb links. For example with the path noted above, breadcrumbs would be pathA > pathB > pathC > pathD. Simple and effective.AYAPOV wrote:For the future real releases, according to albums name lenghts, some thoughts. What if let user some entry field to give short names for breadcrumb purposes (Which may differ from original name, like Gallery name and Title name for the browsers top bar) plus set number of characters, above which original name will truncate to reasonable lenght
Assigning breadcrumbs per page
One might want to assign breadcrumbs for all subfolders inside a folder, but X3 cannot retrieve and inherit settings from parent folders (how far up the tree would it look anyway?). There would be main breadcrumbs plugin settings, where you can enable or disable breadcrumbs for all pages. And then there would be page-settings, where you enable/disable breadcrumbs on a per-page basis.
Plugins as content variable %breadcrumbs%
By default, breadcrumbs plugin would be able to display at very top of page, or at the bottom (above footer). If you want breadcrumbs inside the content (like in your case), I would need to prepare a content-variable %breadcrumbs% that converts into breadcrumbs in the page. Without this feature, it wouldn't be possible to just inject breadcrumbs at some unknown location on page.
Just some notes!