- Legacy-Id: 10255
Note: SVN reference [10158] has been migrated to Git commit 4ac99a9dc4
Note: SVN reference [10253] has been migrated to Git commit 083abf7516
Summary: Add a view for /doc/foo-bar-baz that tries to redirect
helpfully instead of just throwing a 404 in case in an inexact match.
Right now, it knows how to do prefix matches and handles revisions and
extensions. If it can't find a unique match, it redirects to the
search page.
Branch
- Legacy-Id: 10253
Note: SVN reference [10158] has been migrated to Git commit 4ac99a9dc4
This fixes Javascript widgets working with DocAliases, such as the
replaces field in draft submission, to work better with Javascript
disabled. It also makes sense from a modelling perspective as the name
really is a unique key for the alias.
The actual transformation requires a series of migrations taking a
couple of minutes to complete. The actual switch to the key is done at
the end.
- Legacy-Id: 10251
Note: SVN reference [10111] has been migrated to Git commit 8bca1b4b33
Fix an initialization problem for the new work message for recharters.
- Legacy-Id: 10225
Note: SVN reference [10218] has been migrated to Git commit f9e35662e5
helpfully instead of just throwing a 404 in case in an inexact match.
Right now, it knows how to do prefix matches and handles revisions and
extensions. If it can't find a unique match, it redirects to the
search page.
Branch ready for merge.
- Legacy-Id: 10158
settings.URL_REGEXPS, partly to cleanup the urls.py files, partly to
make sure that all URL patterns agree on what constitutes a name
- Legacy-Id: 10114
This fixes Javascript widgets working with DocAliases, such as the
replaces field in draft submission, to work better with Javascript
disabled. It also makes sense from a modelling perspective as the name
really is a unique key for the alias.
The actual transformation requires a series of migrations taking a
couple of minutes to complete. The actual switch to the key is done at
the end.
Branch ready for merge.
- Legacy-Id: 10111
The new API requires at least one event and will automatically save a
snapshot of the document and related state. Document.save() will now
throw an exception if called directly, as the new API is intended to
ensure that documents are saved with both an appropriate snapsnot and
relevant history log, both of which are easily defeated by just
calling .save() directly.
To simplify things, the snapshot is generated after the changes to a
document have been made (in anticipation of coming changes), instead
of before as was usual.
While revising the existing code to work with this API, a couple of
missing events was discovered:
- In draft expiry, a "Document has expired" event was only generated
in case an IESG process had started on the document - now it's
always generated, as the document changes its state in any case
- Synchronization updates like title and abstract amendmends from the
RFC Editor were silently (except for RFC publication) applied and
not accompanied by a descriptive event - they now are
- do_replace in the Secretariat tools now adds an event
- Proceedings post_process in the Secretariat tools now adds an event
- do_withdraw in the Secretariat tools now adds an event
A migration is needed for snapshotting all documents, takes a while to
run. It turns out that a single document had a bad foreign key so the
migration fixes that too.
- Legacy-Id: 10101
