bemoody

@tompollard @li-lcp This is the issue I mentioned earlier today. Notice that NewProjectVersionForm does not set order when creating References. That's a serious problem, and would have been apparent if...

Also notice that /projects/X/preview/ (and /content/X/) is sorted by `order`, while /projects/X/content/ is apparently sorted by `id`. (See BaseModelFormSet.get_queryset in django/forms/models.py)

I did start trying to fix this but I didn't see an easy way to address the existing broken projects. There is no way for us to know automatically whether...

Okay, I'm guessing I know what happened with `chexchonet 1.0.0`, `mimic-iv-fhir 1.0`, and `physiotag 1.0.0`. It looks like `edit_content_item` does not change order of existing references when it deletes a...

Current plan: - Make a data migration to fix 75% of the existing broken projects. - Ensure that projects with undefined/inconsistent reference order cannot be submitted/published. - If project has...

- Fix reference order of demo projects.

- Change unique_together to `[('description', 'project')]`: forbid duplicate descriptions as was originally intended; ignore order.

- Use `id` order in the preview page, to match the content page and reduce confusion.

Key rotation finally became an officially supported feature in Django 4.1, so we just have to turn it on. Probably everything should just work unless we have code that directly...

chardet also wants to classify `\xc2\xa0` as Latin-1 (LATIN CAPITAL LETTER A WITH CIRCUMFLEX, NO-BREAK SPACE) rather than UTF-8 (NO-BREAK SPACE). Not that people should typically be using no-break spaces,...