rubendn
2 Different Tables For The Same Resource
jawaad is on the right path. Let's say it's the User model.
I want to have one table that shows the list of records with certain fields from the User model and another table that shows other fields from the User model but I would like the Add/Edit Form to be the same for both so if I make changes to the form, I don't have to make it in 2 places which I would have to do if I create 2 separate resources for the one model.
9 replies
New Project Recommended Installation Steps/Order?
Sorry, I could have probably been more specific. When you install a new laravel project with Breeze using Livewire it installs Livewire. Will there be any type of conflict when you install Filament which installs Livewire? Do I remove it from composer.json? If it remove it from composer.json can I still use Livewire on the non-Filament pages?
6 replies
FileUpload Previewing with File Name not based on Stored Field
I am using the simple modal forms and the mutateFormDataBeforeFill() was not working so I switched to regular resources and it works with the following to show the preview:
Is there a way to use the mutateFormDataBeforeFill when using simple modal form resources?
5 replies
Many Identical Forms on the Same Custom Page
I've looked all around but can't find any hints on how to do this with a repeater field. The data is not in JSON and I want to be able to save each record individually, not submit and save all the repeaters at the same time.
How this is currently working is it reads a folder of images and then creates an array and then a form is created for each image. On save, the data is saved to a new record in the database, the image is moved to a new directory. There is also the option of copying some fields to the next forms On Save if they are going to be the same.
The main reason for wanting to do it in a standard Filament form is to be able to use some of the great field types such as a searchable Select and an Input with autocomplete without having to code those.
I'm already using the filament blade components for styling purposes.
15 replies
Error while upgrading from v2 to v3
I also found that line misleading and if I try to run "composer require livewire/livewire "^3.0"" to upgrade Livewire first, I get the following error:
Do I need to change the Filament version in Composer.json before upgrading Livewire? Thanks!
12 replies