herakles0910
404 in modal after deleting a record on a custom page
public function deleteTableAction(): DeleteAction
{
return DeleteAction::make('deleteTable')
->record(fn(ProjectDataImportTable $record) => $record)
->action(function (ProjectDataImportTable $record) {
$record->delete();
})
->successRedirectUrl(url()->current());
}
If you're using a custom Livewire component inside the Page, you must pass the record directly to avoid findOrFail() errors. If you use IDs, ensure they’re properly passed and exist in the model
7 replies
404 in modal after deleting a record on a custom page
The issue you're experiencing — where clicking "Confirm" on the DeleteAction results in a 404 error and the modal not closing properly — is likely due to how the route binding, Livewire, and Filament page context are handled.
7 replies
Searching encrypted columns
Why It Doesn’t Work
Filament’s ->searchable() relies on SQL-level filtering, meaning the search query is executed on the database side. Since encrypted fields are stored as ciphertext, SQL cannot match or search them — the database doesn’t “know” what the decrypted values are. What You Can Do
You can’t directly search encrypted columns in SQL unless you:
Index unencrypted duplicates of the fields (not secure unless access-controlled carefully).
Use client-side or Laravel-level filtering after fetching and decrypting the records.
Possible Workaround (Laravel Collection Filtering):
If you can fetch all records first, then filter using Laravel (in memory), you can do
3 replies