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
Include cache key when including unversioned css #1773
Conversation
When including our css files that don't have a version in the name, include cache key based on Mantis version. Fixes #26148
I pushed to PR branch to MantisBT repository by mistake, so will leave it there and cleanup after merge. |
A similar change is needed for inclusion of unversioned js files. I'm planning to do it once this PR is merged. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe it would be better to move the cache key generation and concatenation logic to the html_css_link() function, and drive it with a bool $p_use_cache_key parameter (defaulted to false).
Fixes #26148
@dregad I pushed the refactored version. |
@dregad friendly reminder. Planning to merge this weekend. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
I have detached from #26148 the 2 changesets [1] that were created by the source integration plugin when you pushed to the issue26148_version_css branch in the mantisbt repo. [1]: For the record: |
When including our css files that don't have a version in the name, include cache key based on Mantis version. Refactored `html_css_link()` to have cache param. Fixes #26148, PR mantisbt#1773
When including our css files that don't have a version in the name,
include cache key based on Mantis version.
Fixes #26148