Quote from: ThaClown at Jul 07, 2011, 03:29 PM
Here is my structure:
The call:
[[!getResources? &resources=`5` &tpl=`chunk_footer_left` &includeTVs=`1` &processTVs=`1` &tvPrefix=``]]
The tpl chunk (chunk_footer_left):
[[+tv.footer_content_left]]
The TV called in the chunk (tv.footer_content_left):
input: RichText
output: Default
In the TV I simply put some HTML content.
when you’re using
then ->
can confirm tvs are broken in 2.1.2 all my image tvs no longer work, paths are fine, calls are fine tvs in template are +tv.mytv etc etc, hate to say it guys, and I know I am one of those pain in the arse designers who always complain and moan, but modx updates are really reminding me more and more of drupal updates. The last update to 2.1.1 broke all my tvs as well and had to restructure them, got them to work, but geez guys...
all packages are up to date but just so it’s not asked for here’s the call:
[[!getResources? &parents=`10` &limit=`1` &tpl=`leadstory` &includeContent=`0` &showHidden=`1` &tvPrefix=`tv.`&includeTVs=`1` &processTVs=`1`]]
and the tv in the template:
[[+tv.ArtPhoto]]
The core may be fine, but there are some extras that just have to be on top of new updates, wayfinder, getpage, getresources, formit, register, I mean the "core" may be perfect, but what use is it when 99.9% of sites use a certain set of addons for client after client. I mean some packages get updated yet the docs on RTFM aren’t, or there is no mention of major template changes, etc etc etc. Plus being told to file at github or bugs or no answer at all here in the forums, is really exhuasting after spending hours troubleshooting and googling for solutions, this thread came up for googling: "modx 2.1.2 getresources tv" so I am posting.
Since evo, revo has caused some serious headaches, I always test locally for major updates, but I like to keep my sites tip top to keep the bad guys out, I am already missing evo.
-
MODX Staff
- 10,725 Posts
Can you be more specific about how your image TV’s are "not working", so an appropriate bug ticket is filed and the problem is addressed ASAP. They appear to be working for me in 2.1.1 and 2.1.2 just fine in simple tests.
See also
http://modxcms.com/forums/index.php/topic,66419.msg374500.html#msg374500
In my case getResources works, but the associated tags made with toLinks and tagLister, apparently well-formed, do not lead to anywhere.
[Solved] My bit anyway. Nested cached snippet within un-cached chunk - I think. 2.1.2 upgrade revealed error.
MODX Revolution 2.6.5-pl (traditional)
Hosted on MODX Cloud
Skype: nicbaldeagle
the image simply don’t show, when looking at the page’s source, the url is correct <img src="/assets/html_code/images/the_image_I_want_shown.jpg" />
in 2.1.1 the url is the same, I confirmed by creating a second install of the same site using 2.1.1 and they showed up just fine, the tvs input and output are set correctly but even though the path is correct and the images appear in the backend for the tv in the resource editor, nothing appears in the frontend.
I have double checked all paths in the system settings, and made sure they were correct by looking at phpinfo, and confirmed that both the tvs and tinyMCE all navigate the folder tree and are able to set the images, only the images set by the tvs do not appear in the frontend.
☆ A M B ☆
