Closed marshalc closed 7 years ago
A series of 6 errors this morning, with either S/AE 670 or 577 and Laurent Weekers as the user.
Local testing shows that when logged in as Laurent, this error is generated when trying to edit (view works fine) the S/AE.
Investigating...
It's possible they were trying to get in to update the contact details for the event...
From: l.weekers@chu.ulg.ac.be [mailto:l.weekers@chu.ulg.ac.be]
Sent: 18 September 2017 16:02
To: COPE DB <no-reply@cope.nds.ox.ac.uk>
Cc: Jacques Pirenne <jacques.pirenne@uzleuven.be>; Ina Jochmans <ina.jochmans@uzleuven.be>; sarah mertens <sarah.mertens@uzleuven.be>; Ally Bradley <ally.bradley@nds.ox.ac.uk>; j monard <j.monard@chu.ulg.ac.be>
Subject: Re: Serious Adverse Event Updated - WP445003L
Could you please put Mrs J.Monard in copy of this mails since she is charge for encoding this information in our center ?
Than you
Dr. Laurent WEEKERS
Néphrologie-Transplantation
CHU Sart-Tilman B35
4000 Liège
Ligne Directe: +32(0)4.284.45.20. (Sart-Tilman)
Secrétariat: +32(0)4.270.31.43.
Fax: +32(0)4.270.31.71. (NDB)
+32(0)4.366.83.37 (Sart-Tilman)
----- Original Message -----
From: "COPE DB" <no-reply@cope.nds.ox.ac.uk>
To: "Jacques Pirenne" <jacques.pirenne@uzleuven.be>, "ina jochmans" <ina.jochmans@uzleuven.be>, "sarah mertens" <sarah.mertens@uzleuven.be>, "WEEKERS Laurent" <L.Weekers@chu.ulg.ac.be>
Cc: "ally bradley" <ally.bradley@nds.ox.ac.uk>
Sent: Monday, September 18, 2017 3:35:35 PM
Subject: Serious Adverse Event Updated - WP445003L
Visit https://cope.nds.ox.ac.uk/en-gb/wp4/adverse-event/577/details/ for more details. The Local Investigator is Laurent Weekers and has been emailed at L.Weekers@chu.ulg.ac.be.
Email forwarded from Ally, since Laurent did not notice the "no-reply" in the email address to cope.
Fixed: Missing a form_class
definition from AdverseEventUpdateView
- this was hidden for admin/staff users because of an override put in place for categorisation of events.
Code rebranched into a 0.8.5 branch, and merged with test (so now deployed on test server). There was a bit of a moment where the test server was showing 502 errors, but then it cleared up with no apparent intervention from me, so I'm wondering if there was some server configuration going on on the shared host (though nothing in the status blog about it). At the time of writing the Test Server is running the 0.8.5 release... I'll try and do a production release in the morning.
0.8.5 released to production with this fix in it now.