CRUD List isn't displaying records

[smzapp]

All of the CRUD list of all tables are displaying no records. Upon checking the console, the problem is datatables. How should I fix this?

composer.json

"require": {
    "php": "^8.1",
    "backpack/crud": "^6.7",
    "backpack/editable-columns": "^3.0",
    "backpack/pro": "^2.2",
    "backpack/theme-coreuiv2": "^1.2",
    "backpack/theme-tabler": "^1.2",

}

[backpack-ai-bot[bot]]

When all CRUD list tables in Backpack are displaying no records and the console points to a DataTables issue, there are a few common causes and solutions based on the knowledge sources:

1. Check for JavaScript/Asset Issues

   • If DataTables or other required JS/CSS assets are not loaded (e.g., blocked by browser, missing files, or asset misconfiguration), the tables will not render or function. One user found that blocking external scripts (like datatables.net) caused the list to be empty. Make sure all required assets are loaded and not blocked by browser extensions or network policies. Backpack aims to avoid CDNs, but check your browser’s network tab to confirm all assets are loaded locally and not blocked by CSP or ad blockers Empty model list after creating new crud and adding an item.

2. Clear Cache and Re-publish Assets

   • Asset or cache issues are a frequent cause. Run the following commands to clear Backpack and Laravel caches and re-publish assets:

     php artisan config:clear
     php artisan cache:clear
     php artisan view:clear
     php artisan basset:clear
     php artisan vendor:publish --provider="Backpack\CRUD\BackpackServiceProvider" --tag=public --force
     

   • Also, ensure you have run php artisan storage:link if using Docker or different environments, as missing storage links can cause asset issues Bug.

3. Check AJAX Requests and Network Tab

   • The CRUD list uses AJAX to fetch data. Open your browser’s developer tools, go to the Network tab, and look for failed AJAX requests (usually to /admin/{entity}/search). If you see 500 or 419 errors, check your Laravel logs for more details. Common issues include CSRF problems, route misconfiguration, or missing controller methods List Operation does not get populated with information (no rows in table).

4. Check for Route or Controller Issues

   • Make sure you are using CRUD::resource in your routes, not Route::resource, as the latter does not register the AJAX search route needed by DataTables. If you use Route::resource, you must manually add the search route:

     Route::post('entity/search', 'EntityCrudController@search');

   • Also, ensure your controller exists and is correctly namespaced DataTable warning after update to Backpack 3.3 at Settings and Languages.

5. Check for Asset Conflicts or Outdated Files

   • If you have previously published Backpack assets, they may be outdated. Re-publish them with --force as shown above. Also, ensure you do not have conflicting packages (e.g., do not install both backpack/base and backpack/crud in v4+).

6. Check for Environment-Specific Issues

   • Sometimes, the problem is environment-specific (e.g., works in Docker but not locally, or vice versa). Double-check your .env settings, especially APP_URL, and clear all caches after making changes Bug.

If you follow these steps and the issue persists, check your Laravel logs for errors and ensure your Backpack and Laravel versions are compatible with your installed packages.

If you need more specific help, please provide any error messages from the browser console or Laravel logs.

ℹ️ Please note our AI Bot does not reply to follow-ups, this will be the only AI answer in this thread. If the AI helped you find the answer, please mark it as answered or write details below so it can learn. Then close the conversation. If not, please give more information for when a human reads this. ℹ️

Relevant sources:

Github Issue (closed): DataTable warning after update to Backpack 3.3 at Settings and Languages
Github Issue (closed): [V6][Bug] Possible script widget not loading
Bump datatables.net from 1.11.4 to 1.11.5
Github Issue (closed): Filters not cleaning properly
Github Issue (closed): 3 issues
Github Issue (closed): [4.0.x][Bug] Crud views are broken (Laravel 6.2)
Github Issue (closed): [Bug]
2. CRUD Operations|List Operation
Github Issue (closed): [Bug] Upgrade BackPack v5 to v6
Github Issue (closed): Pagination using AJAX
Github Issue (closed): [Bug] Uncaught TypeError: crud is undefined
Datatable Style
Github Issue (closed): User / news crud list is empty
Github Issue (closed): [Bug] List Operation does not get populated with information (no rows in table)
Github Issue (closed): Empty model list after creating new crud and adding an item

[smzapp]

clearing the basset solved this. thanks

php artisan basset:clear

[ahmadmobaraki-updivision]

Thank you @smzapp it worked for me! there was a CDN incident yesterday for datatables:
https://status.datatables.net/incidents/304991

Even though they claimed they fixed the issue, it was not working for me.. I guess because of the cache..
php artisan basset:clear did the job :)

[ahmadmobaraki-updivision]

@pxpm I get the same error again.. and basset:clear is not working anymore. probably datatable CDN goes down from time to time..
They suggested changing the CDN HERE from cdn.datatables.net to be datatables-cdn.com

How should I do that? I guess copying the whole crud list blade file into resources and modifying it is not a good solution. Same question @karandatwani92 asked here:
#1389

[smzapp]

@ahmadmobaraki-updivision Yeah, I also experience it few minutes ago. If CDN is not stable, I might be forced to use it under resources.

[pxpm]

I think that was the temporary solution. The cdn.datatables.net is as subdomain of the main datatable website, so even with a bit of downtime, in the long road it should be more reliable than an alternative domain IMO.

Also you don't need to publish the view, here is a small trick:

• download the file from any mirror that's working
• put the file in the correct folder in basset.
• rename the file to match the "missing file".

The list will then pick that file and it will work. The new version of basset will come with an improvement in this regard, so that in production you can just run basset:cache to cache the modified files, but keep the files that didn't change. That way, if you push a new version to production, the assets that are already downloaded and not modified, don't need to be cleared.

We will keep an eye on this 👍