Weave Code
Filament Locksmith Laravel Package
discoverydesign/filament-locksmith
Filament Locksmith adds record locking to Filament resources, letting admins lock sensitive records to prevent edits or deletions. It provides lock and unlock actions, clear lock-status indicators, and configurable enforcement so teams can protect critical data from accidental changes.
🔒 Passwords inputs made easy in Filament PHP 🤫
Frequently asked questions about Filament Locksmith
- What does discoverydesign/filament-locksmith actually do?
- It is a Filament plugin that adds record locking to your Filament resources, so admins can lock sensitive records and prevent them from being edited or deleted. It ships lock and unlock actions plus clear lock-status indicators in the panel UI. Enforcement is configurable, which lets teams protect critical data from accidental changes without writing custom policies for every resource.
- How do I install filament-locksmith in a Laravel application?
- Install it with Composer using composer require discoverydesign/filament-locksmith. The package is a standard Laravel package with service provider auto-discovery, so no manual provider registration is normally needed. Publish its config and any publishable assets if the package provides them, then clear cached config, views, and component manifests before testing the panel.
- How do I register the Locksmith plugin in a Filament panel?
- It is a panel-level Filament plugin, so you register it inside your panel provider alongside your other plugins. Existing panel registration and plugin configuration typically carry over unchanged when moving between major versions of the plugin. After registering, clear cached panel and component manifests so Filament picks up the new plugin.
- Does filament-locksmith 2.x require Filament V4?
- Yes, version 2.0.0 is a compatibility release that targets Filament V4, so the package's supported surface is pinned to that host major. The previous major line corresponds to Filament V3. Treat the upgrade as a paired move: Filament V4 plus plugin 2.x, not the plugin in isolation.
- Can I use filament-locksmith on a Filament V3 panel?
- You should stay on the 1.x line while your application remains on Filament V3, because the 2.0.0 constraint will not resolve against the older host major. The plugin cannot lead your Filament upgrade; it has to follow it. Confirm with the maintainer whether the 1.x branch is still maintained and receiving fixes before you rely on it long term.
- Is the lock enforcement configurable?
- Yes, enforcement is configurable so you can decide how strictly locked records are protected against edits and deletions. Configuration lives in the package config file, which you publish into your application. Review the lock-status indicator and action visibility settings so the behaviour matches your team's workflow.
- Which Laravel, PHP, and Livewire versions does version 2.0.0 support?
- The 2.0.0 release notes are minimal, so the exact PHP, Laravel, Filament, and Livewire constraints should be read directly from the package's composer.json before adoption. Check those constraints against your application and your other Filament plugins to avoid a split where two plugins in the same panel require incompatible Filament majors. Livewire version coupling is a common source of Filament upgrade problems, so verify it explicitly.
- What breaking changes are in filament-locksmith 2.0.0?
- The release is described as a compatibility bump for Filament V4 rather than a feature release, so the primary breaking change is the host major requirement. Because the changelog is a single line, it is unclear whether the port also changed rendering or action wiring. Check the published assets and config, republish anything that changed, and smoke-test every panel after upgrading.
- How should I upgrade from 1.x to 2.x in a Filament V4 migration?
- Treat it as one upgrade rather than two: bump Filament to V4 across the application and all Filament plugins together, then resolve the full plugin set to V4-compatible majors, which puts this package on ^2.0. After that, republish config and assets if the publishable set changed, clear cached panels, components, and views, and rebuild. Finally, smoke-test each panel to confirm lock and unlock actions behave as expected.
- Is filament-locksmith well tested and actively maintained?
- The repository does not publicly document its test coverage or the Filament V4 matrix in CI, and a one-line changelog on a major tag is a weak signal for a package that runs inside production admin panels. Before adopting, check the issue tracker responsiveness, release cadence, and whether there is an upgrade guide documenting breaking changes. If you need stronger guarantees, review the source and add your own feature tests covering panel registration and lock enforcement.
Weaver
How can I help you explore Laravel packages today?