644992 - GetPersonas.com "There was an error relocating the persona." error

Status: RESOLVED INVALID

(Websites Graveyard :: getpersonas.com, defect)

Description

[Deb Richardson [:dria] (plz NEEDINFO)]

I went back through the dashboard to approve a persona that had been mistakenly rejected (due to the dashboard not updating properly, but that's a different problem), but when I brought up the review page:

1) There were no images associated with the Persona, so there was no header/footer displayed

2) When I clicked "Accept" (just to test what happened), I go the "There was an error relocating the persona. Please contact [e-mail]" error.

This is a fairly significant issue since we end up occasionally rejecting Personas as duplicates when what has happened (due to the dashboard issue) is that we've just reviewed the same persona twice.

This is new/different behaviour.  I have no idea what might have happened to cause this.

Comment 1

[Matthew N. [:MattN]]

1) I think the images should have been displayed unless it was already approved.

2) This behaviour was added in bug 633290 to inform reviewers when the persona files could not be moved to the directory for approved personas when accepted.  It makes sure that the database record for the persona reflects the actual approved state in the database so we don't have the case that a persona is approved but the files are still in the pending directory.

Also, the rejection email would have been sent already and so if the system did let you approve it, another email would be sent.

I don't think this should have happened for the case of rejection followed by approval... it should only happen in the opposite case since after approval, the files are moved.

Comment 2

[Deb Richardson [:dria] (plz NEEDINFO)]

Ok, edge-casey enough that I'm just going to resolve/invalid this for now.  Will reopen if it happens again or becomes an issue.

Comment 3

[Vishal Kamdar [:vish_moz]]

This is happening again while approving personas.

Comment 4

[Matthew N. [:MattN]]

Marking INVALID since this is about an edge case on production while bug 633290 happens all the time on stage and is a different problem.