Mercurial > p > roundup > code
comparison doc/upgrading.txt @ 5068:5b2ce5723abb
Updated _generic.404.html to use the page template so 404 errors still
look like they are associated with the tracker.
Added a section header to updgrading.txt for an existing change in
release 1.6 since I added a new section.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Sun, 05 Jun 2016 10:54:08 -0400 |
| parents | 5251e97b1de0 |
| children | 487dc55e3c5e |
comparison
equal
deleted
inserted
replaced
| 5067:e424987d294a | 5068:5b2ce5723abb |
|---|---|
| 20 .. contents:: | 20 .. contents:: |
| 21 :local: | 21 :local: |
| 22 | 22 |
| 23 Migrating from 1.5.1 to 1.6.0 | 23 Migrating from 1.5.1 to 1.6.0 |
| 24 ============================= | 24 ============================= |
| 25 | |
| 26 Database back end specified in config.ini | |
| 27 -------------------- | |
| 25 | 28 |
| 26 The ``db/backend_name`` file is no longer used to configure the database | 29 The ``db/backend_name`` file is no longer used to configure the database |
| 27 backend being used for a tracker. The backend is now configured in the | 30 backend being used for a tracker. The backend is now configured in the |
| 28 ``config.ini`` file using the ``backend`` option located in the ``[rdbms]`` | 31 ``config.ini`` file using the ``backend`` option located in the ``[rdbms]`` |
| 29 section. For example if ``db/backend_name`` file contains ``sqlite``, a new | 32 section. For example if ``db/backend_name`` file contains ``sqlite``, a new |
| 41 you can safely delete the ``db/backend_name`` file. | 44 you can safely delete the ``db/backend_name`` file. |
| 42 | 45 |
| 43 Note: the ``backend_name`` file may be located in a directory other than | 46 Note: the ``backend_name`` file may be located in a directory other than |
| 44 ``db/`` if you have configured the ``database`` option in the ``[main]`` | 47 ``db/`` if you have configured the ``database`` option in the ``[main]`` |
| 45 section of the ``config.ini`` file to be something other than ``db``. | 48 section of the ``config.ini`` file to be something other than ``db``. |
| 49 | |
| 50 html/_generic.404.html in trackers use page template | |
| 51 -------------------- | |
| 52 | |
| 53 The original generic 404 error pages for many trackers did not use the | |
| 54 standard page layout. This change replaces the html/_generic.404.html | |
| 55 page with one that uses the page template. | |
| 56 | |
| 57 If your deployed tracker is based on: classic, minimal, responsive or | |
| 58 devel templates and has not changed the html/_generic.404.html file, | |
| 59 you can copy in the new file to get this additional functionality. | |
| 60 | |
| 46 | 61 |
| 47 Migrating from 1.5.0 to 1.5.1 | 62 Migrating from 1.5.0 to 1.5.1 |
| 48 ============================= | 63 ============================= |
| 49 | 64 |
| 50 User data visibility | 65 User data visibility |