Mike Scott
Importer fails rows with blank email fields when the email rule is applied to the column
I generated an importer and it intelligently added the email rule to an email column. The email column is not required - empty emails are allowed. However, the import fails on the email rule when the email is empty. So for a non-required email field, the email rule is useless.
Apologies if I'm missing something obvious. Is there a way around this?
4 replies
SOLVED: Potential Security Issue - Filament isn't exposing model attributes. It was a false alarm.
EDIT: false alarm. It turns out that the Livewire tab in DebugBar isn't actually showing what Livewire is sending to the browser. So the apparent leakage of sensitive data is just the display of Livewire's internal server state by DebugBar.
I was surprised to see my full model data including sensitive attributes in DebugBar's Livewire tab, despite these attributes being listed in the model's $hidden array, as documented on Filament's security page. See attached screenshot.
Am I missing something? Is there some other function I need to call to prevent these secure properties from being serialised and sent to the browser?
9 replies
Multi-level Hierarchical Navigation Groups
Is it possible to have multiple levels of groups in the navigation menu or must there only be a top level of groups with one level of items inside? IOW is there a way to create a navigation group inside a navigation group, then add items to it?
28 replies
How to use a Checkbox to edit fields in a related model
I've got a simple has-one relationship in my
User
model which relates to a UserFeatures
model, which has various fields that I'd like to edit with checkboxes in my UserResource
:
I've tried to do this using 'dot' notation to form a path, where feature_field
is one of the fields in UserFeatures
, like so:
However, this always returns a state of null.
So how can one create checkboxes to edit values in a 'has-one' related model?6 replies
How to access a route parameter in Livewire pagination request?
I've got a resource for customer inquiries, which can be of 5 different types, so I pass the type in a URL query parameter, for example:
/inquiries?type=offer
I can easily get this query parameter in the request and if no type parameter is passed, it defaults to the first inquiry type, so everything works great.
However, when clicking on the pagination for page 2, for example, a Livewire request is sent to the following endpoint:
/livewire/message/app.filament.resources.inquiry-resource.pages.list-inquiries
But the '?type=offer' query parameter is omitted, so the request falls back to the default type and I get the 2nd page for that, not the original inquiry type.
My question is, how can I get the request's query parameters sent in Livewire requests?
6 replies