- What is clevyr/nova-action-button used for?
- It is a Laravel Nova package that adds customizable action buttons to Nova resources. You can use it to trigger Nova actions, routes, or custom callbacks directly from index and detail views. It is a UI ergonomics layer over Nova's existing action pipeline rather than a separate workflow engine.
- How do I install clevyr/nova-action-button?
- Install it with Composer using composer require clevyr/nova-action-button. Pin it to a supported v2.x constraint for modern Nova, such as a caret constraint on 2.0.2. No migrations, infrastructure changes, or data model changes are required.
- Which Laravel Nova versions are supported by clevyr/nova-action-button?
- The v2 line targets modern Nova releases. Older Nova 3 installations must stay on the v1 line. Confirm your Nova major and minor against the package's Composer constraint before upgrading.
- How do I add an action button to a Nova index or detail view?
- Use the package's button component on the Nova surface where you want the action exposed. It lets you render Nova actions as standalone buttons on index, detail, or toolbar areas instead of only inside the actions dropdown. Setup is minimal and intended to replace hand-rolled Vue or Blade action menus.
- Can I wire a Nova action button to a route or custom callback?
- Yes. The package lets you quickly wire buttons to routes, Nova actions, or custom callbacks. That makes it useful for admin workflows that need a direct button rather than a dropdown action.
- What changed in clevyr/nova-action-button v2.0.2?
- v2.0.2 is a patch on the v2 line with a single-line behavioral fix. Actions marked with withoutConfirmation() are now respected, so they no longer show a confirmation modal. This is a behavioral change, not just cosmetic, so audit any flows that relied on the extra click.
- Does clevyr/nova-action-button respect withoutConfirmation() on Nova actions?
- Yes, as of v2.0.2 the package respects withoutConfirmation() and does not force a confirmation modal for those actions. The default confirming path should remain untouched. Test a destructive action after upgrading to confirm confirmation still appears where expected.
- Is clevyr/nova-action-button safe to use in production?
- It is a low-risk, low-coupling UI layer over Nova's action pipeline and does not touch domain code, queues, or persistence. It inherits Nova's authorization, validation, and lifecycle semantics. Because it is a small, single-maintainer package in the admin path, pin the version and cover it with a smoke test.
- How do I upgrade clevyr/nova-action-button from 2.0.1 to 2.0.2?
- The upgrade is a patch-level, semver-safe Composer update with no config key renames, published asset invalidations, or migrations. Run composer update clevyr/nova-action-button and the Nova asset build. Smoke-test a default confirming action, a withoutConfirmation() action, and an action with redirect or close behavior.
- Do I need migrations or database changes for clevyr/nova-action-button?
- No. It is a Composer-only install with no infrastructure change, no data model change, and no migration. It should be treated as a UI dependency of the Nova admin panel only and should not leak into public-facing routes or non-Nova controllers.