mirror of
https://github.com/ciur/papermerge.git
synced 2026-04-25 03:55:58 +03:00
[GH-ISSUE #72] Document view random page order #55
Labels
No labels
2.1
3.0
3.0.1
3.0.2
3.0.3
3.0.3
3.1
3.2
3.2
3.3
3.5
3.x
Fixed. Waiting for feedback.
Fixed. Waiting for feedback.
UX
Version 2.1 - alpha
XSS
announcement
beta
blocker
bug
cannot reproduce
confirmed
confirmed
critical
demo
dependencies
deployment
detchnical debt
discussion
docker
documentation
donations
duplicate
enhancement
feature request
frontend
fundraising
good first issue
good issue
help wanted
high
implemented
important
improvement
incomplete
invalid
investigation
kubernetes
low
low impact
medium
medium
medium impact
migration from 2.0
migration from 2.1
missing-language
missing-ocr-language
no-activity
note
ocr
outofscope
packaging
performance
popular request
pull-request
pypi
question
raspberry pi
roadmap
search
security
setup
status
task
technical debt
updates
user xp
version 1.4.0 - demo
will be implemented
will not be implemented
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/papermerge#55
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @defaultroute-eu on GitHub (Aug 17, 2020).
Original GitHub issue: https://github.com/ciur/papermerge/issues/72
When importing a scanned multi-page document I have the pages displayed in random order when viewing the document:

I fixed this issue in my instance (papermerge running in containers with a postgres db) by adding an ordered_by call to the queryset in
github.com/ciur/papermerge@815079151e/papermerge/core/views/documents.py (L48)like this:Since I found several usages of pages.all() on Document objects, another possibility would be adding a Meta class to Page like this (but I don't know, if this would break something):
What do you think?
@ciur commented on GitHub (Aug 17, 2020):
Fantastic!
@defaultroute-eu, if submit a PR with that change (adding ordering to Page's metaclass) I will accept it right away.
Unfortunately there are no tests for that feature/part of code. But don't worry, if you do the change, I will add a UT (unit test) for that behaviour.
Thank you for your contribution!