Weave Code
Ezloremipsumbundle Laravel Package
kaliop/ezloremipsumbundle
KaliopEzLoremIpsumBundle is a Symfony/eZ Publish bundle that adds lorem ipsum generation tools for eZ content, helping developers create placeholder text and sample content quickly during development and testing.
A bundle for eZPublish5 / eZPlatform dedicated to mass-creation of sample/test content
Frequently asked questions about Ezloremipsumbundle
- Is kaliop/ezloremipsumbundle a Laravel package?
- No. It is a Symfony bundle built for eZ Publish 5 and eZ Platform (now Ibexa DXP), not a Laravel package. It integrates through the eZ kernel, content service, and Symfony dependency injection container, none of which exist in a Laravel application. There is no service provider, facade, config publish step, or Artisan surface.
- How do I install kaliop/ezloremipsumbundle with Composer?
- Install it with Composer inside an eZ Publish 5 or eZ Platform project, then register the bundle in your Symfony/eZ kernel. Version 1.6.0 replaces the abandoned fzaninotto/faker with fakerphp/faker 1.9.1 or newer, which removes the most likely install-time blocker. It also declares compatibility with eZMigrationBundle 5.13 or newer, so that bundle and its constraints must be satisfied too. Expect pinning conflicts if your project uses a modern Composer dependency set.
- Does it provide an Artisan command or Laravel service provider?
- No. The package exposes a Symfony console command that runs inside the eZ Publish/eZ Platform kernel, not an Artisan command. There is no Laravel service provider, facade, configuration publish tag, or package discovery support. In a Laravel app the Composer install would not create any usable integration surface.
- Which Laravel versions does it support?
- None. The package targets eZ Publish 5 and eZ Platform, and its dependencies such as eZMigrationBundle 5.13+ have no Laravel analogue. There is no tested or claimed Laravel version range in the release. Treat any Laravel version support statement as inapplicable.
- How do I generate lorem ipsum content for eZ Publish or eZ Platform?
- Use the bundle's Symfony console command to create Lorem Ipsum content objects under a chosen parent location. It produces realistic titles and body text so theme, template, and presentation testing can run against a populated site structure. The command is repeatable, which helps rebuild local and staging environments without manual data entry. You configure content volume and targets before running it from the CLI.
- Can I target specific content types, parent locations, and languages?
- Yes. The bundle is designed to generate configurable volumes of dummy content and lets you target content types, parent locations, and languages. That makes it practical for populating a specific section of a site structure rather than filling the whole tree. Configuration is done in the eZ/Symfony context, not through Laravel config files.
- Is it compatible with Ibexa DXP 4.x and PHP 8.1 or later?
- That is unverified. Version 1.6.0 modernizes Faker and adds GitHub Actions CI, but the headline compatibility statement targets eZMigrationBundle 5.13+ rather than Ibexa 4.x. The PHPUnit 5.x/8.x references suggest a legacy PHP test matrix around PHP 5.6 to 7.x, so CI presence should not be read as PHP 8.1+ validation. Check the exact composer.json constraints and the CI matrix before assuming Ibexa 4 readiness.
- Is kaliop/ezloremipsumbundle still maintained?
- It shows low-activity, single-vendor signs of life rather than a steady maintenance cadence. Version 1.6.0 landed after a multi-year gap with a Faker migration, CI, a master-to-main branch rename, and a PHPUnit bump, which is a positive signal. However, the repository still has 0 stars and 0 dependents, so long-term support is not guaranteed. Budget for forking or freezing dependencies if you adopt it.
- What should Laravel developers use instead for demo content?
- Use Faker with Laravel model factories and seeders, or database seeding with dedicated fixture classes. That stays inside Laravel's own tooling, respects your Eloquent models, and avoids pulling in eZ/Symfony dependencies. Reimplementing mass fixture generation is measured in days of work, but it is the economically sane path for a Laravel stack. The eZ bundle offers no reusable Laravel components.
- Is it safe to run in production, and what license applies?
- The package has a destructive content-generation capability and version 1.6.0 ships no environment guard, so restrict it to local, CI, and staging environments. Running it against production data risks creating unwanted objects or altering site structure. The license is GPL-2.0 copyleft, which is fine for internal use but a real constraint if you fork it into anything distributed.
Weaver
How can I help you explore Laravel packages today?