Weave Code
Content History Bundle Laravel Package
integrated/content-history-bundle
Integrated Content History Bundle adds revision tracking to Symfony content entities, automatically recording changes and giving editors a clear history view to compare and restore previous versions. Simplify auditing, rollback, and editorial workflows with minimal setup.
Integrated Content History Bundle
Frequently asked questions about Content History Bundle
- Is integrated/content-history-bundle compatible with Laravel?
- No. It is a Symfony bundle that assumes Symfony bundle registration, the service container, configuration trees, and likely Doctrine ORM entity lifecycle hooks. Laravel has no bundle concept and uses Eloquent observers rather than Doctrine listeners by default. Direct Composer adoption into a Laravel app is not feasible without a port or a service boundary.
- How do I install integrated/content-history-bundle with Composer?
- The provided context shows no Packagist presence, so you would likely add the Bitbucket repository as a Composer VCS source and require integrated/content-history-bundle from there. You would then register the bundle and configure it in a Symfony application. Confirm repository access, licensing, and a pinned commit before installing, because no releases or changelog are evident.
- Which Symfony and PHP versions does this content history bundle support?
- The provided context does not specify supported Symfony or PHP majors. Maintenance against current releases is also unverified, so treat version support as an open item. Audit composer.json and the bundle code, then test on your exact Symfony and PHP versions before planning adoption.
- Does the bundle require Doctrine ORM, and can I use it with Eloquent?
- The bundle is described as Doctrine-friendly and its design assumes Doctrine entity lifecycle hooks, so it likely hard-depends on Doctrine ORM or DBAL. Eloquent is not supported natively. Whether the Doctrine layer can be cleanly abstracted is unconfirmed, so a Laravel path would require a port or an API boundary around a Symfony service.
- How does the bundle capture revisions: entity listeners or explicit service calls?
- Symfony bundle conventions and Doctrine lifecycle hooks suggest entity listeners or event subscribers, but the context explicitly flags the capture mechanism as unclear. Read the subscriber or listener directory and DependencyInjection/Configuration.php to confirm. Do not assume automatic capture until you verify it in a proof of concept.
- What storage schema and data does the bundle use for revision history?
- The overview says it records versioned snapshots with timestamps and author metadata and uses configurable mappings without schema rewrites. The context does not confirm whether it stores full snapshots, diffs, or both. Inspect the entity and mapping directory to learn the actual history table shape, retention controls, and archival behavior.
- Can I restore or revert to a previous content version, and is the revert tracked?
- The overview claims diff and restore for previous content versions, so rollback is a stated feature. Whether a revert is recorded as a new revision is not stated and must be verified. Define who may revert and how reverts appear in history, then test restore behavior on non-critical content first.
- Does integrated/content-history-bundle have tests, releases, or Packagist support?
- The TPM assessment reports zero stars, zero dependents, no Packagist presence, and no evident releases, changelog, or test signal. That makes the source code the primary documentation. Ask the maintainer for test coverage and run it locally; missing public metadata is a high-risk signal, not proof that the bundle fails.
- What license and maintenance risks come with a Bitbucket-hosted bundle?
- The license is not stated in the provided context, so confirm that it permits forking and internal maintenance. Bitbucket hosting adds access, CI authentication, and long-term availability concerns that a public Packagist package would not raise. Pin commits and keep a fork or mirror if you adopt it.
- What are alternatives for revision tracking in Laravel or Symfony?
- For Laravel, build revision tracking with Eloquent observers, queued jobs, and migrations, or use a maintained Laravel audit package. In Symfony, evaluate maintained Doctrine revision or audit bundles with public releases and tests. Use this bundle as reference code if its snapshot and restore model fits, and compare retention, diff, and restore requirements before choosing.
Weaver
How can I help you explore Laravel packages today?