Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Layout not found when using artisan queue:work #111

Closed
yonex68 opened this issue Nov 21, 2023 · 6 comments
Closed

Layout not found when using artisan queue:work #111

yonex68 opened this issue Nov 21, 2023 · 6 comments

Comments

@yonex68
Copy link

yonex68 commented Nov 21, 2023

Hi!

I'm encountering a strange issue, as the "php artisan queue:work" command always fails when adding a job to the default queue:

Exception: Filament Fabricator: Layout 'default' not found in file C:\xampp\htdocs\filament-test-export\vendor\z3d0x\filament-fabricator\src\Http\Controllers\PageController.php on line 31

The job is using spatie/laravel-export which crawls the urls of the website.
When using the commands "php artisan queue:work --once" and "php artisan queue:listen", everything is fine, but running "php artisan queue:work" will throw the exception above, although the layout has been created by running "php artisan filament-fabricator:layout DefaultLayout".

Do you have any clue of what can cause this error?

Thx!

@Z3d0X
Copy link
Owner

Z3d0X commented Nov 21, 2023

This was fixed in v2.0.3 pls update your plugin version

@Z3d0X Z3d0X closed this as completed Nov 21, 2023
@yonex68
Copy link
Author

yonex68 commented Nov 21, 2023

All plugins are up to date... Still have the error:

image

image

@yonex68
Copy link
Author

yonex68 commented Nov 21, 2023

I've put some logs in Http\Controllers\PageController.php:

image

And the getLayoutFromName('default') function returns null

@Z3d0X
Copy link
Owner

Z3d0X commented Nov 21, 2023

composer show z3d0x/filament-fabricator

@yonex68
Copy link
Author

yonex68 commented Nov 21, 2023

image

@jydevgit
Copy link

I have exactly the same bug in a similar environment.. have you an idea?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants