Show More
| @@ -29,12 +29,13 b' to make a backup of your configuration f' | |||||
| 29 | content after the automerge. |
|
29 | content after the automerge. | |
| 30 |
|
30 | |||
| 31 | .. note:: |
|
31 | .. note:: | |
| 32 | The next steps only apply to upgrading from non bugfix releases eg. from |
|
32 | Please always make sure your .ini files are upto date. Often errors are | |
| 33 | any minor or major releases. Bugfix releases (eg. 1.1.2->1.1.3) will |
|
33 | caused by missing params added in new versions. | |
| 34 | not have any database schema changes or whoosh library updates. |
|
34 | ||
| 35 |
|
35 | |||
| 36 | It is also recommended that you rebuild the whoosh index after upgrading since |
|
36 | It is also recommended that you rebuild the whoosh index after upgrading since | |
| 37 | the new whoosh version could introduce some incompatible index changes. |
|
37 | the new whoosh version could introduce some incompatible index changes. Please | |
|
|
38 | Read the changelog to see if there were any changes to whoosh. | |||
| 38 |
|
39 | |||
| 39 |
|
40 | |||
| 40 | The final step is to upgrade the database. To do this simply run:: |
|
41 | The final step is to upgrade the database. To do this simply run:: | |
General Comments 0
You need to be logged in to leave comments.
Login now