- What Laravel versions does yajra/laravel-datatables-editor support?
- The package supports Laravel 12.x and 13.x officially, with backward compatibility for versions 5–11 via older package releases (1.x–11.x). Check the [compatibility table](https://github.com/yajra/laravel-datatables-editor) for exact mappings. Always use the version aligned with your Laravel release.
- Do I need a premium license for DataTables Editor to use this package?
- Yes, this package requires a **DataTables Editor premium license** (~$100–$300/year) to function. The license unlocks the Editor library, which this package integrates with for CRUD operations. The package itself is open-source, but the frontend library is commercial.
- How do I integrate this with an existing Laravel DataTables setup?
- Since this is a plugin for `yajra/laravel-datatables`, you’ll first need to install that package. Then, install `yajra/laravel-datatables-editor` via Composer and publish its config. The package extends DataTables’ existing pipelines, so your existing queries and responses will work with minimal adjustments for Editor-specific actions.
- Can I use this with Eloquent models or only query builder?
- The package supports **both Eloquent models and Laravel’s query builder**. It’s designed to work with any data source compatible with `yajra/laravel-datatables`, so you can use it for complex Eloquent relationships or raw SQL queries. The documentation provides examples for both approaches.
- What CRUD actions does this package support for DataTables Editor?
- The package fully supports **create, read, update, and delete** actions (CRUD) via DataTables Editor’s inline editing, bulk operations, and form-based workflows. You can also extend it with **custom actions** (e.g., file uploads, API calls) using the `customActions` property or event hooks.
- How do I handle validation for create/edit operations?
- Validation is handled via Laravel’s built-in **Form Request validation** or manual validation in event hooks. The package triggers `creating`, `updating`, and `deleting` events, allowing you to inject validation logic (e.g., using `Validator::make()` or Form Requests) before database operations occur.
- Is there a way to customize the Editor’s frontend behavior without touching the backend?
- The package focuses on **server-side processing**, so frontend customization (e.g., UI buttons, styling, or integrating with Vue/React) requires using DataTables Editor’s [frontend API](https://editor.datatables.net/manual/index). The backend remains decoupled, so you can style or extend the frontend independently.
- What are the performance implications of bulk operations (e.g., bulk edit/delete)?
- Bulk operations can introduce performance overhead, especially for large datasets, due to server-side processing. Optimize by **indexing database columns**, using **queue jobs** for async processing, or implementing **chunking** in your custom actions. The package processes requests efficiently, but scaling depends on your infrastructure.
- Are there alternatives to this package for Laravel CRUD with DataTables?
- If you don’t need DataTables Editor’s premium features, consider **vanilla DataTables** with custom Laravel routes for CRUD (e.g., using Laravel’s resource controllers). For open-source alternatives, check `spatie/laravel-data-table` or `maatwebsite/excel` for bulk operations. However, none match Editor’s inline editing or bulk workflows out of the box.
- How do I generate Editor stubs or scaffolding for a model?
- The package includes an **Artisan command** (`datatables-editor:generate`) to scaffold Editor configurations for your Eloquent models. Run `php artisan datatables-editor:generate ModelName` to generate a stub file with predefined CRUD actions, columns, and validation rules. This reduces boilerplate for rapid development.