So I'm trying to debug a site which has ajax calls to a module that serves xml.  Of course the debug output appended to the xml breaks it.  I've had this problem before but I never bothered looking closer at it until now.

For a customer i had to find the objects (out of hundreds) that had an attribute filled out, I figured an attribute filter would be the easiest:

If you are using suhosin you WILL end up having a problem when trying to edit a class with more than 20 attributes if you don't first increase the suhosin.post.max_vars and suhosin.request.max_vars to more than the default 200.

Here's code that I've used in a bunch of places - especially for automated syncing scripts:

Here's a little script I use when I have get the info from a class or classes:

I had to find objects that had multiple locations for a client.  This is what I came up with:

As a novice eZPublish programmer 6 year ago my biggest problem was always trying to find my data.  Of course attribute(show) was invaluable... and at first I wrote a shell script to parse that data to make it readable and years later I wrote ezfire to make that data more accessible...  But, for much of the time I was cursing and thinking - to paraphrase Mojo Nixon - "Where the hell's my data."