plone / plone/plone.exportimport
readonly fields in schema are ignored during import
Open
Nobody has claimed this yet.
01 type: bug
- Dominant language
- Python
- Stars
- 2
- Forks
- 3
- Avg merge
- 21h 16m
- Merged PRs (30d)
- 1
Description
Describe the bug
When importing data, fields with readonly=True in schema will not be set.
Expected behavior
The importer should set the fields as they were in the old system.
Software (please complete the following information):
- OS: EndavourOS with 6.18 kernel
- Browser 145.0.7632.116 (Offizieller Build) (64-Bit)
- Plone Version 6.1.3
- Volto Version 19.0.0-alpha.19
- Plone REST API Version 9.15.3
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
Start by locating the importer entry point that handles schema fields, then trace how readonly=True fields are filtered during import. Compare the imported values with the old system’s data and add coverage showing that readonly fields are set as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100