mirror of
https://github.com/inventree/inventree-website.git
synced 2025-06-17 04:25:26 +00:00
Fix docs links to point to stable (not latest) (#228)
This commit is contained in:
@ -19,7 +19,7 @@ You should also refer to the [Django 4.2 release notes](https://docs.djangoproje
|
||||
|
||||
### Site Access Changes
|
||||
|
||||
Django 4.2 has introduced some changes to how cross-site protection is handled. Your existing InvenTree installation may require some changes to continue to operate as expected. In particular, the `CORS` and `CSRF` settings have been made more strict by default. Refer to the [server access configuration guide](https://docs.inventree.org/en/latest/start/config/#server-access) for instructions on which settings will need to be updated.
|
||||
Django 4.2 has introduced some changes to how cross-site protection is handled. Your existing InvenTree installation may require some changes to continue to operate as expected. In particular, the `CORS` and `CSRF` settings have been made more strict by default. Refer to the [server access configuration guide](https://docs.inventree.org/en/stable/start/config/#server-access) for instructions on which settings will need to be updated.
|
||||
|
||||
### Multi Site Support
|
||||
|
||||
@ -27,11 +27,11 @@ InvenTree has, by default, shipped with [multi site support](https://docs.django
|
||||
|
||||
So, in [PR 6390](https://github.com/inventree/InvenTree/pull/6390) we have disabled multi-site support by default. This should simplify the installation process for most users.
|
||||
|
||||
For any users who have been using multi-site support, you will need to manually re-enable it after upgrading to 0.14.0. Refer to the [InvenTree documentation](https://docs.inventree.org/en/latest/start/advanced/#multi-site-support) for more information.
|
||||
For any users who have been using multi-site support, you will need to manually re-enable it after upgrading to 0.14.0. Refer to the [InvenTree documentation](https://docs.inventree.org/en/stable/start/advanced/#multi-site-support) for more information.
|
||||
|
||||
### Test Results
|
||||
|
||||
InvenTree has long supported [test results for stock items](https://docs.inventree.org/en/latest/stock/test/). In [PR 6430](https://github.com/inventree/InvenTree/pull/6430), a significant enhancement was made to the test result system. Previously, test results were not linked to a specific test template in the database. Instead, the results and templates were loosely linked via a string key.
|
||||
InvenTree has long supported [test results for stock items](https://docs.inventree.org/en/stable/stock/test/). In [PR 6430](https://github.com/inventree/InvenTree/pull/6430), a significant enhancement was made to the test result system. Previously, test results were not linked to a specific test template in the database. Instead, the results and templates were loosely linked via a string key.
|
||||
|
||||
In 0.14.0, the test result system has been updated to use a proper database relationship between test results and test templates. This means that test results are now linked to a specific test template, and the test result system has been updated to reflect this change.
|
||||
|
||||
@ -79,7 +79,7 @@ A significant number of new features have been added to InvenTree in this releas
|
||||
|
||||
### Enhanced Validation
|
||||
|
||||
Enhanced custom validation is implemented in [PR 6410](https://github.com/inventree/InvenTree/pull/6410). This addition allows for more comprehensive validation of models by integrated plugins. Refer to the [updated validation plugin docs](https://docs.inventree.org/en/latest/extend/plugins/validation/) for more information.
|
||||
Enhanced custom validation is implemented in [PR 6410](https://github.com/inventree/InvenTree/pull/6410). This addition allows for more comprehensive validation of models by integrated plugins. Refer to the [updated validation plugin docs](https://docs.inventree.org/en/stable/extend/plugins/validation/) for more information.
|
||||
|
||||
### API Documentation
|
||||
|
||||
|
Reference in New Issue
Block a user