gitea

Commit Graph

Author	SHA1	Message	Date
silverwind	85f829fb3c	Enable contenthash in filename for dynamic assets (#20813 ) (#20932 ) This should solve the main problem of dynamic assets getting stale after a version upgrade. Everything not affected will use query-string based cache busting, which includes files loaded via HTML or worker scripts.	3 years ago
wxiaoguang	2bce1ea986	Show messages for users if the ROOT_URL is wrong, show JavaScript errors (#18971 ) * ROOT_URL issues: some users did wrong to there app.ini config, then: * The assets can not be loaded (AppSubUrl != "" and users try to access http://host:3000/) The ROOT_URL is wrong, then many URLs in Gitea are broken. Now Gitea show enough information to users. JavaScript error issues, there are many users affected by JavaScript errors, some are caused by frontend bugs, some are caused by broken customized templates. If these JS errors can be found at first time, then maintainers do not need to ask about how bug occurs again and again. * Some people like to modify the `head.tmpl`, so we separate the script part to `head_script.tmpl`, then it's much safer. * use specialized CSS class "js-global-error", end users still have a chance to hide error messages by customized CSS styles.	3 years ago

Author

SHA1

Message

Date

silverwind

85f829fb3c

Enable contenthash in filename for dynamic assets (#20813 ) (#20932 )

This should solve the main problem of dynamic assets getting stale after
a version upgrade. Everything not affected will use query-string based
cache busting, which includes files loaded via HTML or worker scripts.

3 years ago

wxiaoguang

2bce1ea986

Show messages for users if the ROOT_URL is wrong, show JavaScript errors (#18971 )

* ROOT_URL issues: some users did wrong to there app.ini config, then:
    * The assets can not be loaded (AppSubUrl != "" and users try to access http://host:3000/)
    *The ROOT_URL is wrong, then many URLs in Gitea are broken.
Now Gitea show enough information to users.

* JavaScript error issues, there are many users affected by JavaScript errors, some are caused by frontend bugs, some are caused by broken customized templates. If these JS errors can be found at first time, then maintainers do not need to ask about how bug occurs again and again.

* Some people like to modify the `head.tmpl`, so we separate the script part to `head_script.tmpl`, then it's much safer.

* use specialized CSS class "js-global-error", end users still have a chance to hide error messages by customized CSS styles.

3 years ago

2 Commits (92f72d678c9ea42dacbc1b431df501dfe71605bd)