Upgrade breaks layout #5601

New Issue

GiteaMirror · 2025-11-02T06:30:28-06:00

GiteaMirror commented

2025-11-02 06:30:28 -06:00

Originally created by @cylott on GitHub (Jun 20, 2020).

Hi, I recently upgraded gitea from 1.9.3 to 1.12.0. I assumed I could simply drop in the new binary as before. This did not work well. I loaded the repo in a browser and the layout was all broken - looking at the console the page was trying to load all sorts of js and css resources that were 404: polyfill, semantic, cssrel something etc

I then ran gitea —migrate which seemed to do something to my sqlite db. Loading the page afterwards, I could see fewer 404s, now just looking for semantic.js, but the page was still broken. Everything was working, but obviously key css resources were not found.

I also tried building from source with the same results. Any ideas? I'm on a mac.

Originally created by @cylott on GitHub (Jun 20, 2020). Hi, I recently upgraded gitea from 1.9.3 to 1.12.0. I assumed I could simply drop in the new binary as before. This did not work well. I loaded the repo in a browser and the layout was all broken - looking at the console the page was trying to load all sorts of js and css resources that were 404: polyfill, semantic, cssrel something etc I then ran gitea —migrate which seemed to do something to my sqlite db. Loading the page afterwards, I could see fewer 404s, now just looking for semantic.js, but the page was still broken. Everything was working, but obviously key css resources were not found. I also tried building from source with the same results. Any ideas? I'm on a mac.

GiteaMirror closed this issue

2025-11-02 06:30:28 -06:00

GiteaMirror commented

2025-11-02 06:30:29 -06:00

@lunny commented on GitHub (Jun 21, 2020):

Have you cleared your browser cache?

@lunny commented on GitHub (Jun 21, 2020): Have you cleared your browser cache?

GiteaMirror commented

2025-11-02 06:30:29 -06:00

@zeripath commented on GitHub (Jun 21, 2020):

And are you using custom templates?

@zeripath commented on GitHub (Jun 21, 2020): And are you using custom templates?

GiteaMirror commented

2025-11-02 06:30:29 -06:00

@cylott commented on GitHub (Jun 21, 2020):

Have you cleared your browser cache?

Yes.

@cylott commented on GitHub (Jun 21, 2020): > Have you cleared your browser cache? Yes.

GiteaMirror commented

2025-11-02 06:30:29 -06:00

@cylott commented on GitHub (Jun 21, 2020):

And are you using custom templates?

I'm using arc-green theme and a custom header.

@cylott commented on GitHub (Jun 21, 2020): > And are you using custom templates? I'm using arc-green theme and a custom header.

GiteaMirror commented

2025-11-02 06:30:30 -06:00

@cylott commented on GitHub (Jun 21, 2020):

Ah ok, I turned off the custom header and it seems to be working now. All that was in there was a Matomo JS.

What does "gitea --migrate" do? Was there any reason to run that on my db?

@cylott commented on GitHub (Jun 21, 2020): Ah ok, I turned off the custom header and it seems to be working now. All that was in there was a Matomo JS. What does "gitea --migrate" do? Was there any reason to run that on my db?

GiteaMirror commented

2025-11-02 06:30:30 -06:00

@zeripath commented on GitHub (Jun 21, 2020):

Have you checked that your custom header is not out of sync with what we have in 1.12?

In 1.12/master we also changed the serviceworker so clearing the cache is actually slightly more difficult than you might initially think. (That would resolve itself in 24 hours...) Have you tried browsing on an incognito session or different browser just to confirm that the cache is definitely not involved?

@zeripath commented on GitHub (Jun 21, 2020): Have you checked that your custom header is not out of sync with what we have in 1.12? In 1.12/master we also changed the serviceworker so clearing the cache is actually slightly more difficult than you might initially think. (That would resolve itself in 24 hours...) Have you tried browsing on an incognito session or different browser just to confirm that the cache is definitely not involved?

GiteaMirror commented

2025-11-02 06:30:30 -06:00

@silverwind commented on GitHub (Jun 21, 2020):

A common issue is that people still build with make generate build. Please update that to make build if you're doing that.

@silverwind commented on GitHub (Jun 21, 2020): A common issue is that people still build with `make generate build`. Please update that to `make build` if you're doing that.

GiteaMirror commented

2025-11-02 06:30:30 -06:00

@zeripath commented on GitHub (Jul 4, 2020):

@cylott the migration occurs automatically because between versions we often change the database slightly.

It appears though we've answered your problem. I'm not sure what Matamo js is it how it causes problems but I guess you need to check your browser console to work that out.

I'll close this issue now.

@zeripath commented on GitHub (Jul 4, 2020): @cylott the migration occurs automatically because between versions we often change the database slightly. It appears though we've answered your problem. I'm not sure what Matamo js is it how it causes problems but I guess you need to check your browser console to work that out. I'll close this issue now.

GiteaMirror referenced this issue

2025-11-02 16:17:34 -06:00

[PR #5601] [MERGED] Delete organization endpoint added #17861

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#5601