diff --git a/3.4/crud-operation-delete.md b/3.4/crud-operation-delete.md index 2ac713ac..8a661cd9 100644 --- a/3.4/crud-operation-delete.md +++ b/3.4/crud-operation-delete.md @@ -2,27 +2,27 @@ -- - + ## About This CRUD operation allows your admins to remove one or more entries from the table. >In case your entity has SoftDeletes, it will perform a soft delete. The admin will _not_ know that his entry has been hard or soft deleted, since it will no longer show up in the ListEntries view. - + ## Delete a Single Item - + ### How it Works Using AJAX, a DELETE request is performed towards ```/entity-name/{id}```, which points to the ```destroy()``` method in your EntityCrudController. - + ### How to Use The ```Delete``` action is **enabled by default**. To disable it, you should use ```$this->crud->denyAccess('delete');``` inside your ```setup()``` method. This will prevent the Delete button from appearing in the table view, and will deny access to the controller method if manually accessed. - + ### How to Overwrite In case you need to change how this operation works, just create a ```destroy()``` method in your EntityCrudController: @@ -42,18 +42,18 @@ You can also overwrite the delete button by creating a file with the same name i php artisan backpack:crud:publish buttons/delete ``` - + ## Delete Multiple Items (Bulk Delete) In addition to the button for each entry, you can show checkboxes next to each element, and allow your admin to delete multiple entries at once. - + ### How it Works Using AJAX, a DELETE request is performed towards ```/entity-name/bulk-delete```, which points to the ```bulkDelete()``` method in your EntityCrudController. - + ### How to Use The ```bulkDelete()``` action is **enabled by default**, but there are no buttons using it. To make the buttons show up, inside your ```setup()``` method you should: @@ -63,7 +63,7 @@ $this->crud->enableBulkActions(); $this->crud->addBulkDeleteButton(); ``` - + ### How to Overwrite In case you need to change how this operation works, just create a ```bulkDelete()``` method in your EntityCrudController: diff --git a/3.4/crud-operation-show.md b/3.4/crud-operation-show.md index 6330bc62..ce7a7f6a 100644 --- a/3.4/crud-operation-show.md +++ b/3.4/crud-operation-show.md @@ -2,7 +2,7 @@ -- - + ## About This CRUD operation allows your admins to preview an entry. When enabled, it will add a "Preview" button in the ListEntries view, that points to a show page: @@ -11,19 +11,19 @@ This CRUD operation allows your admins to preview an entry. When enabled, it wil In case your entity is translatable, it will show a multi-language dropdown, just like Edit. - + ## How it Works The ```/entity-name/{id}``` route points to the ```show()``` method in your EntityCrudController. Inside this method, it uses ```setFromDb()``` to try to magically figure out all attributes you would like shown for this Model, and shows them using [Column types](/docs/{{version}}/crud-columns) inside ```show.blade.php```. - + ## How to Use The ```ListEntries``` operations is **disabled by default**. To enable it, you should use ```$this->crud->allowAccess('show');``` inside your ```setup()``` method.This will make a Preview button appear in the table view, and allow access to the show view. This view uses the same column types you've defined in ```setup()``` and adds all other fillable attributes. You will most likely need to add/change/remove columns, so also check out [How to Overwrite](#how-to-overwrite). - + ## How to Overwrite In case you need to add/change/remove any columns, create a ```show()``` method in your EntityCrudController. Using the ```addColumn()``` you're already familiar with, you can change how those attributes are shown to the admin. For example: diff --git a/4.0/base-breadcrumbs.md b/4.0/base-breadcrumbs.md index a3a7d5ad..c9122241 100644 --- a/4.0/base-breadcrumbs.md +++ b/4.0/base-breadcrumbs.md @@ -46,7 +46,7 @@ Notice the last item should NOT have a link, it should be ```false```. ## How to Define Breadcrumbs - + ### Define Breadcrumbs Inside the Controller Make sure a ```$breadcrumbs``` variable is present inside your views: @@ -68,7 +68,7 @@ Make sure a ```$breadcrumbs``` variable is present inside your views: } ``` - + ### Define Breadcrumbs Inside the View Make sure a ```$breadcrumbs``` variable is present: diff --git a/4.0/base-how-to.md b/4.0/base-how-to.md index d952b684..15413e05 100644 --- a/4.0/base-how-to.md +++ b/4.0/base-how-to.md @@ -79,7 +79,7 @@ Our default design might not be pleasant for your, or you might need to make the You'll find a few examples below - but you should use which classes you want to get the result you need. - + #### Backstrap Transparent top menu, transparent sidebar, transparent footer. This is the default. This is what _we_ think is best for most users, from our 8+ years of experience building admin panels. Prioritising _content_ over _menus_. @@ -93,7 +93,7 @@ Transparent top menu, transparent sidebar, transparent footer. This is the defau 'footer_class' => 'app-footer', ``` - + #### Inspired by CoreUI White top menu, dark sidebar. @@ -107,7 +107,7 @@ White top menu, dark sidebar. 'footer_class' => 'app-footer d-none', ``` - + #### Inspired by Github Black top menu, white sidebar. @@ -121,7 +121,7 @@ Black top menu, white sidebar. 'footer_class' => 'app-footer d-none', ``` - + #### Blue Top Menu Blue top menu, dark sidebar. @@ -136,7 +136,7 @@ Blue top menu, dark sidebar. ``` - + #### Construction / Warning Yellow top menu, dark sidebar. @@ -150,7 +150,7 @@ Yellow top menu, dark sidebar. 'footer_class' => 'app-footer d-none', ``` - + #### Red Top Menu Red top menu, dark sidebar. @@ -164,7 +164,7 @@ Red top menu, dark sidebar. 'footer_class' => 'app-footer d-none', ``` - + #### Pink Top Menu Pink top menu, transparent sidebar. @@ -179,7 +179,7 @@ Pink top menu, transparent sidebar. ``` - + #### Green Top Menu Green top menu, white sidebar. diff --git a/4.0/upgrade-guide.md b/4.0/upgrade-guide.md index 4dc5cd01..f34608c4 100644 --- a/4.0/upgrade-guide.md +++ b/4.0/upgrade-guide.md @@ -427,7 +427,7 @@ instead of This is completely optional - whatever you prefer. - + ### Views Most views have suffered big changes, since we've moved from Bootstrap 3 to Bootstrap 4, and from AdminLTE to CoreUI. If you've overwritten many Backpack views, the upgrade process will be more difficult for you: you have to start from our new views and make the changes again. diff --git a/4.1/base-breadcrumbs.md b/4.1/base-breadcrumbs.md index a3a7d5ad..c9122241 100644 --- a/4.1/base-breadcrumbs.md +++ b/4.1/base-breadcrumbs.md @@ -46,7 +46,7 @@ Notice the last item should NOT have a link, it should be ```false```. ## How to Define Breadcrumbs - + ### Define Breadcrumbs Inside the Controller Make sure a ```$breadcrumbs``` variable is present inside your views: @@ -68,7 +68,7 @@ Make sure a ```$breadcrumbs``` variable is present inside your views: } ``` - + ### Define Breadcrumbs Inside the View Make sure a ```$breadcrumbs``` variable is present: diff --git a/4.1/base-how-to.md b/4.1/base-how-to.md index fbaa0cb5..8d4fb45a 100644 --- a/4.1/base-how-to.md +++ b/4.1/base-how-to.md @@ -79,7 +79,7 @@ Our default design might not be pleasant for your, or you might need to make the You'll find a few examples below - but you should use which classes you want to get the result you need. - + #### Backstrap Transparent top menu, transparent sidebar, transparent footer. This is the default. This is what _we_ think is best for most users, from our 8+ years of experience building admin panels. Prioritising _content_ over _menus_. @@ -93,7 +93,7 @@ Transparent top menu, transparent sidebar, transparent footer. This is the defau 'footer_class' => 'app-footer', ``` - + #### Inspired by CoreUI White top menu, dark sidebar. @@ -107,7 +107,7 @@ White top menu, dark sidebar. 'footer_class' => 'app-footer d-none', ``` - + #### Inspired by Github Black top menu, white sidebar. @@ -121,7 +121,7 @@ Black top menu, white sidebar. 'footer_class' => 'app-footer d-none', ``` - + #### Blue Top Menu Blue top menu, dark sidebar. @@ -136,7 +136,7 @@ Blue top menu, dark sidebar. ``` - + #### Construction / Warning Yellow top menu, dark sidebar. @@ -150,7 +150,7 @@ Yellow top menu, dark sidebar. 'footer_class' => 'app-footer d-none', ``` - + #### Red Top Menu Red top menu, dark sidebar. @@ -164,7 +164,7 @@ Red top menu, dark sidebar. 'footer_class' => 'app-footer d-none', ``` - + #### Pink Top Menu Pink top menu, transparent sidebar. @@ -179,7 +179,7 @@ Pink top menu, transparent sidebar. ``` - + #### Green Top Menu Green top menu, white sidebar. diff --git a/4.1/upgrade-guide.md b/4.1/upgrade-guide.md index 67bdb70e..2b91bb49 100644 --- a/4.1/upgrade-guide.md +++ b/4.1/upgrade-guide.md @@ -188,7 +188,7 @@ Why? Since ```$this->request``` did nothing at all, we've removed it, to avoid a Additionally, for the `select2_from_ajax` and `select2_from_ajax_multiple` field types, the inputs on the main form are no longer sent through the AJAX request by default. If you're using [dependant selects](https://backpackforlaravel.com/docs/4.1/crud-how-to#add-a-select2-field-that-depends-on-another-field), please make sure that you add `'include_all_form_fields' => true` to your `select2_from_ajax` and `select2_from_ajax_multiple` field definition to keep the same behaviour as before. - + ### CSS & JS Assets Step 13. We've updated most CSS & JS dependencies to their latest versions. There are two ways to publish the latest styles and scripts for these dependencies: diff --git a/5.x/base-breadcrumbs.md b/5.x/base-breadcrumbs.md index a3a7d5ad..c9122241 100644 --- a/5.x/base-breadcrumbs.md +++ b/5.x/base-breadcrumbs.md @@ -46,7 +46,7 @@ Notice the last item should NOT have a link, it should be ```false```. ## How to Define Breadcrumbs - + ### Define Breadcrumbs Inside the Controller Make sure a ```$breadcrumbs``` variable is present inside your views: @@ -68,7 +68,7 @@ Make sure a ```$breadcrumbs``` variable is present inside your views: } ``` - + ### Define Breadcrumbs Inside the View Make sure a ```$breadcrumbs``` variable is present: diff --git a/5.x/base-how-to.md b/5.x/base-how-to.md index 43003379..ec50191f 100644 --- a/5.x/base-how-to.md +++ b/5.x/base-how-to.md @@ -79,7 +79,7 @@ Our default design might not be pleasant for your, or you might need to make the You'll find a few examples below - but you should use which classes you want to get the result you need. - + #### Backstrap Transparent top menu, transparent sidebar, transparent footer. This is the default. This is what _we_ think is best for most users, from our 8+ years of experience building admin panels. Prioritising _content_ over _menus_. @@ -93,7 +93,7 @@ Transparent top menu, transparent sidebar, transparent footer. This is the defau 'footer_class' => 'app-footer', ``` - + #### Inspired by CoreUI White top menu, dark sidebar. @@ -107,7 +107,7 @@ White top menu, dark sidebar. 'footer_class' => 'app-footer d-none', ``` - + #### Inspired by GitHub Black top menu, white sidebar. @@ -121,7 +121,7 @@ Black top menu, white sidebar. 'footer_class' => 'app-footer d-none', ``` - + #### Blue Top Menu Blue top menu, dark sidebar. @@ -136,7 +136,7 @@ Blue top menu, dark sidebar. ``` - + #### Construction / Warning Yellow top menu, dark sidebar. @@ -150,7 +150,7 @@ Yellow top menu, dark sidebar. 'footer_class' => 'app-footer d-none', ``` - + #### Red Top Menu Red top menu, dark sidebar. @@ -164,7 +164,7 @@ Red top menu, dark sidebar. 'footer_class' => 'app-footer d-none', ``` - + #### Pink Top Menu Pink top menu, transparent sidebar. @@ -179,7 +179,7 @@ Pink top menu, transparent sidebar. ``` - + #### Green Top Menu Green top menu, white sidebar. diff --git a/5.x/upgrade-guide.md b/5.x/upgrade-guide.md index 82ba76c4..011adf46 100644 --- a/5.x/upgrade-guide.md +++ b/5.x/upgrade-guide.md @@ -258,7 +258,7 @@ Alternatively... if you absolutely _hate_ this new behaviour and want your previ - you can create a new file in your `resources/views/vendor/backpack/fields/page_or_link.blade.php` and paste [the content from here](https://raw.githubusercontent.com/Laravel-Backpack/MenuCRUD/e0afc7960d5513017ef847480f50591400bd4a6b/src/resources/views/fields/page_or_link.blade.php); - + ### CSS & JS Assets Step 18. We've removed the custom CSS & JS files that Backpack provided for each operation (eg. `list.css` and `create.js` - [see why here](https://github.com/Laravel-Backpack/CRUD/pull/3942)). diff --git a/6.x/base-breadcrumbs.md b/6.x/base-breadcrumbs.md index 1512ee39..dd5df40c 100644 --- a/6.x/base-breadcrumbs.md +++ b/6.x/base-breadcrumbs.md @@ -46,7 +46,7 @@ Notice the last item should NOT have a link, it should be ```false```. ## How to Define Breadcrumbs - + ### Define Breadcrumbs Inside the Controller Make sure a ```$breadcrumbs``` variable is present inside your views: @@ -68,7 +68,7 @@ Make sure a ```$breadcrumbs``` variable is present inside your views: } ``` - + ### Define Breadcrumbs Inside the View Make sure a ```$breadcrumbs``` variable is present: diff --git a/6.x/upgrade-guide.md b/6.x/upgrade-guide.md index 84866270..5a645cdb 100644 --- a/6.x/upgrade-guide.md +++ b/6.x/upgrade-guide.md @@ -153,7 +153,7 @@ CRUD::field([ Step 15. (OPTIONAL) If you have your `store()` or `update()` methods overriden just as callbacks, to do stuff when entries are `created` or `updated`, we have a suggestion for you that will clean up your code. Instead of overriding those methods, you can use Eloquent model events to achieve the same thing. See [the updated callbacks docs](/docs/6.x/crud-operation-create#callbacks) for all the options available. - + ### CSS & JS Assets Step 16. We have invented a whole new way of using CSS & JS assets in Laravel projects. We heavily recommend you use it too for you custom assets. Instead of installing assets using NPM, then minimizing and compiling them: diff --git a/7.x/base-breadcrumbs.md b/7.x/base-breadcrumbs.md index 1512ee39..dd5df40c 100644 --- a/7.x/base-breadcrumbs.md +++ b/7.x/base-breadcrumbs.md @@ -46,7 +46,7 @@ Notice the last item should NOT have a link, it should be ```false```. ## How to Define Breadcrumbs - + ### Define Breadcrumbs Inside the Controller Make sure a ```$breadcrumbs``` variable is present inside your views: @@ -68,7 +68,7 @@ Make sure a ```$breadcrumbs``` variable is present inside your views: } ``` - + ### Define Breadcrumbs Inside the View Make sure a ```$breadcrumbs``` variable is present: diff --git a/7.x/upgrade-guide.md b/7.x/upgrade-guide.md index 8a42718d..fe07ceb3 100644 --- a/7.x/upgrade-guide.md +++ b/7.x/upgrade-guide.md @@ -143,7 +143,7 @@ php artisan backpack:upgrade-dropzone Step 9.B. **EasyMDE Field** - The `easymde` field now also uses the `AjaxUploadOperation` to handle uploads. To secure the endpoint, we've introduced a new validation rule `ValidEasyMDE`. By default the endpoint will only allow images up to 1MB. If you want to use other file types or sizes, you MUST use the `ValidEasyMDE` rule in your FormRequest to validate the field. - + ### CSS & JS Assets All 3rd party dependencies have been updated to their latest versions. A lot of CSS & JS assets have suffered changes. Fortunately, thanks to Basset, we can easily clear the old files and get the new ones.