hayvern
How to adjust columnSpan for Relation Manager?
The simplest way is that I just widen the main working section from columnSpan(2) -> columnSpan(3)... this makes things align. So it's not a dealbreaker. Just that all table's width (seems to be) governed by the maxContentWidth() in AdminPanelProvider. IMO it would be good if tables can widths can be adjusted. The coding needed to do this is beyond my current skills and I can only imagine the Filament Team has a good reason for not having this adjustment configurable.
Thanks @krekas @Vp for suggestions.
18 replies
How to adjust columnSpan for Relation Manager?
I appreciate the suggestion. However, I want the form to look as is currently (if it can be helped). I know that if I remove the columns it will align. But the form is the main working section and so I have hoped the RM can be sized to match without needing to remove the column settings.
18 replies
How to adjust columnSpan for Relation Manager?
Unfortunately for my use case, I need the sub-navigation to appear because I want to control canEdit on policy for users so they can't edit the ticket. Ofcourse, I can change the design and get rid of sub-navigation (use headerActions instead) and resize the forms (small headache) so that it looks right. But, seems odd that a Relation Manager which is a table and the width cannot be resized... somehow.
18 replies
How to adjust columnSpan for Relation Manager?
The current position of the Relation Manager in my screenshot is acceptable. I just want to control the span of the Relation Manager table to be smaller in width (in accordance to the columns used by the Resource form).
18 replies
FileUpload preview gets 404 error
I fixed the issue by removing the '/admin' that was included into my .env for for APP_URL.
So the value now reads as: APP_URL=http://localhost:8000
4 replies
Line between navigation child items do not appear
Solved. Did a
composer update for version 3.1.28 and refreshed the site. The line is back. It was working on 3.1.15. Broke at 3.1.23. And is working fine with any code changes on my part in version 3.1.28.3 replies
Create and edit pages return error trim(): Argument #1 ($string) ...
I have no idea what I'm doing most of the time. Just too new with Laravel/Filament. But been loving it. Your help just sweetens it much more.
Same here, I'm doc diving, running 2 instances at the same time to test stuff on my on-going project and a fresh one to see what works/breaks. 80% of the time is reading docs, 20% is coding actually.
19 replies
Create and edit pages return error trim(): Argument #1 ($string) ...
Thanks for the hint. I was mucking about with publishing assets early on in the project and I'm not fully aware about how the internal mechanism for Laravel/Filament works yet.
I fixed the issue by:
1. Deleting the vendor folder. [Error goes away but form is wonky, missing components etc]
2. Ran: "php artisan vendor:publish --tag=filament-views --force"
3. php artisan cache:clear, php artisan view:clear, php artisan config:clear
Issue is fixed now. Appreciate the reply!
19 replies
Create and edit pages return error trim(): Argument #1 ($string) ...
I'm getting the same error on a local project that ran fine on v3.0-stable. Did a composer update to v3.1.15 and I'm getting a "trim(): Argument #1 ($string) must be of type string, array given" error when accessing an entry in the Resource table.
Error is pointing to:
resources\views\vendor\filament\components\section.blade.php : 58
Action: I updated composer.json to use "3.1.15" followed by composer update.
Don't know where to start checking... any ideas?
19 replies