| Summary: | Error trying to approve a contact | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Community | Reporter: | Donald Smith <donald.smith> | ||||||
| Component: | Project Management & Portal | Assignee: | Bjorn Freeman-Benson <bjorn.freeman-benson> | ||||||
| Status: | CLOSED FIXED | QA Contact: | |||||||
| Severity: | blocker | ||||||||
| Priority: | P2 | CC: | bjorn.freeman-benson, gabe.obrien | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Donald Smith
Created attachment 97224 [details]
Before error.
Created attachment 97225 [details]
Error.
Coded, checked in. Waiting to go live. Defect introduced by bug 204838 Released in STAGING_201 Sorry, still getting the same error trying to update a pending contact change. Will this fix work for all new contact changes, or should it work on those that are still pending? In other words, is this just a case where we need to manually approve the one already in the DB? - Don Sorry - just realized this is still in stanging and not pushed yet. - Don (In reply to comment #6) No, you're just confused by our terminology. STAGING_nnn is our source code control tag - if we say say "released in STAGING_nnn" it means that that tag (misnamed STAGING_nnn) has been release to production. So it should have fixed the problem. We're looking into it. Coded (fixed, again) and checked-in. Waiting for release to production. Sorry Donald. Released in STAGING_205 where code was required to be released. Closed otherwise. Please see final comments and resolution for actual bug status. Sorry, still does not work. When I click "+1 approve" then "save" I get this error: SQL Trouble: Unknown column 'Oranizations.OrganizationID' in 'where clause' - Don We're certainly learning some embarrassing limitations of our testing framework here :-( Coded, tested (again), and checked in. Will go live soon. Cause: the testing framework does not use the object factory with "create one object" function. The code worked correctly for id = null, but not if id != null. But the testing framework does not test the id != null case for any of our factories. That's not good. Bjorn, Shouldn't a bug be opened about this limitation of the test framework so we can track and fix it? gO' Released in STAGING_209. See actual comments and bug resolution for real status of this bug. This message does not construe any meaning not already mentioned. |