Weave Code
Revise Operation Laravel Package
backpack/revise-operation
Adds a Revise operation to Laravel Backpack CRUD list views, letting admins quickly edit a single field inline via a modal without opening the full edit form. Simple to configure and ideal for fast, focused updates.
Backpack Revise Operation adds version history to Laravel Backpack CRUD panels. It automatically stores changes to Eloquent models and gives admins a dedicated interface to review past revisions and restore an earlier version when needed—without leaving the admin panel.
- Automatic revision tracking for supported Eloquent models
- Revision history interface inside Backpack CRUD
- One-click restore to previous versions
- Simple setup and configuration
Frequently asked questions about Revise Operation
- What does backpack/revise-operation actually do?
- It is a thin UI layer for Laravel Backpack CRUD that adds a Revise action to your admin panel, letting admins create a new version of an existing entry while keeping the original record intact. Changes are made in a familiar Backpack form and saved as revisions by venturecraft/revisionable. It does not implement its own audit storage, queue, or schema beyond revisionable's revisions table.
- How do I install backpack/revise-operation in a Laravel app?
- Install it with Composer alongside venturecraft/revisionable, then publish and run revisionable's migration. Add RevisionableTrait to each Eloquent model you want audited, add the operation trait to your Backpack CRUD controller, and register a Revisions button in setupListOperation(). The wiring is small enough that a working vertical slice is typically achievable in under a day.
- Which Laravel and Backpack versions does backpack/revise-operation support?
- The package sits in the Backpack 3/4 era, and its real dependency risk is venturecraft/revisionable, which has historically lagged Laravel major releases. Backpack 5 and 6 changed operation and view conventions, so the operation view may need adjustment. Before committing, prove that your Backpack major, Laravel major, and PHP minor actually resolve and boot together, and treat that as a gate rather than a spike.
- Do I need venturecraft/revisionable installed to use this package?
- Yes. backpack/revise-operation is only a UI for the revision history that venturecraft/revisionable already records on your Eloquent models. You need revisionable's revisions table migrated and its trait added to the models under audit. Without that foundation the Revise action has nothing to read from or write to.
- Can I revert or restore an entry from a previous revision?
- You can restore a prior revision, but the semantics are coarse: a restore overwrites all audited fields, so it can silently clobber edits made after that revision unless you add your own guard. Restores do not fire model events or handle relations and pivots by default. If you need compliance-grade undo behavior, plan for additional checks on your side.
- Does backpack/revise-operation work with Laravel Nova or Filament?
- No. The package implements Backpack's Operation pattern as a trait on the CRUD controller, a button, and a view, so it is only portable inside a Backpack admin panel. If you are on Nova, Filament, or a hand-rolled admin, the value collapses to reading the revisionable API directly. It is a poor fit for API-only services or environments where admin is not Backpack.
- How does it store revisions and what happens if I rename a model attribute?
- All history storage is handled by venturecraft/revisionable, which saves full serialized attribute snapshots per save. That is verbose and brittle if you later rename or drop model attributes, since historical rows can fail to unserialize cleanly. Factor that into your schema planning if long-term audit retention matters.
- Who can view or restore revisions, and can I restrict access per field?
- Authorization is inherited from Backpack's permission layer, so whoever can access the operation can use it. There is no per-field or per-entity revision ACL out of the box, and no two-person rule or separate restore audit trail. If you need tighter controls, build them on top of Backpack's permission checks.
- Is backpack/revise-operation safe to run in production?
- The dominant risk is maintenance abandonment: zero stars, zero dependents, and a composite score of zero mean nobody is exercising this code against modern Laravel, so there is no upstream security patching. A Laravel or Backpack major upgrade becomes a fork-and-fix exercise on your side. Run it as a time-boxed pilot on one non-critical CRUD first, and promote it only if the version triad resolves cleanly and restore behaves.
- What are the alternatives if backpack/revise-operation does not fit?
- If you need broader framework support or active maintenance, owen-it/laravel-auditing is a common fallback for audit logging in Laravel. If you stay on Backpack, you can also consume the venturecraft/revisionable API directly and build your own Revise screen. Decide buy versus build based on whether your requirement is compliance-grade audit or operator convenience.
Weaver
How can I help you explore Laravel packages today?