Bug report
maxitems counting in ContentRepository is incorrect in certain workspace/versioning scenarios.
Problem
When processing workspace-overlaid tt_content records, the current VersionState condition can evaluate incorrectly.
As a result, records that should be excluded (for example delete placeholders) may be counted, which makes the effective count too high.
Impact
- inconsistent
maxitems behavior
- editors can be blocked from adding/moving records although the visual state suggests capacity is still available
Expected behavior
Only valid records should be counted for maxitems evaluation; delete placeholders must not increase the count.
Fix
A minimal fix updates the VersionState comparison in Classes/Repository/ContentRepository.php.
PR: Link
Bug report
maxitemscounting inContentRepositoryis incorrect in certain workspace/versioning scenarios.Problem
When processing workspace-overlaid
tt_contentrecords, the currentVersionStatecondition can evaluate incorrectly.As a result, records that should be excluded (for example delete placeholders) may be counted, which makes the effective count too high.
Impact
maxitemsbehaviorExpected behavior
Only valid records should be counted for
maxitemsevaluation; delete placeholders must not increase the count.Fix
A minimal fix updates the
VersionStatecomparison inClasses/Repository/ContentRepository.php.PR: Link