Kane G
Persistent search selections on table
You should be able to follow either of these examples below.
You can persist in the URL:
https://filamentphp.com/docs/3.x/tables/columns/getting-started#searching-individually (example at bottom of this section)
Or persist in session:
https://filamentphp.com/docs/3.x/tables/columns/getting-started#persist-search-in-session
4 replies
canAccess() is called on every page/resource AFTER logout resulting in an exception?
The problem is strange in that the nav runs first before the redirect but that could be for a number of reasons.
Realistically you should be making sure your functions return the correct type anyway. That function you posted above, has the possibility to return
null
but specifying only a bool
can be returned.
Would be a better way to check and ensure when auth()->user()
is null
it will return false
.4 replies
Action $arguments returning empty in visible closure
Now that I typed that out, I'm thinking it might be a better idea to create a component to display a single subscription component, and pass the name to that and have all the actions inside that.
5 replies
Action $arguments returning empty in visible closure
I have a custom page that is used to manage subscriptions. On this page I have 3 tabs (my subscription, subscription management and payment methods)
On subscription management, it displays the 3 subscriptions to pick from - these are generated from the DB so I loop over those results to display the subscriptions, with features, price etc.
My goal here is to display a subscribe button (when no active subscription is present) and a switch subscription button (when there is an active one). To process the the correct subscription, I pass the subscription name through the arguments on the action. On the switch subscription button I only want to show available subscriptions so I want to hide the active switch subscription action only.
Something like this:
I have a workaround atm (provided from the bug report I sent through). Setting the action to a variable first and then calling that variable actually solves the issue.
eg.
I change this:
To this:
I'm quite new to filament so not sure if this is the best approach.
5 replies
Typed static property error when trying to activate cluster functionality
Ok I fixed my issue by updating my
config/livewire.php
settings. Making sure render_on_redirect
is set to false
will fix the Typed static property Filament\Pages\BasePage::$view must not be accessed before initialization
issue.5 replies
After Login in, Dashboard design is all out of wack.
After reading your comments about making sure spa settings weren't activated, I ran back over my code. That actual issue here was using
wire:navigate
on my links from my guest pages. Removing that and allowing the pages to load naturally fixed my display issues.16 replies
After Login in, Dashboard design is all out of wack.
I'm running into this same issue moving between admin/user panel and laravel blade pages (outside of filament) . I have some guest pages built with Laravel / Livewire and the problem happens when including
@livewireScripts
within the guest layout.
This is using the default laravel sail setup (locally)16 replies