On Aug 18, 12:35 pm, rio <[EMAIL PROTECTED]> wrote: > The problem was in the DB. Strangely in the "dev" environment I could > connect to the DB and everything worked fine, and in the "prod" > environment it causes an exception and throws an "Internal server > error 500". So I changed the DB user settings to root and got it > working. Not the best solution but... The problem was that I was not > able to get an readable error message from symfony. I tried enabling > debugging mode, logging, custom error messages, etc. Nothing changed - > still got symfony's default "Error 500" page. Any ideas how could I > debug easily in the "prod" environment or just get readable error > messages (sorry it the question was answered before)? 10x :)
Usually the symfony classes haven't loaded with a 500 error from Apache, so the best place to look for clues is your Apache error log. -- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
