-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
Conflict with cached routes #25
Comments
Hey, I tried to do some exploration on the issue. I discovered than when the routes are cached they don't seem to show up in the I'm using a fresh Laravel 5.8 project with Nova 2, this is how the route is registered: |
Catch the same issue, have any ideas how to fix it? Don't want to lose ability of route caching 😕 |
+1 still having those issues with Laravel Nova 2.0.11 + nova-page 0.2.3 |
Any idea to solve this issue guys, please |
Just hit this issue myself when deploying this with a project using deployer. It breaks a lot of stuff! I've even tried limiting down my routes file so it doesn't leverage the middleware, and doesn't define a template but still no joy... |
Hit this issue on a new (nova 2.7) project just now. |
@voidgraphics The issue still exists with L6.14.0 and Nova 2.10.1 |
Is there any fix for this yet @voidgraphics ? Really seems a shame to not get this bug fixed. Have the exact same issues as above in Laravel 8 and Nova 3. The package itself is fantastic and super useful. |
The Nova Pages tool doesn't load correctly when routes are cached with
php artisan route:cache
.Steps to reproduce:
php artisan route:cache
.php artisan route:clear
.From my debugging, appears as if the original Nova routes are used when caching is enabled which is giving a dependency injection error.
The text was updated successfully, but these errors were encountered: