[eluser]coffeeandcode[/eluser]
Alright, I figured it out. Updating here for the sake of anyone finding this through a search.
It was a stupid error, as I had hoped. I have a content model that handles things that don't make sense as data - items for a carousel, a list of banners, etc. I was putting everything in the same model, and it started to get unwieldy, so I used the content model as a front end to other models - one for banners, one for carousel items, etc.
So in my controller I did:
Code:
$banners = $this->content->banners($section)
And in the content model I had:
Code:
function banners($section) {
return $this->banners($section);
}
When I should have had:
Code:
function banners($section) {
return $this->banners->get($section);
}
Instead of requesting the content from the banners model, I was calling the banners method again and again. Infinite recursion. So, it was my fault
hut:
Out of curiosity though, should CI be able to handle this better and produce a more helpful error message? Or is it the kind of situation where it has no way of knowing about the error? It seems like having /error/500.html in the uri string would provide a way to handle it....
Thanks!