Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

global "mark all folders as read" does not update folder unread messages count label #6270 #6307

Closed
grape6 opened this issue May 25, 2018 · 5 comments

Comments

@grape6
Copy link

grape6 commented May 25, 2018

described in #6270

Seems this happens for any folder except INBOX.

Can be reproduced in that way: mark some messages as unread in any other folder (tmp), log out,
log in, select another folder (arch), mark all messages as read, and for (tmp) folder count label is not updated.

RCM git, only contextmenu plugin is enabled.

@alecpl
Copy link
Member

alecpl commented May 25, 2018

Still works for me. Any errors in browser console? Could you check response of the ajax request? Could you enable imap_debug and provide the log?

@johndoh
Copy link
Contributor

johndoh commented May 25, 2018

The problem seems to be related to $_SESSION['unseen_count'] its NULL. Debug shows the unseen_count being populated for each folder during login but then its nulled.

It means in rcmail_send_unread_count $unseen != $old_unseen is 0 != null which is false so the set_unread_count command is not set for anything accept inbox.

I checked and the unseen_count is removed from the session but I cannot find where :/

running git-master all plugins disabled.

@johndoh
Copy link
Contributor

johndoh commented May 26, 2018

problem occurs with session_storage 'db' but not 'php'

@alecpl
Copy link
Member

alecpl commented May 26, 2018

Thanks @johndoh that helped. There are list and getunread ajax request when Mail UI is displayed. I was able to reproduce the issue if I make the list request to take longer and finish after getunread.

@alecpl alecpl added this to the 1.3.7 milestone May 26, 2018
alecpl added a commit that referenced this issue May 26, 2018
…s were not reset (#6307)

also fixed one PHP 7.2 warning
alecpl added a commit that referenced this issue May 26, 2018
…s were not reset (#6307)

also fixed one PHP 7.2 warning
@alecpl
Copy link
Member

alecpl commented May 27, 2018

Fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants