Yajra datatable issues in laravel
Basic roles ,user and permission index is not working
not showing any data from database.?
Replies (8)
Hi Waqar,
If the basic roles, users, and permissions index is not showing any data from the database, it's possible that the database tables might not have been seeded with the required data.
To resolve this issue, you can try running the database seeder to populate the necessary data. You can do this by running the following command:
php artisan migrate:fresh --seedThis command will refresh the database by dropping all tables and then re-run the database migrations and seeders. After running this command, the tables should be populated with the required data, and you should be able to see the data in the basic roles, users, and permissions index.
If the issue still persists after running the seeder, please let me know.
Best regards
i run this command but its not comming data is already seeded
its the issue of datatable
js/custom folder is not compiling to public
there is no custom folder in js only two file
Hi Waqar,
Do you have access to our GitHub? the folder js/custom should be there.
https://github.com/KeenthemesHub/Metronic/tree/master/laravel/laravel_demo1/starterkit/public/assets/js/custom
Could you let me know if the problem occurs only after you build the assets with "npm run dev"?
Thanks
in github its exists but when i run the command npm run dev its not build to assets i tried two three times but still issue comming
Hi @Waqar,
Kindly Check with Latest node installed. My Node v18.17.0
Try below in order .
npm install
npm install --global yarn
yarn
npm install laravel-mix@latest --save-dev
npm run dev
Hi @Shyam,
After making all this steps now i am facing this issue at the end
[webpack-cli] Error: Cannot find module 'glob'
Require stack:
- C\***\***\****\*****\Projects\Metronic\webpack.mix.js
- C:\***\***\****\*****\\Projects\Metronic\node_modules\laravel-mix\setup\webpack.config.js
- C:\***\***\****\*****\Projects\Metronic\node_modules\webpack-cli\lib\webpack-cli.js
-C:\***\***\****\*****\Projects\Metronic\node_modules\webpack-cli\lib\bootstrap.js
- C:\***\***\****\*****\Projects\Metronic\node_modules\webpack-cli\bin\cli.js
- C:\***\***\****\*****\Projects\Metronic\node_modules\webpack\bin\webpack.js
at Module._resolveFilename (node:internal/modules/cjs/loader:995:15)
at Module._load (node:internal/modules/cjs/loader:841:27)
at Module.require (node:internal/modules/cjs/loader:1061:19)
at require (node:internal/modules/cjs/helpers:103:18)
at Object.<anonymous> (C:\***\***\****\*****\Projects\Metronic\webpack.mix.js:2:14)
at Module._compile (node:internal/modules/cjs/loader:1159:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
at Module.load (node:internal/modules/cjs/loader:1037:32)
at Module._load (node:internal/modules/cjs/loader:878:12)
at Module.require (node:internal/modules/cjs/loader:1061:19) {
code: 'MODULE_NOT_FOUND',
requireStack: [
'C:\***\***\****\*****\\Projects\\Metronic\\webpack.mix.js',
'C:\\***\***\****\*****\\Projects\\Metronic\\node_modules\\laravel-mix\\setup\\webpack.config.js',
'C:\\***\***\****\*****\\Projects\\Metronic\\node_modules\\webpack-cli\\lib\\webpack-cli.js',
'C:\\***\***\****\*****\\Projects\\Metronic\\node_modules\\webpack-cli\\lib\\bootstrap.js',
'C:\\***\***\****\*****\\Projects\\Metronic\\node_modules\\webpack-cli\\bin\\cli.js',
'C:\\***\***\****\*****\\Projects\\Metronic\\node_modules\\webpack\\bin\\webpack.js'
]
}
Hi,
Just to clarify, after running the "npm run dev" command, the assets are compiling correctly, but the public/assets/js/custom folder is not being generated, is that correct?
To investigate this further, we would appreciate if you could provide us with some additional information. Firstly, could you please let us know your current Node.js version? If you are not using Node.js version 18.x, please try using that version as it might resolve the issue.
It appears that this issue may be occurring under certain conditions, such as specific Node.js versions or on Windows OS. We suspect that these factors might be contributing to the problem. We will thoroughly look into this issue and work on a solution to fix it.
Thanks
