getResources broken in 2.1.2-pl?

5,888 Posts

Bruno17 Reply #21, 15 years, 2 months ago

Quote from: dez at Jul 08, 2011, 04:40 PM

workaround for image based tvs at least is to set an explicit url in the system setting FILE MANAGER URL to: http://site.com/assets/
or on localhost http://localhost/sitename/assets/ regardless if the file manager path or url are set to relative or not, the file manager path still needs to be set to /assets/ for tinyMCE and TVs to navigate file tree

I am most likely mistaken, but I don’t think this should be necessary should it? I have never needed to set it to http in any previous install of revo or evo,
so this may actually not be a getresources error, humble apologies for my meltdown if it is not.

also I figure I will simply mention this because it may have some bearing, within a getresources template I have if snippet calls which rely on TV’s if; if the parent is this show this tv...right now in 2.1.1 they work as they should, now with the update, they don’t, only "static" tvs and with the file manager url set as above will work

there must be something wrong with your configuration. You don’t need to set any static urls other than they are in your config.inc.php.
And I would think FILE MANAGER URL has nothing todo with your frontend-output. Mine is mostly just: /
Are you sure you have <base href="[[++site_url]]" /> in your template?

-------------------------------

you can buy me a beer, if you like MIGX

http://webcmsolutions.de/migx.html

Thanks!

21 Posts

dez Reply #22, 15 years, 2 months ago

yep, as always the answer must be a problem with my configuration, as I said, I have checked my paths and urls in system settings over and over;making sure by taking a look at phpinfo.

the output is correct for the tv, read previous posts, but NOTHING SHOWS, soooooooo by actually setting url like that shows the image WHY I HAVE NO IDEA, go figure. I believe this update specifically addresses an issue with the File browser to thumbnail path issue, or something like that maybe this is what is causing the issue with getresources?

And if my configuration was wrong, why does the exact same site on 2.1.1 perform fine?
Now, I find it odd that I am not the only one complaining of funky behavior after this update, so even though i am at fault, all sites running on 2.1.1 with getresources current package output just fine.

☆ A M B ☆
350 Posts

Menno Pietersen Reply #23, 15 years, 2 months ago

I have problems as well.. Good setup, works in 2.1.1 > breaks in 2.1.2

All problems are related with getResources for me...

MODX Ambassador (NL) | Responsive web design specialist, developer & speaker
DESIGNfromWITHIN, MPThemes and Any Screen Size
Follow me on Twitter | Read my blog | My code on GitHub

MODX Staff
10,725 Posts

opengeek Reply #24, 15 years, 2 months ago

Your going to have to discuss details of what is not working. It’s working fine for me. If specific TV’s are not rendering as expected, that may be a different issue and not necessarily related to getResources. As for the query issue with the &resources parameter, that is a bug related to a change in xPDO and needs to be addressed.

Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek

5 Posts

DutchIris Reply #25, 15 years, 2 months ago

I am not sure if we are all talking about the exact same situation but I have been having a similar problem and found a fix.

After installing Revo 2.1.2 and getresources 1.3.0, suddenly getresources didn’t produce any output. Previously (under Revo 2.1.0) it had produced output. I am not sure what version of getresources I was running at that time.

My getresources call looked like this:

[[getResources? &tpl=`homecontentblock` &resources=`15` &limit=`1` &includeContent=`1` &showHidden=`1`]]

When debugging, I noticed that in the SQL query, the ’parents’ property was always used. And since I hadn’t specified a parent in the getresource call, it just used the id of the resource the call was in. But that resource doesn’t have any children! So, because that condition in the SQL query was an "AND" condition, rather than an "OR" condition, I got no output.

I resolved this by adding &parents=`0` to the getresources call. It works fine now.

☆ A M B ☆
350 Posts

Menno Pietersen Reply #26, 15 years, 2 months ago

You sir, are my hero!

Old code:

[[!getResources? &resources=`[[$settings_page_id]]` &tpl=`chunk_footer_contact` &includeTVs=`1` &processTVs=`1` &tvPrefix=``]]

Works here now with:

[[!getResources? &resources=`[[$settings_page_id]]` &tpl=`chunk_footer_contact` &includeTVs=`1` &processTVs=`1` &tvPrefix=`` &parents=`0` &includeContent=`1` &showHidden=`1`]]

MODX Ambassador (NL) | Responsive web design specialist, developer & speaker
DESIGNfromWITHIN, MPThemes and Any Screen Size
Follow me on Twitter | Read my blog | My code on GitHub

101 Posts

Hori76 Reply #27, 15 years, 2 months ago

I’ve got the exact same problem as Manuele:
http://bugs.modx.com/issues/5201

I’ve already had a lot of trouble with the previous upgrade and now it happens all over again!

All my getResources calls are broken, I always use TV’s in the tpl-chunk, and it works fine in all previous revo versions.

Don't believe anything you read on the net. Except this.

101 Posts

Hori76 Reply #28, 15 years, 2 months ago

Ok, found it, apparently it’s a nested and cached - uncached problem:

http://modxcms.com/forums/index.php?topic=66419.0

Don't believe anything you read on the net. Except this.

☆ A M B ☆
318 Posts

freejung Reply #29, 15 years, 2 months ago

Just to add to this, as I also had the same problem: something about the &depth parameter is not working properly with this as well. I had this code:

[[getResources? &parents=`1` &resources=`[[*resource-docs]]` &sortby=`FIELD(modResource.id, [[*resource-docs]] )` &sortdir=`ASC` &tpl=`resource-docs.tpl` &tplFirst=`resource-docsFirst.tpl` &limit=`0` &depth=`1` &includeTVs=`1` &processTVs=`1` &tvPrefix=``]]

which was working fine in 2.1.1. After upgrading to 2.1.2 it was listing no docs, so I changed it to:

[[getResources? &parents=`0` &resources=`[[*resource-docs]]` &sortby=`FIELD(modResource.id, [[*resource-docs]] )` &sortdir=`ASC` &tpl=`resource-docs.tpl` &tplFirst=`resource-docsFirst.tpl` &limit=`0` &depth=`1` &includeTVs=`1` &processTVs=`1` &tvPrefix=``]]

and it still listed no docs. So I removed the &depth parameter and it works fine. Oddly, it also works fine with depth set to 3, but not less. None of my docs have children anyway, so it doesn’t really matter, but I thought I’d post it in case anyone else has a similar problem. This code is working fine for me:

[[getResources? &parents=`0` &resources=`[[*resource-docs]]` &sortby=`FIELD(modResource.id, [[*resource-docs]] )` &sortdir=`ASC` &tpl=`resource-docs.tpl` &tplFirst=`resource-docsFirst.tpl` &limit=`0` &includeTVs=`1` &processTVs=`1` &tvPrefix=``]]

MODX Staff
10,725 Posts

opengeek Reply #30, 15 years, 2 months ago

Quote from: esnyder at Jul 15, 2011, 01:02 PM

Just to add to this, as I also had the same problem: something about the &depth parameter is not working properly with this as well. I had this code:

This is actually an issue with the resources property due to changes in xPDO that were applied to MODX 2.1.2. This is fixed now; if you are using MODX 2.1.2 please update to getResources 1.3.1 which should resolve the issue for you.

Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek