[18.0][FIX] vault_share: make share token consistent between UI and DB - #992
Open
jans23 wants to merge 1 commit into
Open
[18.0][FIX] vault_share: make share token consistent between UI and DB#992jans23 wants to merge 1 commit into
jans23 wants to merge 1 commit into
Conversation
jans23
force-pushed
the
18.0-fix-vault_share-token
branch
from
August 24, 2026 16:18
34a1209 to
7c8b7b0
Compare
The server stored a different token than the one the form used to build the share link, which then always resulted in 'Invalid token'. Generate the token client-side via a string default and persist that exact value using a view readonly field with force_save, so the UI and DB always agree.
jans23
force-pushed
the
18.0-fix-vault_share-token
branch
from
August 24, 2026 16:22
7c8b7b0 to
c2a7b45
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The server stored a different token than the one the form used to build the share link, which then always resulted in 'Invalid token'. Generate the token client-side via a string default and persist that exact value using a view readonly field with force_save, so the UI and DB always agree.