Myster
Problem with ->unsavedChangesAlerts().
Guys, I'm using
->unsavedChangesAlerts()
. I need it to work when I trigger an action that is in the EditResource. I made the action redirect to another page and it still didn't trigger ->unsavedChangesAlerts()
. Any ideas what to do?2 replies
Notification for unsaved data
Guys, I currently have an action in my edit without verification, I can modify the form without clicking save and clicking on the action and it will work, but it will not save the changes. It is possible, for example, to add a
->requiresConfirmation()
that when clicking on the action and not having saved the data, a message appears "you have unsaved data, do you want to continue anyway?" but the message only appears if the person clicked on the action, modified the form data and did not save it.
Example action:
7 replies
Separate bulkactions.
Hey guys, is it possible to improve the visualization of bulkaction? I would like to separate them by lines, as if they were categories.
Bulkaction:
Test1
Test2
Test2
Delete
bulkaction wanted to know if it was possible:
Test1
-------
Test2
Test2
-------
Delete
5 replies
Auto increment field in the table.
Guys, I have a problem here. I need an auto increment field in my table. I tried using BigIncrements, however, as I have an id field that already has a primary key, I was unable to use it. Would there be another way to increase the table? I just can't use the id, I have to create another field for that.
4 replies
Hide table items according to status. No use of filters.
Hello, I have a question. I have my table that currently contains all the items in the database. I wanted to know if it is possible to bring only selected items. Ex:
Database:
ID | type | status
1 | A | new
2 | B | new
3 | A | in_process
Would it be possible, in the filament table, to only bring items that have the 'new' status? Without using filters on the table.
Filament:
ID | type | status
1 | A | new
2 | B | new
7 replies
Allow only users with specific roles to access the login.
Hi, I'm in a filament project with FilamentShield plugin. I have two panels, one for admin and one for a regular user. The admin has the super_admin role and the user has the user role. It is worth mentioning that the project has other roles. How do I so that, on the /admin route, only the super_admin can log in and that too on the /user route. How can I prevent other users with different roles from logging in? Plugin: FilamentShield.
5 replies