collective / collective/collective.exportimport

Component conversation_view not available when executing view export_content() from the Plone CLI

Open
#92 9 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
19
Forks
20
PR merge metrics
No merged PRs in 30d

Description

I hae a snippet of code that is supposed to export (and it works with all exports other than content), but when I try it _with content export_, I get a zero-bytes JSON file. This snippet of code runs as an entry point of my `bin/client` program.

Does anyone know what the problem with the export is?

Code: https://gist.github.com/Rudd-O/f46154c80eb9937ec387e2b460ebbe8b

EDIT:

Ultimately the goal is to be able to command an export of everything via the Plone CLI (`bin/client -c export.py`), primarily for (but not limited to) migration automation and testing. All other exports work correctly using this code — only the content one does not.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the content export with the linked gist through `bin/client -c export.py`, then compare it with the other exports that work. Trace the content-export entry point and the `conversation_view` lookup described in the issue. Done means the Plone CLI produces a non-empty JSON content export.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.