@Luke, may I jump in here, as the described issue also still exists in another context - see this post - and the observations here might explain those issues.
Those movies are grouped manually (as they are in different folders) - and the (different) folders are NOT named the same, nor do the filenames share a common start. This seems to be an issue, I reproduced today with latest beta server version, that it is still the same - such movie version groups will not be properly displayed. After grouping two movies, in a Collectionsview, they will still show up with two separate entries, each showing a "2" in the number of contained versions.
Maybe you can reproduce by grouping two movies from different places and different directory names together to be able to reproduce the behaviour. I think due to the issues this also leads to the other issues (e.g. splitting not properly working) described in the mentioned post.
library of type 'movies'
Scan will both identify as the same (due to imdb id), afterwards mark them both and group them manually, then go to the collections view -> you should see what described above.
resulting XML is:
´╗┐<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<Overview>Die Geschichte der Franz├Âsin Marion, gespielt und produziert von Julie Delpy.</Overview>
<LocalTitle>2 Tage in... Filmreihe</LocalTitle>
<Studio>Temp├¬te Sous Un Cr├óne Productions</Studio>
<Studio>Senator Film Produktion</Studio>
<Studio>3L Filmproduktion GmbH</Studio>
<Studio>Polaris Film Productions & Finance</Studio>
I didn't look into the code, but is it possible, that the linked items (for the blie indicator) come from the DB, but the grouped display is taken from the namingconventions in the XML file? I think both should rely on the linked item configuration from DB - regardless of the naming of the file - otherwise the manual grouping will not work as intended!?