I hve also tried to disable the default module since my layout.php consists of components only. No need for calling an module/action by default. But I was also unsuccessfull like Alexander
Stefan Koopmanschap wrote: > Hi, > > Tried accessing the default module through the _dev version of your > site? That will tell you which exception happens. > > There's a fair chance though that you get the exception because the > 404 handling (IIRC) goes through the default module, unless you've > created your own 404 handling. So it should give a 404 but the module > handling the 404 is gone, resulting in a 500. > > keep in mind, I'm just thinking out loud here, I'm not entirely sure > this is it, but this may just be it. > > Stefan > > On Jul 25, 4:45 pm, Alexander Deruwe <[EMAIL PROTECTED]> > wrote: > >> Hey everyone, >> >> After disabling the default module, when trying to access it I get an >> exception 'default module not enabled' - on production this goes to a >> symfony error 500 page. >> Why does this not just cause a 404? >> >> I think I can change the error 500 page by updating web/error500.php, >> but that's beside the point - I've disabled the default module to get >> rid of it, not to get exceptions about it being disabled. >> >> Is there any way around this? >> >> Cheers, >> >> Alexander >> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
