404 only when RelationManager enabled (tenant setup, policies applied)
Hi all, I’m stuck with Filament v4 returning 404 when a RelationManager is active.
Setup
- Laravel v12, Filament v4
- Multi-tenancy modeled with companies table (company_id)
- Models:
Company (tenant, route by slug) CompanyRequestEvent → belongsTo(Company) CompanyRequestEventSector → belongsTo(CompanyRequestEvent) + hasOneThrough to CompanyResource / RelationManager
CompanyRequestEventResource: protected static ?string $tenantOwnershipRelationshipName = 'company'; CompanyRequestEventSectorsRelationManager: protected static string $relationship = 'companyRequestEventSectors'; + same tenantOwnershipRelationshipNameObserved behavior
Event edit page works without RelationManager Enabling RelationManager → 404 Tinker confirms $sector->company and $event->company return valid modelsWhat I tried
Policies for all 3 models with all methods returning true AuthServiceProvider registered hasOneThrough works in Tinker TenantOwnershipRelationshipName set correctlyQuestion / Help
Has anyone seen 404 only when RelationManager is active, even with policies and tenant ownership set? Where in Filament v4 would you debug authorization / tenant checks for RelationManagers?Thanks!
1 Reply
Solution
fix in version 4.0.11