View not found

Has anyone come across the issue where you're experiencing the error View [name-of-view] not found on Vapor when it works fine on your local machine? We're using Vapor/AWS to host our site. We imported the package: "njxqlus/filament-relation-manager-component" which seems to work great on our local dev environment, but then when we deploy it to vapor, even if we publish the views, we're getting these errors:
"exception":
{
"class":
"Illuminate\View\ViewException",
"message":
"View [infolists.relation-manager] not found. (View: /var/task/vendor/filament/infolists/resources/views/component-container.blade.php) (View: /var/task/vendor/filament/infolists/resources/views/component-container.blade.php) (View: /var/task/vendor/filament/infolists/resources/views/component-container.blade.php) (View: /var/task/vendor/filament/infolists/resources/views/component-container.blade.php) (View: /var/task/vendor/filament/infolists/resources/views/component-container.blade.php)",
"code":
0,
"file":
"/var/task/vendor/laravel/framework/src/Illuminate/View/FileViewFinder.php:137"
"exception":
{
"class":
"Illuminate\View\ViewException",
"message":
"View [infolists.relation-manager] not found. (View: /var/task/vendor/filament/infolists/resources/views/component-container.blade.php) (View: /var/task/vendor/filament/infolists/resources/views/component-container.blade.php) (View: /var/task/vendor/filament/infolists/resources/views/component-container.blade.php) (View: /var/task/vendor/filament/infolists/resources/views/component-container.blade.php) (View: /var/task/vendor/filament/infolists/resources/views/component-container.blade.php)",
"code":
0,
"file":
"/var/task/vendor/laravel/framework/src/Illuminate/View/FileViewFinder.php:137"
Am I forgetting something that needs to be modified or published somewhere?
Solution:
Turns out the package used a capital "I" in Infolist rathern than the required folder name having a lowercase "i" as in infolist. Published the views then renamed the folder to get it to work.
Jump to solution
1 Reply
Solution
Clay Bitner
Clay Bitner2mo ago
Turns out the package used a capital "I" in Infolist rathern than the required folder name having a lowercase "i" as in infolist. Published the views then renamed the folder to get it to work.