-
Notifications
You must be signed in to change notification settings - Fork 117
Cannot apply settings. Possibly related to #506. #567
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
Comments
Hi, I've just spent about a week pulling my hair out.
So after using this install guide http://redmine-git-hosting.io/get_started/, we noticed things missing. Eg, where does this go?
This needs to be added into Also we getting an "Internal error 500" when We had to manually edit
Then for the safe side we restarted the server, and everything worked, when running "git commits" the comments would be there. Don't hit "apply" or make changes for the "redmine_git_hosting" plugin via the gui it will break every time. I hope this helps. |
@jblobb oh, thank you very much! That indeed did work and I managed to set settings to correct values. I will leave the issue open for a time being since the GUI is still broken. |
I can't reproduce it with the next release (1.2.2) :
Closing it. |
Same error here. I've got some extra plugins installed but I haven't had problem before recently. I tried downgrading to 3.1.3 (because 3.1.x is confirmed to work) but that didn't make the problem go away (probably due to database screwed up as well as files).
I'm kind of stuck here with working configuration that I would very much like to change but can't. It would be really great if there was a way I can adjust access configuration safely somehow as a temporary workaround.
I've been having this for probably quite a long time since I noticed it about a month ago but didn't have enough time to investigate back then.
The log says:
And the versions are:
Do ask any additional questions if you feel like I haven't provided enough information (because I feel I didn't).
Thanks!
The text was updated successfully, but these errors were encountered: