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

Disabling translations causes internal server error #478

Closed
ghost opened this issue Nov 25, 2015 · 6 comments
Closed

Disabling translations causes internal server error #478

ghost opened this issue Nov 25, 2015 · 6 comments
Labels

Comments

@ghost
Copy link

ghost commented Nov 25, 2015

I have languages enabled and translation turned on. In the admin panel when I disable translations and click save, it displays an internal server error box. When I reload the admin panel I get an error.

500
Server Error
Sorry, something went terribly wrong!
E_ERROR - Call to a member function get() on a non-object
For further details please review your logs/ folder, or enable displaying of errors in your system configuration.

The log shows:

[2015-11-25 09:05:07] grav.CRITICAL: Call to a member function get() on a non-object - Trace: #0 /home4/gigatree/public_html/s2/vendor/filp/whoops/src/Whoops/Run.php(357): Whoops\Run->handleError(1, 'Call to a membe...', '/home4/gigatree...', 433) #1 [internal function]: Whoops\Run->handleShutdown() #2 {main} [] []

I've attached the good (before) and bad (after) yaml files. The only diff is the
languages: translations: true/false.

If i set it back to false. The admin panel loads fine. If i set it to true, I get the error.

user.config..system.yaml.good.txt
user.configsystem.yam.bad.txt

@flaviocopes
Copy link
Contributor

Can you turn on error reporting (system.errors.display) to see a more detailed stack trace of the error? I cannot reproduce the problem even when adding your bad system.yaml

@ghost
Copy link
Author

ghost commented Nov 25, 2015

okay what would you like me to send you

@flaviocopes
Copy link
Contributor

Just turn on error reporting and post the error / screenshot of the error details

@ghost
Copy link
Author

ghost commented Nov 25, 2015

snap8

@flaviocopes
Copy link
Contributor

Ok I see I recreated it on a skeleton with the current Grav version. It's already fixed in the repository, will be fixed in the next Grav update!

@ghost
Copy link
Author

ghost commented Nov 25, 2015

great, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant