On Friday, October 12, 2012 10:05:39 AM UTC-7, Christian Hammond wrote:
> You're close. It's two reviews with different IDs from the same user on
> the same review request that are both still set to public=false.
> This really shouldn't be happening. It used to, but the cause was found
> and fixed long ago. Please let us know if it happens again.
Is there something I can do to fix this entry to the user can access his
review? Right now he's blocked. Would setting public=true in the db fix the
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at