Skip to content
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

custom/template not work after update #4561

Closed
2 of 7 tasks
EnricoFerro opened this issue Jul 30, 2018 · 5 comments · Fixed by #4638
Closed
2 of 7 tasks

custom/template not work after update #4561

EnricoFerro opened this issue Jul 30, 2018 · 5 comments · Fixed by #4638
Labels
Milestone

Comments

@EnricoFerro
Copy link
Contributor

EnricoFerro commented Jul 30, 2018

  • Gitea version (or commit ref): d572336 ( probably from a74426d )
  • Git version:
  • Operating system: Linux Ubuntu
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

In Docker after update from be4ec0c to d572336 the custom/templates is not more read ( in particular after the modification of template/home.tmpl.
The public image ( custom/public/img ) is not affected.

Probably the cause is the a74426d commit.

Screenshots

Before:
image

After:
image

@lafriks lafriks added this to the 1.6.0 milestone Jul 30, 2018
@LER0ever
Copy link
Contributor

LER0ever commented Aug 3, 2018

Hi, same issue here. Probably the this line in this commit caused the tplFileSys to be initialized more than it should be?

@sankethpb
Copy link

could this be back-ported to 1.5.2 ?

@lafriks
Copy link
Member

lafriks commented Sep 22, 2018

I don't think 1.5 branch has that problem

@sankethpb
Copy link

We are facing the same issue in 1.5.1, in docker image.

@strk
Copy link
Member

strk commented Sep 23, 2018 via email

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants