Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion cms/views.py
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
from urllib.parse import urljoin

LEGACY_PYTHON_DOMAIN = 'http://legacy.python.org'
PYPI_URL = 'https://pypi.python.org/'
PYPI_URL = 'https://pypi.org/'


def legacy_path(path):
Expand Down
2 changes: 1 addition & 1 deletion docs/source/administration.rst
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Administration
Navigation
----------

Navigation on the site is managed by the `Sitetree <https://pypi.python.org/pypi/django-sitetree>`_ application. The hierarchy should be fairly obvious. The biggest gotcha is when defining the URLs.
Navigation on the site is managed by the `Sitetree <https://pypi.org/pypi/django-sitetree>`_ application. The hierarchy should be fairly obvious. The biggest gotcha is when defining the URLs.

Many URLs are defined using `Django's URL system <https://docs.djangoproject.com/en/dev/topics/http/urls/>`_ however many are also simply defined as relative paths. When editing a particular item in the Sitetree in the *Additional Settings* fieldset there is an option named *URL as pattern*. If this option is checked the URL pattern is checked against the URLs defined by the Django applications. If it is left unchecked relative and absolute URLs can be entered.

Expand Down