github-starred/vaultwarden
2
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-08-24 23:22:58 -05:00
Code Issues 534 Packages Projects Releases 86 Wiki Activity

send: "current access count" not updating in web vault #4640

New Issue
Closed
opened 2026-03-07 19:56:00 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-03-07 19:56:00 -06:00
Owner
Copy Link
Copy Source

Originally created by @fbartels on GitHub (Mar 29, 2021).

Subject of the issue

The send feature allow to expire items once it has been requested a given amount of times. This in itself also word (e.g. saying a link should have a "maximum access count" of two, no longer works when visiting it for the third time. However the gui also has a field "current access count" which looks like it should show how often an item has been requested already, but this seems to be stuck a "0".

Deployment environment

  • bitwarden_rs version: 1.20.0
  • Install method: using bitwardenrs/server:1.20.0
  • Clients used: bundled web vailt
  • Reverse proxy and version: Apache
  • MySQL/MariaDB or PostgreSQL version: sqlite
  • Other relevant details: none

Steps to reproduce

  • go to https://domain/#/sends and create a new send
  • expand "options" and set "maximum access count to e.g. "2"
  • click save and visit the link

Expected behaviour

  • after visiting the link the "current access" should have increased from "0" to "1"

Actual behaviour

  • the counter stays at "0"

Troubleshooting data

Originally created by @fbartels on GitHub (Mar 29, 2021). ### Subject of the issue The send feature allow to expire items once it has been requested a given amount of times. This in itself also word (e.g. saying a link should have a "maximum access count" of two, no longer works when visiting it for the third time. However the gui also has a field "current access count" which looks like it should show how often an item has been requested already, but this seems to be stuck a "0". ### Deployment environment * bitwarden_rs version: 1.20.0 * Install method: using bitwardenrs/server:1.20.0 * Clients used: bundled web vailt * Reverse proxy and version: Apache * MySQL/MariaDB or PostgreSQL version: sqlite * Other relevant details: none ### Steps to reproduce - go to `https://domain/#/sends` and create a new send - expand "options" and set "maximum access count to e.g. "2" - click save and visit the link ### Expected behaviour - after visiting the link the "current access" should have increased from "0" to "1" ### Actual behaviour - the counter stays at "0" ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data -->
GiteaMirror commented 2026-03-07 19:56:01 -06:00
Author
Owner
Copy Link
Copy Source

@fbartels commented on GitHub (Mar 29, 2021):

After opening this issue I went to the Chrome extension to see how this is displayed there and there the counter was successfully increased. Curiously after opening the element again in the web vault also there it now showed the correct amount of requests. I did make sure to reload the web vault before, but its counter stayed at zero.

Screenshot showing the web vault and the browser extension side by side:
image

@fbartels commented on GitHub (Mar 29, 2021): After opening this issue I went to the Chrome extension to see how this is displayed there and there the counter was successfully increased. Curiously after opening the element again in the web vault also there it now showed the correct amount of requests. I did make sure to reload the web vault before, but its counter stayed at zero. Screenshot showing the web vault and the browser extension side by side: ![image](https://user-images.githubusercontent.com/1257835/112823672-de558d00-9089-11eb-9130-e8c91bf08a1f.png)
GiteaMirror commented 2026-03-07 19:56:02 -06:00
Author
Owner
Copy Link
Copy Source

@Panja0 commented on GitHub (Mar 29, 2021):

Having the same problem on my side.
Refreshing (F5 or shift F5) does not change the status of the Current Access Count.

Logging out and logging back in to the web vault does change the Current Access Count though.

@Panja0 commented on GitHub (Mar 29, 2021): Having the same problem on my side. Refreshing (F5 or shift F5) does not change the status of the Current Access Count. Logging out and logging back in to the web vault **_does_** change the Current Access Count though.
GiteaMirror commented 2026-03-07 19:56:02 -06:00
Author
Owner
Copy Link
Copy Source

@BlackDex commented on GitHub (Mar 30, 2021):

If you switch to the My Vault page and back to Send it will update also.
We can not fix this, this also happens on upstream vault.bitwarden.com.

Duplicate of: #1554

@BlackDex commented on GitHub (Mar 30, 2021): If you switch to the `My Vault` page and back to `Send` it will update also. We can not fix this, this also happens on upstream vault.bitwarden.com. Duplicate of: #1554
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
better for forum
bug
documentation
duplicate
enhancement
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
SSO
Third party
troubleshooting
wontfix
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#4640