How to show errors in browser? - symfony

I'm getting started with Sylius. Symfony version is 3.2.7. On some pages I have some errors. The pages show text:
Oops! An Error Occurred
The server returned a "500 Internal Server Error".
Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused.
I want the errors to be displayed in browser, with full stacktrace.
I know I can see the error in var/prod.log, but it doesn't show the whole stacktrace, only the last frame. And seeing the error in browser would be more convenient: that's what I'm used to after a lot of working with Yii and Magento.
Is that possible with Symfony/Sylius?

I added /app_dev.php to the url to run the website in development environment, and there I can see the stack trace.
That is, https://[my_domain]/app_dev.php/[page] instead of https://[my_domain]/[page]

By default Symfony show trace in dev environment. In prod environment it show simple error message. For running your project in dev you can use built-in PHP Web Server or Web Server Bundle

Also you can use symfony installer app to serve request
Use symfony serve --no-tls in symfony folder.
It will show you requests and errors in red.

Related

Error on deploying website to IIS - App still refers to local files directory even after publish

Has anyone experienced this issue before? I published a website using File Deploy and placed it in an IIS. Other apps works just fine, but the website I deployed shows this error:
It seems to still be pointing to my local directory. I've updated the paths but to no avail. Help please.
Thanks in advance.
The paths show locations at compile-time, that is not a problem. Here, you are getting an exception on line 65 in DataAccess.cs - object reference not set to an instance of an object.
If you set custom error "on" (in the web.config), you can get more info about the exception. In the "Network" tab of "Developer tools", you can check your request and response.

The route is truncated on my Symfony application getting a 404 error

I have two differents pages getting the same error in my symfony3.4 application.
It is a detail page of an entity, it is working most of the time but sometimes and I don't know what is triggering the error, I get a 404 error and I can see my route truncated in the error.
The route is : {base_url}/app_dev.php/stock/model/{id}/detail
On some of my resources, the error message is :
It seems to happend on specific entities but I have no clues about what could possibly trigger that kinds of error.
Any idea of what I could investigate to debug ?
-- EDIT --
It seems that the route is working fine using {base_url}/web/app_dev.php , the problem appears when the route has no /web in dev mode ({base_url}/app_dev.php)
Sometimes Symfony3 throught a 404 error in dev mode without the /web . It is a server configuration matter. Check https://symfony.com/doc/3.4/setup/web_server_configuration.html for more informations

Migrated Hybris storefront throws Server Error but log shows no error

I'm migrating from a Hybris 5.2 to Hybris 6.5, so far we managed to get rid of compilation errors and erros when running the server, but so far we have been unable to access the storefront.
When we try to access it we get a server error, but the log doesn't show anything that could give us a hint. Even the Chrome console doesn't show any errors.
I include the logs generated from the ant clean all and the hybris server startup in this link.
I have even debugged the home page controller, but no exceptions are being thrown, and my guesses are small since I have no feedback on the possible issue at hand.
What do we have to look at in these kind of situations? Is there a way to track the issue? Any tool in Hybris or an external one that could help me sniff the problem?
The issue was due to a missing configuration for JCO and SMTP, our client had a local.properties that had this configuration commented, after setting a configuration for these two the storefront was visible, still we don't understand how this missing configuration could not throw any error on console and we reached to this solution after a lot of trial and error.

Lucee not showing run-time errors

Running Lucee server 5.2.1.9 (hosted at Vivio), and I'm unable to get it to show any run-time errors.
I have debugging enabled
I have enabled all debug info types
I've set a debug template (for all IPs); currently set to "Classic", but I've tried "Comment" and "Modern" as well.
When an error occurs, I get an empty page. If a debug template set, I get dumps of all the appropriate scopes and DB activity, as well as execution times... but no error message/details or stack trace.
Is there a setting I'm missing?
How do I insure Lucee displays my run-time errors during development?
I'm not sure if you every figured this out (kind of a necro). If you are in Dev disect your application.cfc. I had an issue in my onRequest section. Someone threw a cftry around the target page include. This ran Lucee into the catch and it showed a blank page.
If that doesn't help try removing your OnError function in there. There might be something in there that is trying to serve up a friendly error page which could prevent error output.
Also, look in Lucee server administrator and check that it is pointing to the native error.cfm that comes with the Lucee package.
I have to add it even though it isn't likely the cause. Search your code for any abort. It could be someone was testing a routine and was aborting to see how far Lucee was processing.
Hope these suggestions help.

2sxc: 404 Error after adding App module on the page. API is missing?

I have a problem when placing an App module(v 8.4.8) on a page. When I placed an App module on a page I got a pop up saying "Had an error talking to the server (status 404). if you are an advanced user you can learn more about what went wrong - discover how on 2sxc.org/help?tag=debug".
This error happens on whatever action I try to do: trying to add and app, refresh page etc.
I checked a communication to the server using Firebug and seems that one of APIs are missing:
~/desktopmodules/2sxc/api/view/Module/GetSelectableApps
Referer: ~/desktopmodules/tosic_sexycontent/dist/dnn/ui.html?sxcver=8.4.8.19191
Did I missed something? Should I make some configuration after SexyContent module install (v 8.4.8)?
I just checked a video by Daniel Mettler where he showed how to install a module and seems that process is simple. Nothing to worry about.
Does anybody has any idea what might went wrong here?
The same actually happens when I install and Content module: Error about missing APIs:
~/desktopmodules/2sxc/api/view/Module/GetSelectableContentTypes
~/desktopmodules/2sxc/api/view/Module/GetSelectableTemplates
Thanks a lot for your time
My best guess is that it's an issue with the dnn domain/path configuration. So basically my guess is that
you have multiple domains, and if this is configured incorrectly, the paths in the js-calls won't fully match the original one
you have sub-portal (with paths like /products/) or something, and this isn't configured correctly in dnn
languages in portal-paths are causing similar issues.
So please compare EXACTLY the full base path and see if that's the issue.

Resources