You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 7.x-dev/installation.md
+10-3Lines changed: 10 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,11 +5,11 @@
5
5
<aname="requirements"></a>
6
6
## Requirements
7
7
8
-
If you can run Laravel 10 or 11, you can install Backpack. Backpack does _not_ have additional requirements.
8
+
If you can run Laravel 12, you can install Backpack. Backpack does _not_ have additional requirements.
9
9
10
10
For the following process, we assume:
11
11
12
-
- you have a [working installation of Laravel](https://laravel.com/docs/11.x#installation) (an existing project is fine, you don't need a *fresh* Laravel install);
12
+
- you have a [working installation of Laravel](https://laravel.com/docs/12.x#installation) (an existing project is fine, you don't need a *fresh* Laravel install);
13
13
14
14
- you have configured your .ENV file with your database and mail information;
15
15
@@ -24,7 +24,14 @@ For the following process, we assume:
24
24
Go to your Laravel project's directory, then in your terminal, run:
25
25
26
26
```bash
27
-
composer require backpack/crud
27
+
# during beta, configure your Composer.json to accept unstable version, by running:
Copy file name to clipboardExpand all lines: 7.x-dev/release-notes.md
+60-25Lines changed: 60 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,34 +2,64 @@
2
2
3
3
---
4
4
5
-
**Planned launch date:**Dec 4th, 2024
5
+
**Planned launch date:**August 1st, 2025
6
6
7
-
For the past 2 years, we've done our very best to make all changes to Backpack in a backwards-compatible way. To not push a new version, because we know it's a pain in the bee's hind to upgrade stuff. But... it's time for a new release. Have no fear though, we've made this super easy for you.
7
+
For the past 2.5 years, we've done our very best to make all changes to Backpack in a backwards-compatible way. To not push a new version, because we know it's a pain to upgrade stuff. But... it's time for a new release. Have no fear though, we've made this super easy for you - and the new features & bug fixes are worth it!
8
8
9
-
Backpack v7 is a maintenance release. Yes, it does have a few breaking changes, but they will not impact 99.9% of projects. But that doesn't mean you shouldn't follow the upgrade guide! Please do - read it from top to bottom and make sure none of the changes impact you.
9
+
Here are the BIG things Backpack v7 brings to the table and why you should upgrade from [Backpack v6](/docs/6.x) to v7. But first... we should give credit where credit is due. **Big BIG thanks to our team: [Pedro Martins](https://github.com/pxpm), [Jorge Castro](https://github.com/jcastroa87)**, [Karan Datwani](https://github.com/karandatwani92)** and [Cristian Tabacitu](https://github.com/tabacitu) for working on this new version - and of course **our paying customers**, who have made all of this possible by supporting our work 🙏
10
10
11
-
Here are the BIG things Backpack v7 brings to the table and why you should upgrade from [Backpack v6](/docs/6.x) to v7. But first... we should give credit where credit is due. **Big BIG thanks to**:
12
-
-**[Pedro Martins](https://github.com/pxpm)** for x;
13
-
-**[Jorge Castro](https://github.com/jcastroa87)** for y;
14
-
-**[Karan Datwani](https://github.com/karandatwani92)** for z;
15
-
-**[Cristian Tabacitu](https://github.com/tabacitu)** for t;
16
-
-**our paying customers**, who have made all of this possible by supporting our work 🙏
17
-
18
-
Together, our team has put in an incredible amount of work to make v7 what it is - more than XXX commits, across YYY months, all while still maintaining, bug fixing and improving v6. Again, big thanks to everybody who has helped made this happen 🙏
11
+
Together, our team has put in an incredible amount of work to make v7 what it is - more than 1000 commits, across more than 8 months, all while still maintaining, bug fixing and improving v6. Again, big thanks to everybody who has helped made this happen - and of course, BIG thanks to our beta testers 🙏
19
12
20
13
<aname="added"></a>
21
14
## Added
22
15
23
-
### CRUD Lifecycle Hooks
16
+
### Data Components
24
17
25
-
Previously when working with Operations, developers found themselves needing to _override_ an entire operation method, in order to do things before/after the routes/defaults/operation is set up. This created a lot of duplicate code, and made it hard to maintain. Now, you can use CRUD Lifecycle Hooks to add your own code before/after each operation method. This is a much cleaner way to add your own code, without having to override the entire method. [Read more](/docs/{{version}}/crud-operations#lifecycle-hooks).
18
+
Our team has spend a lot of time and effort to make it possible to include the content of our main operations... anywhere you want. In the process, we've not only bent the laws of physics (ok maybe only PHP), but also made those operations _cleaner_.
19
+
20
+
#### Datatable component
21
+
22
+

23
+
24
+
You can now include a datatable anywhere you want! Just use the component in your custom views, custom pages or custom operations - it will pick up all the setup from your existing CrudController. [Read more](/docs/{{version}}/base-components#datatable-1).
25
+
26
+
#### Dataform component
27
+
28
+

29
+
30
+
You can now include a form anywhere you want! Same as the datatable - just use the component in your custom blade files, and it will pick up the fields from your CrudController. [Read more](/docs/{{version}}/base-components#dataform-component).
31
+
32
+
#### Datalist component
33
+
34
+

35
+
36
+
You can now use the content of the Show page for a particular entry... anywhere you want. It's as simple as loading the component and passing the CrudController. [Read more](/docs/{{version}}/base-components#datalist-component).
37
+
38
+
#### Datagrid component
39
+
40
+

41
+
42
+
Our previous design for the Show operation worked fine... but it wasn't pretty. We've developed an alternative comopnent, so that your Show operation looks a little better - just specify you want the show operation to use `datagrid` in your `config/backpack/operations/show.php`. Of course... you can also use it (you guessed it)... anywhere you want. It's as simple as loading the component and passing the CrudController. [Read more](/docs/{{version}}/base-components#datagrid-component).
26
43
27
-
### Two-Factor Authentication
44
+
### Chips
28
45
29
-
// TODO
46
+

30
47
31
-
### Re-Usable Filters
48
+
You know columns, you know fields - please welcome... chips! A chips helps show the information of a database entry, in a format that takes up little space visually. It can be used anywhere you want, but it's particularly useful inside the Show and List operations, to cram as much info as possible in as little space as possible. [Read more](/docs/{{version}}/crud-chips).
32
49
50
+
### Skins
51
+
52
+

53
+
54
+
It's been 2.5 years since we've adopted Tabler as our default HTML template - and in this time, we have only grown more fond of it. We are truly convinced that it's the best free Bootstrap template for admin panels, and our partnership and commitment has only grown. This new version of Backpack comes with a new feature inside our Tabler theme... skins.
55
+
56
+
Skins are a simple CSS file, that you can enable/not, to give your admin panel a completely different look. We're launching with one modern skin (that we call "non-liquid glass"). Soon enough, we'll follow up with a few more skins and... a way for you to _quickly_ create a custom skin, that will match your brand colors.
57
+
58
+
### CRUD Lifecycle Hooks
59
+
60
+
Previously when working with Operations, developers found themselves needing to _override_ an entire operation method, in order to do things before/after the routes/defaults/operation is set up. This created a lot of duplicate code, and made it hard to maintain. Now, you can use CRUD Lifecycle Hooks to add your own code before/after each operation method. This is a much cleaner way to add your own code, without having to override the entire method. [Read more](/docs/{{version}}/crud-operations#lifecycle-hooks).
61
+
62
+
### Re-usable Filters - Inside Custom Pages or Operations
@@ -39,29 +69,34 @@ Starting with this Backpack version, you can use the [filters](/docs/{{version}}
39
69
40
70
Filters can now be used inside [Custom Views for your List operation](https://backpackforlaravel.com/docs/{{version}}/crud-operation-list-entries#custom-views-for-listoperation-pro). This means once the admin has selected the Custom View, they can further drill down in the list, using the filters. But not only that... you can _remove_ the general filters and add entirely new filters, just for that Custom View.
41
71
42
-
### Browser Tests
43
-
44
-
// TODO
45
-
46
-
47
72
<aname="changed"></a>
48
73
## Changed
49
74
75
+
### New Versions for All Assets
76
+
77
+
We've bumped the version of ALL javascript and CSS assets we have, across the board. By upgrading to Backpack v7, you're automatically getting the best they have to offer - including Tabler, Bootstrap, Datatables etc.
78
+
50
79
### Uploaders
51
80
52
-
// TODO
81
+
We've ironed out all the quirks of Uploaders (and uploaders inside repeatables etc). This needed a few small breaking changes, but nothing that should affect you, if you haven't created custom uploaders. Try them again - they should all work fine now!
53
82
54
83
### Moved TinyMCE and CKEditor fields & columns
55
84
56
-
// TODO
85
+
We've moved the TinyMCE & CKeditor fields & columns from PRO to their own addons - released under open-source licenses. Please note that the underlying JS libraries are under GPLv2 license - which means you should not use them inside paid projects without purchasing a license from their respective creators.
57
86
58
87
### Basset
59
88
60
-
// TODO
89
+
A revolution in how easy it is to load CSS and JS assets in PHP, but we found out the hard way that making things easy is... _hard_. We're glad to tell you we've finally fixed most problems that came with Basset - and it's more reliable than ever. Additionally, you can now:
90
+
- name your assets, to easily use the same asset in multiple places;
91
+
- publish the assetmap, to override assets from vendor packages;
92
+
- use Basset on localhost (to code without an internet connection);
93
+
- store your assets in Git, so there's zero need to run basset in production;
94
+
95
+
For more information, check out [the docs for Basset's next version](https://github.com/Laravel-Backpack/basset/tree/next).
Copy file name to clipboardExpand all lines: 7.x-dev/upgrade-guide.md
+24-22Lines changed: 24 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,8 @@
4
4
5
5
This will guide you to upgrade from Backpack v6 to v7. The steps are color-coded by the probability that you will need it for your application: <spanclass="badge badge-danger text-white"style="text-decoration: none;">High</span>, <spanclass="badge badge-warning text-white"style="text-decoration: none;">Medium</span> and <spanclass="badge badge-secondary-soft"style="text-decoration: none;">Low</span>. **At the very least, please read what's in bold**.
6
6
7
+
> IMPORTANT NOTE: This upgrade guide is NOT AT ALL final. We do not recommend you upgrade your existing project to v7. We're working on making the upgrade process easier for you. We will let you know when this changes.
8
+
7
9
<aname="requirements"></a>
8
10
## Requirements
9
11
@@ -26,37 +28,37 @@ Please make sure your project respects the requirements below, before you start
26
28
<aname="upgraade-steps"></a>
27
29
## Upgrade Steps
28
30
29
-
<aname="step-0"href="#step-0"class="badge badge-danger"style="text-decoration: none;">Step 0.</a> **[Upgrade to Laravel 11](https://laravel.com/docs/11.x/upgrade) if you don't use it yet, then test to confirm your app is working fine.**
31
+
<aname="step-0"href="#step-0"class="badge badge-danger"style="text-decoration: none;">Step 0.</a> **[Upgrade to Laravel 12](https://laravel.com/docs/12.x/upgrade) if you don't use it yet, then test to confirm your app is working fine.**
30
32
31
33
<aname="composer"></a>
32
34
### Composer
33
35
34
36
<aname="step-1"href="#step-1"class="badge badge-danger text-white"style="text-decoration: none;">Step 1.</a> Update your ```composer.json``` file to require:
35
37
36
38
```
37
-
"backpack/crud": "v7-dev",
39
+
"backpack/crud": "^7.0@dev",
38
40
```
39
41
40
42
<aname="step-2"href="#step-2"class="badge badge-danger text-white"style="text-decoration: none;">Step 2.</a> Bump the version of any first-party Backpack add-ons you have installed (eg. `backpack/pro`, `backpack/editable-columns` etc.) to the versions that support Backpack v6. For 3rd-party add-ons, please check each add-on's Github page. Here's a quick list of 1st party packages and versions:
41
43
42
44
```js
43
-
"backpack/crud":"v7-dev",
44
-
"backpack/pro":"v3-dev",
45
-
"backpack/filemanager":"^3.0",
46
-
"backpack/theme-coreuiv2":"^1.0",
47
-
"backpack/theme-coreuiv4":"^1.0",
48
-
"backpack/theme-tabler":"^1.0",
49
-
"backpack/logmanager":"^5.0",
50
-
"backpack/settings":"^3.1",
51
-
"backpack/newscrud":"^5.0",
52
-
"backpack/permissionmanager":"^7.0",
53
-
"backpack/pagemanager":"^3.2",
54
-
"backpack/menucrud":"^4.0",
55
-
"backpack/backupmanager":"^5.0",
56
-
"backpack/editable-columns":"^3.0",
57
-
"backpack/revise-operation":"^2.0",
58
-
"backpack/medialibrary-uploaders":"^1.0",
59
-
"backpack/devtools":"^2.0",
45
+
"backpack/crud":"dev-next",
46
+
"backpack/pro":"dev-next",
47
+
"backpack/filemanager":"dev-next",
48
+
"backpack/theme-coreuiv2":"dev-next",
49
+
"backpack/theme-coreuiv4":"dev-next",
50
+
"backpack/theme-tabler":"dev-next",
51
+
"backpack/logmanager":"dev-next",
52
+
"backpack/settings":"dev-next",
53
+
"backpack/newscrud":"dev-next",
54
+
"backpack/permissionmanager":"dev-next",
55
+
"backpack/pagemanager":"dev-next",
56
+
"backpack/menucrud":"dev-next",
57
+
"backpack/backupmanager":"dev-next",
58
+
"backpack/editable-columns":"dev-next",
59
+
"backpack/revise-operation":"dev-next",
60
+
"backpack/medialibrary-uploaders":"dev-next",
61
+
"backpack/devtools":"dev-next",
60
62
```
61
63
62
64
<aname="step-3"href="#step-3"class="badge badge-danger text-white"style="text-decoration: none;">Step 3.</a> Let's get the latest Backpack and install it. If you get any conflicts with **Backpack 1st party add-ons**, most of the time you just need to move one version up, eg: from `backpack/menucrud: ^3.0` to `backpack/menucrud: ^4.0`. See the step above again. Please run:
@@ -109,10 +111,10 @@ No changes needed.
109
111
<aname="views"></a>
110
112
### Views
111
113
112
-
**List Operation View** - The List Operation view got a huge change. We decoupled the datatable from the view, so that you can use the table anywhere you would like.
113
-
Most of the code is still identical but moved to `datatable.blade.php`. The `list.blade.php` view now only includes the mentioned datatable component.
114
+
**List Operation View** - The List Operation view got a huge change. We decoupled the datatable from the view, so that you can use the table anywhere you would like.
115
+
Most of the code is still identical but moved to `datatable.blade.php`. The `list.blade.php` view now only includes the mentioned datatable component.
114
116
115
-
If you had customized the `list.blade.php` you should move your customizations to `datatable.blade.php`.
117
+
If you had customized the `list.blade.php` you should move your customizations to `datatable.blade.php`.
0 commit comments