Bulk selection by filter checks access one entry at a time

Open
#3,283 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
csharp

Research direction

Start with ContentService.Bulk.cs:160-183 and compare its per-entry CanAccessEntryAsync calls with AuthorizationEvaluator.AccessibleEntriesAsync. Trace how selected ids are paged and how access results are used before writes. Done means selecting a page uses a constant number of access queries; verify this with the relevant tests or query-count checks.

Written by the indexing model from the issue text.

Description

area:authorization area:content performance type:bug

Problem

ContentService.Bulk.cs:160-183 calls CanAccessEntryAsync for every selected entry (one or two queries each), up to about 11,000 round trips before any write, though AuthorizationEvaluator.AccessibleEntriesAsync checks a set at once.

Proposal

Check each page of ids with AccessibleEntriesAsync.

Acceptance

  • Selecting a page of entries runs a constant number of access queries

Found in the code review of 17 Nov 2026 (P4).

Dominant language
C#
Stars
569
Forks
107
Avg merge
2h 49m
Merged PRs (30d)
397

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fluentcms/FluentCMS

All issues in fluentcms/FluentCMS

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.