-
Notifications
You must be signed in to change notification settings - Fork 7
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
Tables not shown after updating to v2.3 #50
Comments
we don't have 2.3. Latest stable version is v.2.2. Do you use vuejs in your project? |
Because when I composer update, suddenly I got this message, "- Installing woo/laravel-grid-view (2.3): Extracting archive" so I thought that the package has been updated and that was why like suddenly the table was not displayed with Vue warn message. After that, even after downgrading or like specifying the version at composer.json, it still do not fix the issue. In my project, we don't use vuejs, we are only using Laravel 9 with PHP 8.1.6 . |
I have vue js on my project and i am facing same issue |
@farouqariff did you fixed the issue? |
@SunnnyGohil this gridview uses vue for rendering. If you have your gridview rendered within vue-handled component you might get vue warning that it doesn't support script inject into vue component. if you have the following error please try out creating your grid with 'standaloneVue' => true in your config and registering this component in your vue instance: |
or please provide some detailed screenshots/logs of error so I could assist you |
this is the my code |
I replace this package with laravel-grid-view by itstructure.. |
thanks for the suggestion I will update. |
I come from v2.2 and I implement it on my Laravel project. I don't know why but after updating to v2.3 suddenly the tables were not able to displayed. When I check on Inspect page, it said "app.js:17 [Vue warn]: Unknown custom element: - did you register the component correctly? For recursive components, make sure to provide the "name" option.". Hope Mr. Denis can help me on solving this issue.
The text was updated successfully, but these errors were encountered: