Ticket #852 (closed task: fixed)
[M] Is trackback receiver working on latest deployed browse
Reported by: | spepler | Owned by: | lawrence |
---|---|---|---|
Priority: | blocker | Milestone: | PROD Step3 |
Component: | MOLES | Version: | |
Keywords: | Cc: |
Description
We tried to manually do a trackback to browse like this
and get Server internal error. This needs to be fixed to make CLADDIER tests work.
Change History
comment:1 Changed 14 years ago by lawrence
- Status changed from new to closed
- Resolution set to fixed
comment:2 Changed 14 years ago by spepler
- Status changed from closed to reopened
- Resolution fixed deleted
Tried this out. Still get an error.
produces the following
<response> <error>1</error> <message> Unable to forward trackback to designated recipient [Error sending mail ['module' object is not callable]] </message> </response>
This is a mail error from ows_server/controllers/trackback.py "Unable to forward trackback to designated recipient [Error sending mail "
The "object is not callable?" is from ows_server.lib.mailer.
I have run tests on the ows_server.lib.mailer and this seems to be working as a standalone function.
comment:3 Changed 14 years ago by spepler
I have found the problem and will add it to the SVN as soon as I have worked out how.
Note: See
TracTickets for help on using
tickets.
Strictly speaking we shouldn't support a trackback GET ... but for now we do ... The underlying bug(s) are fixed in changeset:2829, but note that when this installed on glue, trackbacks will start to be received by badc ... this can be changed in the ndgDiscovery file.