Closed Bug 469899 Opened 16 years ago Closed 15 years ago

Developer reply to review without title is rejected; comes back escaped

Categories

(addons.mozilla.org Graveyard :: Public Pages, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: davemgarrett, Assigned: smccammon)

References

()

Details

Attachments

(1 file)

Just replied to a review and left the "title" field blank. It didn't like that and told me that the field is required, even though it isn't necessary normally. The body of the reply also came back with escaped quotes and newlines. (i.e. \', \n, etc.) It must not be unescaping it when it comes back to the reply page with the error message.
This problem still exists in current AMO (2/nov/2009)
Priority: -- → P3
Target Milestone: --- → 4.x (triaged)
Attached patch FixSplinter Review
Assignee: nobody → smccammon
Status: NEW → ASSIGNED
Attachment #416631 - Flags: review?(clouserw)
Attachment #416631 - Flags: review?(clouserw) → review+
r57668
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Keywords: push-needed
Resolution: --- → FIXED
Target Milestone: 4.x (triaged) → 5.5
Dave, I'm lazy -- mind verifying? :-)
https://preview.addons.mozilla.org/en-US/firefox/reviews/reply/165313
Escaping is fixed. Try to reply with a blank title and it yells at you with:
"There are errors in this form. Please correct them and resubmit."
and
"This field must not be empty."
with the main review field coming back correctly unescaped.

However, it is still requiring a title. If I then put one in, it still gives me the first error saying there are errors in the form. Apparently I can't post a dev reply at all anymore. REOPENING.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Both replying to and creating new comments fail on preview, yet work just fine on my clean dev copy.

clouserw: is there anything wacky going on with the staging database?
(In reply to comment #7)
> Both replying to and creating new comments fail on preview, yet work just fine
> on my clean dev copy.
> 
> clouserw: is there anything wacky going on with the staging database?

The schema could be out of date if something has changed recently.  I don't know of any system problems.
Turning debug on revealed the following error when saving a review:

Warning: SQL Error: 1062: Duplicate entry '4294967295' for key 1 

Somehow the reviews table on preview.a.m.o had its auto_increment value maxed out. Clouserw deleted the rogue review with id=4294967295 and reset auto_increment. Reviews can now be saved on preview as expected.
Status: REOPENED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → FIXED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: