Bump Django version to 4.2

[jarosenb]

Overview

Bump Django version to 4.2 and fix compatibility issues.
This uses a new fork of djangocms-forms that updates imports to deal with Django 4 deprecations: https://github.com/TACC/djangocms-forms

Related

• required by Task/TUP-454: Upgrade to Django v4.2 tup-ui#324

Testing

1. docker-compose -f docker-compose.yml build
2. Run the CMS locally as per usual.

Notes

Repo Maintainer Notes

UI Demo is broken. That's expected, because of v3.12.0-beta.2. This branch is off of https://github.com/TACC/Core-CMS/releases/tag/v3.12.0-beta.2 (technically, off of two 006fc47, which is noop commits ahead of beta.2).
— @wesleyboar

[wesleyboar]

This is exciting.

Also, I only just noticed that the original fork recently begun Django 4 updates (avryhof/djangocms-forms#13).

Comparisons:

• src. fork: avryhof/djangocms-forms@master...django4
• TACC fork TACC/djangocms-forms@master...compat/django4

[wesleyboar]

We might not need the TACC fork, because the original fork has similar (and more) updates for Django 4. Excellent work though. The work of both is similar.

^{P.S. I prefer your use of as when importing to make a cleaner diff.}

[wesleyboar]

The original fork's dajngo4 branch has no PR, and no Issue. Gross. Also it is 63 commits ahead of upstream, while its master branch is 64 commits ahead. That's just weird. At least TACC's version is a commit on master. So, we stick with TACC, sure.

Only oddity of sticking with TACC is that the trail is unexpectedly long:

• https://github.com/mishbahr/djangocms-forms
  • https://github.com/avryhof/djangocms-forms
    • https://github.com/jarosenb/djangocms-forms
      • https://github.com/TACC/djangocms-forms

@jarosenb How about removing jarosenb link in the chain? Or make PR to avryhof/djangocms-forms?

[wesleyboar]

The Bootstrap revision worries me. I cannot find a paper trail.

[wesleyboar]

Re-review notes.

[wesleyboar]

Note
The merge of main (0992f47) means deploying this on TUP will also get unreleased changes. But, that should be okay, because the changes are docs, submodule, noop, and one new not-yet-enabled feature.

[wesleyboar]

Latest Issues:

1. Form submission failure. This is being investigated (private link).
2. Update djamgo-admin-style to latest to fix UI bugs (source).
3. Failure to create page on new local setup.

[wesleyboar]

CMS test went well. See (internal document) TUP Testing Session Django 4.2 Update - WMA.