I encountered a funky problem during my first encounter with CatalystX::ListFramework::Builder ... and (just before throwing my hands up and Petitioning my Fellow Monks) ...solved(!) it.   W00t! W00t! :-D

To save your precious hair-follicles... here's what the problem was, and here's how I diagnosed and solved it.

The Problem:

I followed the man-page instructions most carefully, to create a DBIx::Class::Schema for my new database and to reference it properly within the configuration file. So, when I started Catalyst and entered the /admin page, I found the complete list of tables (yay!) ... but upon selecting any of those tables, I was taken to an edit screen that was ... empty. (boo hoo!)

Well, certainly not completely empty ... it had the header, the breadcrumbs bar, and the footer. But it had no table in-between. The same was consistently true for all table screens. An obviously-sensible page (and page-source...), but no table.

The Catalyst output showed nothing useful.

The Clue:

As we all know, “Firebug is a wonderful thing.” This JavaScript debugger gave me only one slim clue in the console output: “file not found.” There were no “404”s anywhere to be found.

The Solution! :

Upon very close re-inspection of the Catalyst output, I noticed that the various requests for JavaScript components looked like this: static/js/extjs/extjs-2/blah... Now mind you, the Catalyst log did not say anything further. It did not say that either the files or the path did not, in fact, exist...

But in fact, they didn't. The correct path (I had typo'd it in the configuration) should have simply been /static/js/extjs-2. No files existed at the path that was originally being used.

In closing...

I am genuinely surprised to discover that, when Catalyst is asked to serve-up a static file that does not exist, it says nothing in its log file. I am also somewhat surprised to notice that a web-browser kept equally “mum.” The upshot was, at least for me, a problem that was trivial to fix, but quite difficult to spot.

So... “now you know” and “hope it helps.” May the next hair-follicles to be preserved be your own! (They certainly were not mine.)   ;-D

Replies are listed 'Best First'.
Re: FYI: a funny problem with CatalystX::ListFramework::Builder .. solved! :-)
by Your Mother (Archbishop) on Dec 30, 2008 at 00:51 UTC

    Firebug, plugin for Firefox, has a "Net" console that would have shown the 404s in real time. Doing anything Ajaxy without Firebug is agony. Check it out. And the Web Developer plugin is also wonderful.

Re: FYI: a funny problem with CatalystX::ListFramework::Builder .. solved! :-)
by locked_user sundialsvc4 (Abbot) on Dec 30, 2008 at 22:15 UTC

    That's a very good point:   I had glommed onto the idea of using Firebug to study the problem, but I had not chosen that particular tab in the Firebug display.

    Definitely, Firebug is a “don't leave home without it” plug-in. Especially nice because it's free...

Re: FYI: a funny problem with CatalystX::ListFramework::Builder .. solved! :-)
by hobbs (Monk) on Jan 13, 2009 at 22:25 UTC
    I'm assuming that you're using Static::Simple, or else there wouldn't be any reason to expect anything about static files to be in Catalyst's logs at all. Static::Simple, by default, doesn't log anything at all, to avoid crudding up the logs. However, if you have debugging enabled in your app (with use Catalyst '-Debug' or the -d option to the standalone server, or overriding sub debug in your app), then Static::Simple will do logging of both successful requests and 404s. One way or another, the requests should be visible in your access.log.