You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As admin, create 4 articles, and ask a review for the fourth post (I believe).
Login as editor, go to Reviews, but only the 3rd post (unpublished) appear (did I mistakenly ask a review for the 3rd post instead of the 4th?)
As editor, go as a review to self for the 4th post
from Reviews, click on the 4th post, the error happens.
Seeing 2 issues here:
review request from admin didn't show up in Reviews
Multiple reviewers (actually the same user twice) can be assigned to a post, but wagtail-review doesn't support it (wagtail_review/views/admin.py l.133)
The text was updated successfully, but these errors were encountered:
Sorry for the lack of clarity, I'm just getting started with WagTail and don't yet understand the details behind it.
Here what I can see from a shell
In [27]: rf=Review.objects.first()
In [28]: PageRevision.objects.get(id=rf.page_revision_id)
Out[28]: <PageRevision: "Third post unpublished"at2019-04-1907:02:40.572529+00:00>In [29]: [User.objects.get(id=r.user_id) forrinrf.reviewers.all()]
Out[29]: [<User: Reviewer>, <User: dori>]
In [30]: rl=Review.objects.last()
In [31]: PageRevision.objects.get(id=rl.page_revision_id)
Out[31]: <PageRevision: "4th post to review"at2019-04-1907:04:40.425567+00:00>In [32]: [User.objects.get(id=r.user_id) forrinrl.reviewers.all()]
Out[32]: [<User: Reviewer>, <User: Reviewer>]
I do not know why my 3rd post has 2 reviewers. Is there some logic where unpublishing a post auto-assign reviewers? Strange... Also, no error happens when viewing it.
screenshot
I suppose the relevant bug report here is that the same user can be assigned twice for the same review, which causes a 500 error. Why the review made as admin didn't show up first in the user Reviews page is another concern.
Traceback
Steps:
Seeing 2 issues here:
wagtail_review/views/admin.py
l.133)The text was updated successfully, but these errors were encountered: