I don't seem to be getting the familiar symfony error messages I used to when I wasn't running on a VM. The error message I get when there is a Laravel related issue is a "Whoops, looks like something went wrong" in a white background.
Is there a common solution to this/others run into this problem who can help out?
thanks
You need to turn $debug to true in app/config/app.php
Related
I deployed my Laravel application to my web hosting site. Everything transferred successfully, but every time I login I get some message about parse syntax unexpected ? but its not telling me where its coming from this happens also on my other pages.
I'm using PHP 7.0 on my hosting site and Laravel 5.4. it will mean so much if you can help me understand what is going on. I can't provide you with a code because I don't know where the error is coming from. It doesn't tell me what line or anything. Please do not tell me the solution is in this similar question where it says "parse error" duplicate because I tried that and nothing happened
Parse error: syntax error, unexpected '?', expecting variable (T_VARIABLE)
The question marks are a feature of php 7.1. As you have said in the comments, the version on the server is only 7.0.
see http://php.net/manual/en/migration71.new-features.php for more information about this feature.
We are using Sentry for finding some errors.
How do you proof, that a reporting is working?
I had a Spring-Boot project, which was not sending any error to Sentry, so it looks like it was working without an error, but I saw in Kibana, that there have been errors.
So, my configuration was wrong. After fixing the setup, it's now sending the errors to Sentry too.
Is there any way to proof that the sending to Sentry is working?
Something like on startup of my Spring-Boot application sending a first string?
I found 2 possible solutions which both sucks, so that's why I ask for a more professional way:
I can make just on application start up a log.error("sentry is working")
I can set the log-level from warning / error to info just to see that it's working and if see it in Sentry, you change it back?
But as i mentioned, both methods are not good, so let me know how you are resolving problems like this
are unprofessional to me, so let me know
There isn't a real "answer" here currently, as part of Sentry's simplicity is it doesn't do anything until an error happens. One potential solution is to introduce a path like example.com/500 that deliberately errors.
How can I print the error message on browser where I access my app instead of seeing 'Whoops, looks like something went wrong.' which is not very helpful and is very annoying when I have to go to the storage/logs/lumen.log to find the error?
I am using Laravel's Lumen and it is not as friendly as Slim. Any ideas how can I see the error on screen instead?
After installing laravel I get the following message when run the project:
Whoops, looks like something went wrong.
You can have a look at your laravel log, located at app/storage/logs/laravel.log.
Whilst your application is in development mode, you can make your life a lot easier by enabling detailed error reporting. Just change false to true here:
In this file (app/config/app.php) - first line:
Nobody will be able to help you with above posted error message, but it will be very easy to help yourself with detailed error reporting enabled
Set 'debug' to true in app/config/app.php.
If it's already to true, set it to false, refresh, then set it again to true.
I 've installed magento and it seems to work, but if I want to save a new Catalog_product_set with different attributes then I get Internal Error Message with Status Code 500
Does anyone have the same problem?
Thanks in advance
cheers tabaluga
Your screenshot (and from the looks of it Magento's error page) clips the edge of the error off. Seeing the rest of the error message might be important. Regardless, it looks like Magento is trying to load a config file w/ simplexml, and cannot find that file.