mirror of
https://github.com/modoboa/modoboa.git
synced 2026-04-26 01:16:01 +03:00
[GH-ISSUE #343] amavis extension: internal error when deleting messages on last page of a multi-page quarantine #326
Labels
No labels
bug
bug
dependencies
design
documentation
duplicate
enhancement
enhancement
enhancement
feedback-needed
help-needed
help-needed
installer
invalid
looking-for-sponsors
modoboa-contacts
new-ui
new-ui
pr
pull-request
pyconfr
python
question
security
stale
webmail
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/modoboa-modoboa#326
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 @tonioo on GitHub (Dec 4, 2013).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/343
Originally assigned to: @tonioo on GitHub.
Originally created by Louis-Dominique Dubeau on 2012-10-26T12:31:31Z
Modoboa version 0.9.3
(However it also happened with 0.9.2. Forgot to report it. Sorry.)
This is easily reproducible on my installation:
I considered that maybe the problem is that if all the messages on the last page (let's call it page N) are deleted Modoboa still tries to display page N instead of page N-1 and fails because page N no longer exists since all the messages that would be on it have been deleted. However, the error happens even if only a subset of messages on page N are deleted and thus still exists after the deletion operation.
@tonioo commented on GitHub (Dec 4, 2013):
Posted by Antoine Nguyen on 2012-10-26T19:25:24Z
Hi Louis-Dominique,
can you tell me which SGBD you're using?
@tonioo commented on GitHub (Dec 4, 2013):
Posted by Antoine Nguyen on 2012-10-26T20:01:27Z
Applied in changeset commit:de9065a80b9a.
@tonioo commented on GitHub (Dec 4, 2013):
Posted by Antoine Nguyen on 2012-10-26T20:02:38Z
Actually, the issue was due to a wrong URL manipulation (the '#listing/' part was removed after the operation).