- Is piszczek/pimcore-fixtures-bundle a Laravel package or a Symfony bundle?
- Despite being listed among PHP packages, piszczek/pimcore-fixtures-bundle is a Symfony bundle built for Pimcore, not Laravel. Pimcore itself runs on Symfony, so this package has no place in a Laravel application. If you are working in Laravel, you want a purpose-built seeder instead.
- How do I install piszczek/pimcore-fixtures-bundle in Pimcore?
- Install it as a dev dependency with composer require --dev piszczek/pimcore-fixtures-bundle, then register the bundle in config/bundles.php (or AppKernel.php on older Pimcore) under dev and test only. After that you load fixtures through Pimcore's console using the Doctrine fixtures command. Keep it out of production environments.
- Which Pimcore and Symfony versions does pimcore-fixtures-bundle support?
- The repository does not publish a compatibility matrix, so Pimcore major, Symfony major and PHP minor support is only implied. Check composer.json constraints and confirm with a short, time-boxed spike against your exact pinned versions before adoption. With no CI or release cadence, do not assume compatibility from documentation.
- How do I run fixture loading from the Pimcore console?
- It follows Doctrine Data Fixtures conventions, so you load fixtures with the doctrine:fixtures:load console command. Fixture classes can be grouped and ordered, and you can load them individually or as ordered sets. This lets you seed Pimcore content reproducibly instead of entering it by hand in the admin UI.
- Can I create Pimcore DataObjects, documents and assets with fixtures?
- Yes, fixture classes are written in code and can create Pimcore objects, documents and assets, and they are versioned with your project. The bundle is designed for demos, tests and repeatable environment setup. Complex cases such as binaries, relations and localized fields still need to be validated in your own spike.
- Does loading fixtures wipe existing Pimcore content?
- The bundle is designed to append data to existing Pimcore installations without wiping content. That makes it useful for incremental seeding on a working dev environment. Still, test idempotency and element path or ID collisions on a copy before running it against anything you care about.
- Is it safe to run Pimcore fixtures in production?
- No. It is scoped to development and test, so register it only under dev/test and gate invocation behind a kernel.environment check. Fixture content must never leak into staging or production trees. The lack of a security response process and the single-maintainer bus factor make production use a non-starter.
- Does pimcore-fixtures-bundle support relations, localized fields and field collections?
- The README does not document handling for relations, localized fields, field collections, classification stores or asset binaries. Fixtures necessarily touch Pimcore internals such as element save semantics, versioning and indexing, which are the most volatile surfaces across upgrades. Treat these areas as unverified and prove them in a time-boxed spike.
- Is piszczek/pimcore-fixtures-bundle maintained and tested?
- The package has 0 stars, 0 dependents, no CI and a bus factor of one, so assume no upstream fixes or support channel. There is no test suite described in the repository, and fixture tooling tends to fail quietly with partial loads or orphaned elements. You inherit the debugging.
- What license does pimcore-fixtures-bundle use and can I fork it for in-house use?
- The license is not stated in the provided context, so check the repository LICENSE file before it enters your lockfile. Confirm that the license permits vendoring or forking, because with zero dependents nobody else has vetted the supply chain. If it is a thin wrapper over doctrine/data-fixtures, a bounded in-house implementation may be cheaper than adopting a 0-star dependency.