|
3
|
1 |
How to update your bundle ? |
|
|
2 |
=========================== |
|
|
3 |
|
|
|
4 |
This document explains how to upgrade from one FOSUSerBundle version to |
|
|
5 |
the next one. It only discusses changes that need to be done when using |
|
|
6 |
the "public" API of the bundle. If you "hack" the core, you should probably |
|
|
7 |
follow the timeline closely anyway. |
|
|
8 |
|
|
|
9 |
* The methods relative to the groups have been removed from `FOS\UserBundle\Model\UserInterface` |
|
|
10 |
and a new `FOS\UserBundle\Model\GroupableInterface` has been added (implemented |
|
|
11 |
by `FOS\UserBundle\Model\User`). |
|
|
12 |
|
|
|
13 |
* The User class of the bundle does not contain the timestampable fields anymore |
|
|
14 |
as they were not used by the bundle. |
|
|
15 |
|
|
|
16 |
* The `fos:user:changePassword` command has been renamed to `fos:user:change-password`. |
|
|
17 |
|
|
|
18 |
* The way to configure the forms has been refactored to give more flexibility: |
|
|
19 |
|
|
|
20 |
* The configuration of the type now accepts the name of the type. You can |
|
|
21 |
register your own type by creating a tagged service in the container: |
|
|
22 |
|
|
|
23 |
<tag name="form.type" alias="acme_custom_type" /> |
|
|
24 |
|
|
|
25 |
* The configuration of the handler now accepts a service id. |
|
|
26 |
|
|
|
27 |
* The form classes have been moved to subnamespaces to keep them organized. |
|
|
28 |
|
|
|
29 |
* The ACL implementation using JMSSecurityExtraBundle which was broken |
|
|
30 |
since Symfony beta2 has been removed. |
|
|
31 |
|
|
|
32 |
* The Twig block has been renamed from `content` to `fos_user_content`. |