Briq
/
django-polymorphic
6
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merge pull request #223 from adamchainz/readthedocs.io 

Convert readthedocs links for their .org -> .io migration for hosted projects
fix_request_path_info
Diederik van der Boor 2016-06-16 13:25:30 +02:00 committed by GitHub
parent b1f037dd68 9abb56a7a6
commit ede30f0c7a
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.rst
View File

@ -52,7 +52,7 @@ Django to perform an ``INNER JOIN`` to fetch the model fields from the database.
While taking this in mind, there are valid reasons for using subclassed models. While taking this in mind, there are valid reasons for using subclassed models.
That's what this library is designed for! That's what this library is designed for!
For more information, see the `documentation at Read the Docs <https://django-polymorphic.readthedocs.org/>`_. For more information, see the `documentation at Read the Docs <https://django-polymorphic.readthedocs.io/>`_.
License License
======= =======

2
docs/third-party.rst
View File

@ -10,7 +10,7 @@ However, they require more setup than standard models. That's become:
* The children models are not registered in the admin site. * The children models are not registered in the admin site.
You will therefore need to manually register them to django-reversion_. You will therefore need to manually register them to django-reversion_.
* Polymorphic models use `multi-table inheritance <https://docs.djangoproject.com/en/dev/topics/db/models/#multi-table-inheritance>`_. * Polymorphic models use `multi-table inheritance <https://docs.djangoproject.com/en/dev/topics/db/models/#multi-table-inheritance>`_.
See the `reversion documentation <http://django-reversion.readthedocs.org/en/latest/api.html#multi-table-inheritance>`_ See the `reversion documentation <https://django-reversion.readthedocs.io/en/latest/api.html#multi-table-inheritance>`_
how to deal with this by adding a ``follow`` field for the primary key. how to deal with this by adding a ``follow`` field for the primary key.
* Both admin classes redefine ``object_history_template``. * Both admin classes redefine ``object_history_template``.