getResources - bug or feature?

I notice that getResources skips all documents with an empty content field using this tpl:



I created a bunch of resources with just pagetitles to play with it and it took me a while to figure out why only a few of them were retrieved by getResources.

hmm... I tested it with:



and it shows all resources, also these with empty content.
But it showed me also childchilds (goes 2levels deep from parent), so I changed


to


what seems to fix this issue

Quote from: BobRay at Oct 30, 2009, 01:31 AM

I notice that getResources skips all documents with an empty content field using this tpl:

Title: [[+pagetitle]]<br />

I created a bunch of resources with just pagetitles to play with it and it took me a while to figure out why only a few of them were retrieved by getResources.

I don’t understand what you mean BobRay; it doesn’t skip anything because it doesn’t have a content field for sure.

Also, Bruno17, that issue was reported elsewhere and will be addressed in the next release, though it should be depth=`0` which currently you cannot pass in due to the !empty() check.

IMO, if I go one level deep (&depth=`1`) from parent I want to show only the direct childs, as it is in getChildIds or as it was in Ditto, too???

OK, I see what’s happening.

There are two issues:

1. I assumed that &limit=`0` would give me all of them, but it only gives five. I’m not sure what it should do, but probably not that.

What confused me is that putting any content in the content filed moves a document onto the list of five shown.

This must have to do with the sort order, but all the docs were published to begin with so saving them shouldn’t affect publishedOn, which is the stated default for sorting.

2. I looked in the DB and confirmed that saving a document updates both editedOn and publishedOn to the current timestamp (I’ll Jira that).