requiresConfirmation modal is empty after composer update

On our staging server one of our developers has update composer (composer update) and the requiresConfirmation() modal is no longer working. The background fades like the modal was triggered and other modals still have their content. It seems to only be happening with the requiresConfirmation. I've tried going back to a previous version of livewire, making sure all caches are cleared, dumping composer autoload etc. The changelog doesn't note anything change with this method and there are no errors in the php log when using the modal. The same code works fine on prod. No errors or warning in console and all logs are empty. The modal is just blank. It's very similar to this, except it happens BEFORE the confirmation instead of after. If you remove the requiresConfirmation() method, works fine. https://github.com/filamentphp/filament/issues/919
protected function getActions(): array
{
return [
Action::make('exports')
// call Maatwebsite Export
->action(fn() => ( new CustomerMageLogExport( $this->getTable() ) ) ) )
->requiresConfirmation(),
];
}
protected function getActions(): array
{
return [
Action::make('exports')
// call Maatwebsite Export
->action(fn() => ( new CustomerMageLogExport( $this->getTable() ) ) ) )
->requiresConfirmation(),
];
}
Attached are the currently installed libs. Any ideas of things to try? The thread linked above the error just went away but nothing we've tried seems to work. I suspect some sort of conflict but there are no errors anywhere so it's hard to track down. I'm still digging and will update if I find anything.
GitHub
requiresConfirmation on table action ends in overlay and errors · I...
Package filament/tables Package Version v2.5.31 Laravel Version v8.76.2 Livewire Version v2.8.2 PHP Version 8.0.13 Bug description I am using the table and forms package outside of filament admin! ...
3 Replies
Chrispian
Chrispian15mo ago
I tried using modalContent() without the custom action and no joy there either, same behavior. I've stripped it down to just the basics so it seems to be something related to the composer update. I reverted to the previous composer.json versions and it's working again. So something in the composer update is definitely the root cause.
Dan Harrin
Dan Harrin15mo ago
let me know if this doesnt get fixed after the next update, but i havent made any specific changes that would make a difference
Chrispian
Chrispian15mo ago
Sounds good. I'm guessing it might be in something else that updated because I didn't see any changes here either but couldn't get a good error to track it down. We'll update again in a few weeks or so and I'll report back.