Skip to content

Make home.tmpl visible with Signin-View enabled #4040

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

Merged
merged 2 commits into from May 24, 2018
Merged

Make home.tmpl visible with Signin-View enabled #4040

merged 2 commits into from May 24, 2018

Conversation

ghost
Copy link

@ghost ghost commented May 24, 2018

Fix #3846

@codecov-io
Copy link

codecov-io commented May 24, 2018

Codecov Report

Merging #4040 into master will decrease coverage by <.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #4040      +/-   ##
==========================================
- Coverage   19.96%   19.95%   -0.01%     
==========================================
  Files         153      153              
  Lines       30478    30478              
==========================================
- Hits         6086     6083       -3     
- Misses      23479    23481       +2     
- Partials      913      914       +1
Impacted Files Coverage Δ
modules/process/manager.go 69.56% <0%> (-4.35%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8ebd15e...2781168. Read the comment docs.

@bkcsoft bkcsoft added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label May 24, 2018
@bkcsoft bkcsoft added lgtm/need 1 This PR needs approval from one additional maintainer to be merged. and removed lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. labels May 24, 2018
@daviian
Copy link
Member

daviian commented May 24, 2018

LGTM

@bkcsoft bkcsoft added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels May 24, 2018
@techknowlogick techknowlogick added type/enhancement An improvement of existing functionality topic/ui Change the appearance of the Gitea UI labels May 24, 2018
@techknowlogick techknowlogick added this to the 1.5.0 milestone May 24, 2018
@techknowlogick techknowlogick merged commit 2a97994 into go-gitea:master May 24, 2018
@agaida
Copy link

agaida commented May 29, 2018

Not a good idea - with that merged the LANDING_PAGE setting is ignored

@lunny
Copy link
Member

lunny commented May 30, 2018

So this result in a bug. @agaida maybe you can fire an issue. see #4079

aswild added a commit to aswild/gitea that referenced this pull request Jul 6, 2018
@nillith
Copy link

nillith commented Nov 23, 2018

Why can't you just add a new opt in option instead of changing the default behavior of REQUIRE_SIGNIN_VIEW? I upgraded from 1.1 to 1.5 now all the users, organizations and public repositories are exposed. What can I do? Stick with 1.1?

@lunny
Copy link
Member

lunny commented Nov 23, 2018

@nillith this PR will only expose home page that should have no any usable contents. I think your problem maybe not effected by this PR.

@cht47
Copy link

cht47 commented Nov 23, 2018

I can confirm that the change is working like intended. @nillith it seems you have configured something wrong. REQUIRE_SIGNIN_VIEW = true keeps everything save from anonymous users. The only thing you can see now is the home.tmpl (which was never visible before that change with require_signin true)

@nillith
Copy link

nillith commented Nov 24, 2018

home.tmpl >> base/head.tmpl >> base/head_navbar.tmpl >> Explore and BOOM . This is the path where all the things are exposed.
I'm pretty sure this is the causal change. I did a clean install and got the same problem. REQUIRE_SIGNIN_VIEW literally means you can only see the login page. Any other things you'd like to expose must be explicitly specified.

@lafriks
Copy link
Member

lafriks commented Nov 24, 2018

I would agree with @nillith as it is kind of annoying on having to click on login menu all the time

@lunny
Copy link
Member

lunny commented Nov 24, 2018

@nillith @lafriks I agree with that's some annoying but I think @nillith 's

I upgraded from 1.1 to 1.5 now all the users, organizations and public repositories are exposed.

is not effected by this PR.

@nillith
Copy link

nillith commented Nov 26, 2018

@lunny I think its already written on the wall. The home.tmpl contains more than just the home page. And I tried the version 1.4.3 and 1.6. 1.6 have the same problem and 1.4.3 is OK.
It looks like the problem only happens after the first installation and disappeared after I restart the docker container. So I think it's fine.

@cht47
Copy link

cht47 commented Nov 26, 2018

Ok I'm not using a docker container, maybe there is another problem with it. Can't see a problem where it is annoying to click on login. For EU you must deliver an Imprint, Cookie Law, GDPR. Forcing it on the front page is the best option in this case as you can't add some fancy modals. For Intranet only you don't need REQUIRE_SIGNIN_VIEW. Right Management can handle access to repos.

@kandeshvari
Copy link

@cht47 Habitual behavior was changed. I(and many others) don't need home screen at all and yes - it's really annoying to click Login button every time I go to my intranet git (I even searched and found this issue!). There was a reasonable question - why don't provide new option instead of changing old one?

@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
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. topic/ui Change the appearance of the Gitea UI type/enhancement An improvement of existing functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.