>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3619946. --> Reported by: [mably](https://www.drupal.org/user/3375160) Related to !321 >>> <p>A booker who ends up spread across rows in the section they asked for is shown two warnings at once:</p> <ul> <li>Your places are in another row now.</li> <li>Your places are in the same section, but not all in the same row.</li> </ul> <p>Both are true, and together they undercut each other. The first is written in the singular and reads as "the party moved, as a unit, into one other row", which is exactly what the second denies.</p> <h3>Where it comes from</h3> <p><code class="language-php">VenuePlacementProvider::place()</code> appends the two independently. The first, at the top of the message block, fires when <code class="language-php">array_diff_key($ends_in, $was_in)</code> is non-empty and the party was somewhere before. <code class="language-php">$was_in</code> and <code class="language-php">$ends_in</code> are sets keyed <code class="language-php">area:row</code>, so that condition asks only whether the party entered a row it was not in; it never asks how many rows the party ends up across. The second comes from <code class="language-php">SeatingCloseness::getMessage()</code> further down, and for <code class="language-php">SameArea</code> it is the plural "in the same section, but not all in the same row".</p> <p>So the route warning is phrased for the case where a party leaves one row for another, and it is emitted for the case where a party fans out over several.</p> <p>The same string is emitted a second time, from the consolidation path that returns a <code class="language-php">UnitAssignment</code> directly. That one cannot stack, because no closeness is computed there, so it is left alone.</p> <h3>Proposed</h3> <p>Gate the route warning on the party ending in a single row, so it is said only when "another row" is accurate. Where the party ends up across rows, <code class="language-php">SeatingCloseness</code> already reports where they are, and more precisely.</p> <p>The cost is that the "you were moved" signal is lost for a scattered party, which is the case a booker who has told a friend where to find them minds most. The alternative is a second string for that shape, and two warnings still stacked. Taking the gate on the grounds that "not all in the same row" already tells a booker their seating changed shape, which is the part they can act on.</p> <h3>Tests</h3> <p>Four tests in <code class="language-php">SeatTogetherTest</code> touch these strings and each sees exactly one of them: <code class="language-php">testThePartyIsToldWhenItEndsUpInAnotherRow</code> and <code class="language-php">testTheRePlaceThatMovesThePartySaysNothing</code> on the route side, <code class="language-php">testPartyAcrossRowsIsToldAboutRowsNotParts</code> and <code class="language-php">testTheRunsAreAsEvenAsTheHouseAllows</code> on the closeness side. None covers the overlap, which is why it went unnoticed. The fix wants a test that lands a party across rows in one section and asserts a single warning.</p> <p>AI-Generated: Yes (Claude Code was used to help draft this issue summary and to trace the two emitters. I reviewed it before posting; there is no code on this issue yet.)</p>