Auto-remapped old django docs to new version. Resolve #3126

docs/source/Components/Signals.md

@@ -15,7 +15,7 @@ you can "attach" any number of event-handlers to these signals. You can attach
 any number of handlers and they'll all fire whenever any entity triggers the
 signal.
 
-Evennia uses the [Django Signal system](https://docs.djangoproject.com/en/2.2/topics/signals/).
+Evennia uses the [Django Signal system](https://docs.djangoproject.com/en/4.1/topics/signals/).
 
 
 ## Working with Signals

docs/source/Components/Tags.md

@@ -119,7 +119,7 @@ with a given Tag like this in code:
 
 > Note that searching for just "furniture" will only return the objects tagged with the "furniture" tag that has a category of `None`. We must explicitly give the category to get the "luxurious" furniture. 
 
-Using any of the `search_tag` variants will all return [Django Querysets](https://docs.djangoproject.com/en/2.1/ref/models/querysets/), including if you only have one match. You can treat querysets as lists and iterate over them, or continue building search queries with them.
+Using any of the `search_tag` variants will all return [Django Querysets](https://docs.djangoproject.com/en/4.1/ref/models/querysets/), including if you only have one match. You can treat querysets as lists and iterate over them, or continue building search queries with them.
 
 Remember when searching that not setting a category means setting it to `None` - this does *not*
 mean that category is undefined, rather `None` is considered the default, unnamed category.

docs/source/Components/Typeclasses.md

@@ -34,7 +34,7 @@ This is how the inheritance looks for the typeclasses in Evennia:
                                                          └────┘
 ```
 
-- **Level 1** above is the "database model" level. This describes the database tables and fields (this is technically a [Django model](https://docs.djangoproject.com/en/2.2/topics/db/models/)).
+- **Level 1** above is the "database model" level. This describes the database tables and fields (this is technically a [Django model](https://docs.djangoproject.com/en/4.1/topics/db/models/)).
 - **Level 2** is where we find Evennia's default implementations of the various game entities, on top of the database. These classes define all the hook methods that Evennia calls in various situations. `DefaultObject` is a little special since it's the parent for `DefaultCharacter`, `DefaultRoom` and `DefaultExit`. They are all grouped under level 2 because they all represents defaults to build from.
 - **Level 3**, finally, holds empty template classes created in your game directory. This is the level you are meant to modify and tweak as you please, overloading the defaults as befits your game. The templates inherit directly from their defaults, so `Object` inherits from `DefaultObject` and `Room` inherits from `DefaultRoom`.
 
@@ -190,7 +190,7 @@ Most of the time you search for objects in the database by using convenience met
 `caller.search()` of [Commands](./Commands.md) or the search functions like `evennia.search_objects`.
 
 You can however also query for them directly using [Django's query
-language](https://docs.djangoproject.com/en/1.7/topics/db/queries/). This makes use of a _database
+language](https://docs.djangoproject.com/en/4.1/topics/db/queries/). This makes use of a _database
 manager_ that sits on all typeclasses, named `objects`. This manager holds methods that allow
 database searches against that particular type of object (this is the way Django normally works
 too). When using Django queries, you need to use the full field names (like `db_key`) to search:
@@ -294,7 +294,7 @@ The arguments to this method are described [in the API docs here](github:evennia
 
 *This is considered an advanced section.*
 
-Technically, typeclasses are [Django proxy models](https://docs.djangoproject.com/en/1.7/topics/db/models/#proxy-models).  The only database
+Technically, typeclasses are [Django proxy models](https://docs.djangoproject.com/en/4.1/topics/db/models/#proxy-models).  The only database
 models that are "real" in the typeclass system (that is, are represented by actual tables in the database) are `AccountDB`, `ObjectDB`, `ScriptDB` and `ChannelDB` (there are also [Attributes](./Attributes.md) and [Tags](./Tags.md) but they are not typeclasses themselves). All the subclasses of them are "proxies", extending them with Python code without actually modifying the database layout.
 
 Evennia modifies Django's proxy model in various ways to allow them to work without any boiler plate (for example you don't need to set the Django "proxy" property in the model `Meta` subclass, Evennia handles this for you using metaclasses). Evennia also makes sure you can query subclasses as well as patches django to allow multiple inheritance from the same base class.

docs/source/Components/Web-Admin.md

@@ -1,6 +1,6 @@
 # The Web Admin
 
-The Evennia _Web admin_ is a customized [Django admin site](https://docs.djangoproject.com/en/3.2/ref/contrib/admin/)
+The Evennia _Web admin_ is a customized [Django admin site](https://docs.djangoproject.com/en/4.1/ref/contrib/admin/)
 used for manipulating the game database using a graphical interface. You
 have to be logged into the site to use it. It then appears as an `Admin` link
 the top of your website. You can also go to [http://localhost:4001/admin](http://localhost:4001/admin) when
@@ -113,7 +113,7 @@ the `Can delete Account` permission, for example.
 ## Customizing the web admin
 
 Customizing the admin is a big topic and something beyond the scope of this
-documentation. See the [official Django docs](https://docs.djangoproject.com/en/3.2/ref/contrib/admin/) for
+documentation. See the [official Django docs](https://docs.djangoproject.com/en/4.1/ref/contrib/admin/) for
 the details. This is just a brief summary.
 
 See the [Website](./Website.md) page for an overview of the components going into

docs/source/Components/Website.md

@@ -162,7 +162,7 @@ Some important things to know:
 
 This allows for template inheritance (making it easier to make all pages look the same without rewriting the same thing over and over)
 
-There's a lot more information to be found in the [Django template language documentation](https://docs.djangoproject.com/en/3.2/ref/templates/language/).
+There's a lot more information to be found in the [Django template language documentation](https://docs.djangoproject.com/en/4.1/ref/templates/language/).
 
 ### Change webpage colors and styling
 
@@ -242,7 +242,7 @@ urlpatterns = [
 
 So we just import `index` from the new location and point to it. After a reload the front page will now redirect to use your copy rather than the original.
 
-The frontpage view is a class `EvenniaIndexView`. This is a [Django class-based view](https://docs.djangoproject.com/en/3.2/topics/class-based-views/). It's a little less visible what happens in a class-based view than in a function (since the class implements a lot of functionality as methods), but it's powerful and much easier to extend/modify.
+The frontpage view is a class `EvenniaIndexView`. This is a [Django class-based view](https://docs.djangoproject.com/en/4.1/topics/class-based-views/). It's a little less visible what happens in a class-based view than in a function (since the class implements a lot of functionality as methods), but it's powerful and much easier to extend/modify.
 
 The class property `template_name` sets the location of the template used under the `templates/` folder. So `website/index.html` points to `web/templates/website/index.html` (as we already explored above. 
 
@@ -283,7 +283,7 @@ Let's see how to make a `/test/` page from scratch.
 
 - Add a new `test.html` file under `mygame/web/templates/website/`. Easiest is to base this off an existing file. Make sure to `{% extend base.html %}` if you want to get the same styling as the rest of your site.
 - Add a new view `testview.py` under `mygame/web/website/views/` (don't name it `test.py` or
-  Django/Evennia will think it contains unit tests). Add a view there to process your page. This is a minimal view to start from (read much more [in the Django docs](https://docs.djangoproject.com/en/3.2/topics/class-based-views/)):
+  Django/Evennia will think it contains unit tests). Add a view there to process your page. This is a minimal view to start from (read much more [in the Django docs](https://docs.djangoproject.com/en/4.1/topics/class-based-views/)):
 
     ```python
     # mygame/web/website/views/testview.py
@@ -326,7 +326,7 @@ Firstly, this must be represented in HTML. The `<form> ... </form>` is a
 standard HTML element you need to add to your template. It also has some other
 requirements, such as `<input>` and often Javascript components as well (but
 usually Django will help with this). If you are unfamiliar with how HTML forms
-work, [read about them here](https://docs.djangoproject.com/en/3.2/topics/forms/#html-forms).
+work, [read about them here](https://docs.djangoproject.com/en/4.1/topics/forms/#html-forms).
 
 The basic gist of it is that when you click to 'submit' the form, a POST HTML
 request will be sent to the server containing the data the user entered. It's
@@ -334,11 +334,11 @@ now up to the server to make sure the data makes sense (validation) and then
 process the input somehow (like creating a new character).
 
 On the backend side, we need to specify the logic for validating and processing
-the form data. This is done by the `Form` [Django class](https://docs.djangoproject.com/en/3.2/topics/forms/#forms-in-django).
+the form data. This is done by the `Form` [Django class](https://docs.djangoproject.com/en/4.1/topics/forms/#forms-in-django).
 This specifies _fields_ on itself that define how to validate that piece of data.
 
 The form is then linked into the view-class by adding `form_class = MyFormClass` to
 the view (next to `template_name`).
 
 There are several example forms in `evennia/web/website/forms.py`. It's also a good
-idea to read [Building a form in Django](https://docs.djangoproject.com/en/3.2/topics/forms/#building-a-form-in-django) on the Django website - it covers all you need.
+idea to read [Building a form in Django](https://docs.djangoproject.com/en/4.1/topics/forms/#building-a-form-in-django) on the Django website - it covers all you need.