[eluser]koorb[/eluser]
Ok, so I do have a problem with the poor debugging messages from CI. But that's a little beside the point of this topic. I do love CI I use it all the time. I have extended the Log library so it's a little saner, more common logging format and logging to just *one file*!
But the thing that really causes me problems at the moment is the debug logging around routes. So I get a debug message "Router Class Initialized" and an error message "404 Page Not Found -->" and that's all. So whether I'm using simple routes or regex it's very hard to see what the problem is, what exactly is the "-->" in that error message? It would really help if that error included exactly which controller it couldn't find. It would also help if the debugging included the actual request segments and the routed segments so you could see better what CI was trying to do with your routes. "Router Class Initialized" is useful for developers of CI but developing apps with CI that's not especially useful information.
Along with that though is that a 404 error is logged even if the controller is there but there is some errors within the method, it is very misleading. Why does that happen?
Sorry to moan, I do love CI :-)
