mirror of
https://github.com/cypht-org/cypht.git
synced 2026-04-25 04:56:03 +03:00
[GH-ISSUE #296] 🕷 Moving EMails fails silently #257
Labels
No labels
2fa
I18N
PGP
Security
Security
account
advanced_search
advanced_search
announcement
api_login
authentication
awaiting feedback
blocker
bug
bug
bug
calendar
config
contacts
core
core
devops
docker
docs
duplicate
dynamic_login
enhancement
epic
feature
feeds
framework
github
github
gmail_contacts
good first issue
help wanted
history
history
imap
imap_folders
inline_message
installation
keyboard_shortcuts
keyboard_shortcuts
ldap_contacts
mobile
need-ssh-access
new module set
nux
pop3
profiles
pull-request
question
refactor
release
research
saved_searches
smtp
strategic
tags
tests
themes
website
wordpress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cypht#257
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 @ulfgebhardt on GitHub (Oct 26, 2018).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/296
Originally assigned to: @jasonmunro on GitHub.
Moving EMails often fails silently.
Steps:
Remarks:
This did not happen before:
87b5c99b12020f9b2cf7@jasonmunro commented on GitHub (Oct 26, 2018):
almost certain this is related to the recent work on moving the open message in inline view. I will check it out.
@jasonmunro commented on GitHub (Oct 26, 2018):
I found the problem - context. The move/copy logic had no indication of which move/copy button was used, so the logic to collect the message ids was incorrect. I have added a context to the chain of function calls so when the move/copy is executed the code knows (message or list) and collects the correct message id(s). If you could test out the latest master branch and let me know if its resolved for you that would be great!
@ulfgebhardt commented on GitHub (Oct 27, 2018):
Confirming fix,
your the Best!
Grüße Ulf <3