|
|
|
|
<!DOCTYPE html>
|
|
|
|
|
<html lang="{{ctx.Locale.Lang}}" class="theme-{{if .SignedUser.Theme}}{{.SignedUser.Theme}}{{else}}{{DefaultTheme}}{{end}}">
|
|
|
|
|
<head>
|
|
|
|
|
<meta name="viewport" content="width=device-width, initial-scale=1">
|
|
|
|
|
<title>{{if .Title}}{{.Title | RenderEmojiPlain}} - {{end}}{{if .Repository.Name}}{{.Repository.Name}} - {{end}}{{AppName}}</title>
|
|
|
|
|
{{if .ManifestData}}<link rel="manifest" href="data:{{.ManifestData}}">{{end}}
|
|
|
|
|
<meta name="author" content="{{if .Repository}}{{.Owner.Name}}{{else}}{{MetaAuthor}}{{end}}">
|
|
|
|
|
<meta name="description" content="{{if .Repository}}{{.Repository.Name}}{{if .Repository.Description}} - {{.Repository.Description}}{{end}}{{else}}{{MetaDescription}}{{end}}">
|
|
|
|
|
<meta name="keywords" content="{{MetaKeywords}}">
|
|
|
|
|
<meta name="referrer" content="no-referrer">
|
|
|
|
|
{{if .GoGetImport}}
|
|
|
|
|
<meta name="go-import" content="{{.GoGetImport}} git {{.RepoCloneLink.HTTPS}}">
|
|
|
|
|
<meta name="go-source" content="{{.GoGetImport}} _ {{.GoDocDirectory}} {{.GoDocFile}}">
|
|
|
|
|
{{end}}
|
|
|
|
|
{{if and .EnableFeed .FeedURL}}
|
|
|
|
|
<link rel="alternate" type="application/atom+xml" title="" href="{{.FeedURL}}.atom">
|
|
|
|
|
<link rel="alternate" type="application/rss+xml" title="" href="{{.FeedURL}}.rss">
|
|
|
|
|
{{end}}
|
|
|
|
|
<link rel="icon" href="{{AssetUrlPrefix}}/img/favicon.svg" type="image/svg+xml">
|
|
|
|
|
<link rel="alternate icon" href="{{AssetUrlPrefix}}/img/favicon.png" type="image/png">
|
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
|
|
|
{{template "base/head_script" .}}
|
|
|
|
|
<noscript>
|
|
|
|
|
<style>
|
|
|
|
|
.dropdown:hover > .menu { display: block; }
|
|
|
|
|
.ui.secondary.menu .dropdown.item > .menu { margin-top: 0; }
|
|
|
|
|
</style>
|
|
|
|
|
</noscript>
|
|
|
|
|
{{template "base/head_opengraph" .}}
|
|
|
|
|
{{template "base/head_style" .}}
|
|
|
|
|
{{template "custom/header" .}}
|
|
|
|
|
</head>
|
|
|
|
|
<body>
|
|
|
|
|
{{ctx.DataRaceCheck $.Context}}
|
|
|
|
|
{{template "custom/body_outer_pre" .}}
|
|
|
|
|
|
|
|
|
|
<div class="full height">
|
|
|
|
|
<noscript>{{ctx.Locale.Tr "enable_javascript"}}</noscript>
|
|
|
|
|
|
|
|
|
|
{{template "custom/body_inner_pre" .}}
|
|
|
|
|
|
|
|
|
|
{{if not .PageIsInstall}}
|
|
|
|
|
{{template "base/head_navbar" .}}
|
|
|
|
|
{{end}}
|
|
|
|
|
|
|
|
|
|
{{if false}}
|
|
|
|
|
{{/* to make html structure "likely" complete to prevent IDE warnings */}}
|
|
|
|
|
</div>
|
|
|
|
|
</body>
|
|
|
|
|
</html>
|
|
|
|
|
{{end}}
|
