On 23.12.2008, at 17:04, Jon Hancock wrote:
> very strange..any debugging tips? In the stack trace your can copy a method name and figure out partial path Merb tries to find. This will help. So far, I do not understand what path Merb tries to locate, and what partial is called from where. Could you provide a bit more details? MK --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
