Weave Code
Statamic Entries Export Laravel Package
roorda-ict/statamic-entries-export
A Statamic addon from Roorda ICT for exporting entries from the control panel. Select and filter entries, then download them as a spreadsheet for reporting, backups, or migration. Simple to configure and works with your existing collections.
Exports Statamic collection entries
Frequently asked questions about Statamic Entries Export
- What is roorda-ict/statamic-entries-export used for?
- It is a Statamic addon from Roorda ICT that exports collection entries from the Statamic control panel. You select and filter entries, then download them as a spreadsheet for reporting, backups, or migration. Because it is an addon rather than a standalone library, it only applies to projects that already run Statamic as the content layer on Laravel.
- Does this package support Statamic 5 and Laravel 11?
- Release 2.1.1 added explicit Statamic 5 support, and Statamic 5 runs on Laravel 11 with PHP 8.2 or newer, so that is effectively the package's target floor. Support for Statamic 4 is less clear, because it has not been confirmed whether 2.1.1 drops the older major or uses a constraint like ^4.0|^5.0. Check composer.json in your project before planning any upgrade.
- Can I use this addon in a plain Laravel app without Statamic?
- Most likely no. The package is described as a Statamic addon and its value is tied to the Statamic control panel and collection data model. Whether statamic/cms is a hard or optional dependency has not been verified in the current record, so treat it as out of scope for Laravel-only applications until composer.json confirms otherwise.
- How do I install roorda-ict/statamic-entries-export?
- Install it with Composer using composer require roorda-ict/statamic-entries-export. For a Statamic 5 build, pin the exact version 2.1.1 rather than floating a caret range, so a minor Statamic release cannot break you unexpectedly. Also confirm whether the addon publishes config, migrations, or assets, because that turns the upgrade from a pure Composer operation into a multi-step deployment.
- What format are the exported entries in?
- The package downloads entries as a spreadsheet, which suits reporting, backups, or migration work. The documentation reviewed here does not specify the exact file extension or delimiter used. Run a test export in a throwaway project to confirm the output before building downstream tooling around it.
- Can I filter which entries get exported?
- Yes. The addon lets you select and filter entries in the control panel before downloading them. The specific filter options are not documented in the material reviewed here. Test against your own collections to confirm the filters map to the fields you care about.
- Does version 2.1.1 still work with Statamic 4?
- That is unresolved. The 2.1.1 release is a patch that adds Statamic 5 support, and it is unclear whether the constraint is ^5.0 only or a disjunction that includes ^4.0. Do not assume patch-level safety: resolve the dependency against your existing Statamic 4 project and read composer.json before committing.
- Is this package safe to use in production?
- The main concerns are single-maintainer bus factor and version-pinning fragility rather than any known defect. There is also no primary data in the current record on test coverage, issue history, or release cadence, so the assessment is inferred from release-note behaviour. Pin an exact version and review the source before relying on it for anything critical.
- Does the package have tests and CI coverage?
- This has not been verified. The technical evaluation flags that no dependency manifest, test coverage signals, or CI configuration were available in the record. Before adoption, check the repository's CI workflow and whether it runs against both Statamic majors and the minimum supported PHP version.
- What are the alternatives for exporting Statamic entries?
- Generic options include a custom Artisan command or controller endpoint that queries entries and streams a CSV, or a spreadsheet package wired into a small control-panel action. The advantage of this addon is that the selection and filtering UI already exists in the control panel. If you need a very specific export schema or scheduled exports, a bespoke implementation may fit better.
Weaver
How can I help you explore Laravel packages today?