test crawler from going to /account/login/ and getting an error back,
with this change the crawler currently runs without reporting any
errors
- Legacy-Id: 7114
intended std level and consensus is not filled in for the draft before
sending it (as per discussion with Alice Russo) - the consensus check
is skipped for ISE drafts
- Legacy-Id: 7103
out nomcom.js is included in the wrong pages, and on the pages it is
actually useful in, it's obsolete, so delete it together with the
obsoleted AJAX view and the other JS left-over cruft in nomcom/, this
fixes an include 404 and removes the remaining dependency on
jquery-1.5.1 apart from the Secretariat tools
- Legacy-Id: 7097
meeting AJAX code is using PUT instead of POST (even if it's not
PUT'ing in the literal sense but POST'ing). Theoretical discussions
aside, Django has poor support for PUTs turned POSTs so rewriting them
removes the need for a couple of hacks, and makes it easier to test.
- Legacy-Id: 7067
Script to run from cron to send daily messages to IETF Announce showing the email header field change.
This should be run from Jan 6 to Jan 20, after which point we need to deploy analagous changes to the code that constructs last call announcements.
This is related to bug #811
Commit ready for merge.
- Legacy-Id: 6952
Note: SVN reference [6857] has been migrated to Git commit c500184eee
Adds pages to show what a given document refers to and what refers to it.
Fixes bug #1194
commit ready for merge
- Legacy-Id: 6951
Note: SVN reference [6701] has been migrated to Git commit d19967ac93
This should be run from Jan 6 to Jan 20, after which point we need to deploy analagous changes to the code that constructs last call announcements.
This is related to bug #811
Commit ready for merge.
- Legacy-Id: 6857
script includes are put in the "js" block rather than the "scripts"
block, the latter is for inline scripts, not script includes (this
fixes a couple of weird syntax errors)
- Legacy-Id: 6815
duplicated code, make sure the custom form widgets escape their input.
There's still a bit of custom proxying going on in the IETFHM class
hierarchy.
- Legacy-Id: 6794
message to use https: instead of http:. This is generally a good idea, and
also silences Google Chrome's phishing warning. Fixes issue #1204.
This commit should have contained only changes to a template file; by
mistake, changes to two django files were also committed here. That
change has been undone in [6725].
- Legacy-Id: 6724
Note: SVN reference [6725] has been migrated to Git commit ca1a04f660aa0473bf8f3aadc7809d462ac4cac0
- Rename IdSubmissionDetail to Submission
- Rename various submission fields to correspond to the conventions in
the new schema
- Use a name model for the states instead of IdSubmissionStatus
- Drop the TempIdAuthor model which is based on splitting up author
names
- Add a simple textual SubmissionEvent for tracking events in the
lifetime of a submission
- Delete a bunch of obsolete fields
- Make sure all submission have an access key so we can depend on it
- Add state for when approval is needed from previous authors
A couple of migrations take care of transforming the
IdSubmissionDetail and moving data over/cleaning it up.
Also revamp the submit view code:
- Make form code do validation/cleaning only so there's a clear
separation of concerns
- Reduce uses of inheritance that made the code hard to follow -
forms now don't inherit from each other, views don't call each other
but instead reuse common utilities, templates share CSS/utilities
instead of relying on inheritance
- Move email rendering/sending to separate file
- Drop the in-grown terminology use (auto post vs. manual posts)
- Make the status page explain who is emailed for what purpose
- Add history table with recorded events
- Make the status page handle its post actions by itself instead of
duplicating most of the setup logic in a number of simple views
- Fix a couple of minor bugs and handle some edge cases better
- Expand tests with a couple of more cases
Possibly the submit tool could still use more help text added to
explain the process, ideally what's explained in the tool instructions
page should be inlined or self-evident.
- Legacy-Id: 6714
