On Aug 18, 12:18 pm, rio <[EMAIL PROTECTED]> wrote: > i got the same problem as you, Andrew. The simplest way is to enable > logging in your prod and take a look at the log. This could help you a > lot. Actually I found the solution of my problem in the server's log, > but it doesn't matter. Be sure you set up the appropriate right with > "symfony fix-perms" and set the appropriate DB connection settings.
Another option is to use a mixin to add an exception handler - we use this technique to send errors as emails from our production web servers. -- --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
