getResources snippet suddenly not even returning an array

Hi all,

I’m not sure if this is just a symptom of something else, but it’s the only clue I have right now.
I had a blog set up as seen here: http://rtfm.modx.com/display/revolution20/Creating+a+Blog+in+MODx+Revolution with 2 sections.

Everything was working fine, I then added a new user and installed TinyMC for her. She logged in once and accidentally moved the two section containers around, but then moved them back and it looks fine - but all of a sudden getResources is not displaying anything, not even an array when I remove the &includeContent=`1`. I’ve tried uninstalling the rich text editor, calling the snippet cached and uncached, I’ve de- and reinstalled getResources, I’ve checked the showHidden properties ... but no luck.

Does anybody have any clue of what could have happened?

Thanks so much,
R

... no ideas? Pretty sure this isnt even a getResources issue, but since I have no idea where else to start, I’d be very grateful if somebody could give me some debugging tips!

Could she have unpublished a parent or container, or selected hide from menus?

If something is hidden or unpublished, it’s children won’t show up.

nopes, that’s not it ... I am so stumped by it not even showing an array - there’s got to be a problem with the snippet itself, it might not even have anything to do with the other user - I just don’t know how I can try debugging the snippet. Is there some kind of a tutorial or a forum post that could get me on the right track?

Are you using getPage? If so, try taking that out of the picture.

Was using getpage, deinstalled it, still nothing ...

Try deleting all the files in the /core/cache/ directory except index.php and clearing your browser cache and cookies.

If that doesn’t work. Paste your getResources tag here.

Hi Bob and thanks for your patience, I’ve been travelling some so please excuse the late answer.

I deleted the core/cache directory but I’ve made such a mess of my snippets in the meantime that I wasn’t at all surprised when it still didn’t work ...

I’ll now upgrade to 2.0.2 and then redo the whole blog-thingy, myabe it’ll work on a clean slate. Thanks for your tips and I’ll telle you what happened!

Good luck.