Shared fields lose updates across locales
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
Research direction
Start in ContentService.cs:727-781 to trace the If-Match check, then read ContentService.Publishing.cs:681-698 for how other locales are recomputed. Follow the shared-row version and publish-copy paths, and inspect the provider tests. Done when stale ETags return 412 after shared-field changes, publish skips a changed shared row, and tests pass on every provider.
Written by the indexing model from the issue text.
Description
Problem
If-Match is compared with the written locale's draft version only (ContentService.cs:727-781). When a save changes shared (non-localizable) fields, RecomputeOtherLocalesAsync (ContentService.Publishing.cs:681-698) recomputes the other locales' status but not their versions. Editor A saves en and changes price; editor B then PUTs fr with an ETag read earlier, which is still valid, and reverts price. Publish has the same gap: the shared copy is not conditional on the shared row being unchanged.
Proposal
Version the shared row and include it in the ETag, or bump every locale's draft version when shared fields change; make the publish copy conditional.
Acceptance
- A PUT in one locale with an ETag read before a shared-field change in another locale answers 412
- Publish does not copy a shared row changed since the publisher's read
- Tests on every provider
Found in the code review of 17 Nov 2026 (B2).
- Dominant language
- C#
- Stars
- 569
- Forks
- 107
- Avg merge
- 2h 49m
- Merged PRs (30d)
- 397
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fluentcms/FluentCMS
-
area:host area:operations type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:build security type:chore
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:sdk security type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:content security type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area:build type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
All issues in fluentcms/FluentCMS
Similar issues
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
microsoft/microsoft-ui-reactor#1567 ·
Maintainers usually reply within 1 day
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw-windows-node#2287 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
kind:ux needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
elsa-workflows/elsa-foundation#4742 ·
Maintainers usually reply within 1 day
-
priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
enhancement good first issue help wanted new-language
Difficulty 2/5 1-3 hours Newbie friendliness 82/100