Feat/implement cache busting mechanism #21
Merged
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.
Implement a cache-busting mechanism for page reloads after a successful payment and login via PayButton. Instead of a standard reload, the URL is now appended with a unique timestamp query parameter (e.g., ?t=123456789) to force browsers and caching layers to fetch a fresh version of the page. This change has been applied in both assets/js/paywalled-content.js (after payment success) and assets/js/paybutton-paywall-cashtab-login.js (after login. This update addresses a rare caching issue reported by some users, where content would not appear unlocked until they performed a hard refresh.
To Test: