It’s best practice to debug or develop against the same content that is in production, but what should you do if there’s a limited amount of space to work with and the full production data can’t be pulled down? You can use Zope’s export/import.
The export/import process is most helpful when a client reports a bug within a particular section of the site. With this feature, the developer can export the section, load the content locally and debug it without “breaking” the production site. Plone docs also recommend using this process as a way to test that an add-on has been cleanly removed.
Because you can’t select multiple folders at a level to export them together, the exports should be done one folder at a time. When importing, the folder doesn’t need to be imported at the same location - it can be put anywhere in the local instance. After importing, don’t forget to update the catalog if it should be aware of the new content.
An important note: the sites that content is being exported and imported between need to be identical. If the local instance is on a different version of Plone, or missing add-ons that are in production, the file won’t be able to be imported. Six Feet Up uses buildout to manage the install across multiple instances and keep it consistent, but other tools such as Docker work for this as well.
portal_catalog
> Advanced tab > “Update Catalog” button. (A “Clear and Rebuild” may also be necessary.)