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

[Bug] - no hint path defined backpack with livewire v3 #5599

Closed
t-prod opened this issue Aug 5, 2024 · 2 comments
Closed

[Bug] - no hint path defined backpack with livewire v3 #5599

t-prod opened this issue Aug 5, 2024 · 2 comments
Assignees
Labels

Comments

@t-prod
Copy link
Contributor

t-prod commented Aug 5, 2024

Bug report

What I did

I've updated on Laravel 10 Livewire 3 and Backpack 6 (was 5 before)

What I expected to happen

I have no hint path defined laravel when I include full page components with Livewire 3

What happened

I have this error : I have no hint path defined for backpack

What I've already tried to fix it

Try to override the theme config

How can I do to fix this error. :
I include full page component like this :

return view('quote::livewire.quote-data-table', [
            'results' => $results, 'countStatuses' => $countStatuses
        ])->extends('backpack::layouts.top_left')->section('content');
@tabacitu
Copy link
Member

Hi @t-prod ,

Here are a few ideas:

  1. Are you sure you've followed all steps in the upgrade guide? For example I see quite a few previous issues where Pedro replied they should delete the errors views directory - could that be your problem too? No hint path defined for [backpack] error in all pages  FileManager#41 (comment)

  2. "No hint path defined" is a very general error. Any chance you can provide a link to the error using Ignition/Flare? So that we can look at the error stack?

Cheers!

@tabacitu tabacitu moved this to In Progress in This week Aug 20, 2024
@tabacitu tabacitu self-assigned this Aug 20, 2024
@tabacitu
Copy link
Member

Hey @t-prod - I'm going to assume the above will fix your issue too and close the issue - let us know if that's not the case. But I'm pretty sure it's an upgrade step being skipped, so I'll close it. Cheers!

@github-project-automation github-project-automation bot moved this from In Progress to Done in This week Aug 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

No branches or pull requests

2 participants