[5.x]: Issue with “Last Edited By” column in Multi-Country Setup
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 3.6k
- Forks
- 705
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 134
Description
What happened?
Description
We’re experiencing an issue with how the “Last Edited By” column display in our multi-country Craft CMS setup.
- Our site uses a template duplicated across multiple countries.
- In the entry list view, the “Last Edited By” column shows the last editor globally, regardless of which country’s entry is being managed.
- This is causing confusion among our agents, since edits made in one country appear under other countries’ entries.
- As a temporary measure, we have disabled the “Last Edited By” columns, but ideally, we would like to display the correct, context-specific information instead of removing these column.
Questions:
- Is this expected behavior in Craft CMS when working with duplicated entries across multiple countries?
- Is there a way to filter or scope “Last Edited By” so they reflect only the relevant editors within that country/section?
- If not, is there any workaround or upcoming fix planned to address this?
We’d appreciate your guidance on how best to resolve this, as our team finds this information useful but currently misleading.
Steps to reproduce
Expected behavior
Actual behavior
Craft CMS version
Craft Pro 5.8.17
PHP version
8.2.27
Operating system and version
Linux 5.4.0-208-generic
Database type and version
MySQL 31
Image driver and version
GD 8.2.27
Installed plugins and versions
No response
Contributor 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.
Research direction
The report concerns the entry-list “Last Edited By” column in a multi-country setup; start by reproducing it with duplicated templates in Craft Pro 5.8.17 on PHP 8.2 and MySQL. Verify whether the displayed editor is scoped to the current country, then document the expected behavior and a reproducible fix or confirmed workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql, php
- Domain
- backend, localization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100