Ticket #1248: catch DoesNotExist errors with user.get_profile() when user does not have a corresponding Person record.
- Legacy-Id: 7178
Note: SVN reference [7151] has been migrated to Git commit d119b33a1a
changes to official proceedings generation code to support new agenda schema
- Legacy-Id: 7177
Note: SVN reference [7073] has been migrated to Git commit 35a94362a1
with a query for the appropriate event types, this should work now
that new events set the correct type and old events have been migrated
- Legacy-Id: 7140
doc/utils_charter.py) in favour of add_state_change_event which has
slightly better API but otherwise does basically the same except it
sets an event type we can later search for. Also expand tests slightly
to exercise three more templates.
- Legacy-Id: 7129
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
found with a simple error message, this mimicks the way the rest of the
Datatracker is handling missing files and avoids an annoying 404 when
running the test-crawler without all directories set up
- Legacy-Id: 7105
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
checking a StreamName against the slug, which happened to work with
MySQL because the stream name is the same as the slug, just uppercase
- but MySQL is case insensitive
- Legacy-Id: 7091
SimpleUrlTest tests to work with fake data and expand them a bit (they
are still pretty basic), rewrite the agenda editing tests to work with
the small generated fake data, delete those tests that are trivial or
only testing fixture facts as opposed to actually exercising the code,
combine some of them, expand most to actually check the returned JSON
and generally clean up the copy-paste mess of incorrect comments and
incorrect POST data.
At this point, no tests are using the real data base test machinery,
so one can run the full test suite with just
python manage.py test --settings=settings_sqlitetest
This takes about 72 seconds one a 2.4 GHz Intel Core 2. The
test-crawler and other real data tests take somewhat longer, though.
- Legacy-Id: 7069
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
