Hello all,
Yea it's me again, and I'm wondering if someone could tell me what I'm doing wrong here, as my TV values are not displaying properly.
Now if I happen to select one of the radio buttons (which I can barely see), the output values shows up as expected on front end.
I just have to guess at it because it's not being fully displayed in manager. Please see attached.
[ed. note: ironchip last edited this post 14 years, 8 months ago.]
Try setting the compress_js (and maybe compress_css) system settings to "No" in System -> System Settings (I'm assuming you're using Revolution).
---------------------------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using . . . PLEASE!
MODx info for everyone:
http://bobsguides.com/modx.html
My bad, I am using Revolution 2.2rc3. I changed settings for both compress_js & compress_css to No (both were originally set to Yes).
Still same view, nothing changed.
Weird, apparently this issue is isolated to just 1 of my resources, all others display the TV properly.
I even reset the compress_css & compress_js back to Yes, and still only the 1 resource not displaying TV properly.
Think I will just recreate that resource from scratch.
Well, guess I spoke too soon, now another resource I'm working on has began to display the same distorted values as previous resource I mentioned.
Seems when I select an option in the any TV is when things goes awry. Even when I go back and un-check the radio buttons, the damage does not seem to be reversible.
Yes, this is happening on every resource I work with now, starts out displaying properly in manager, as soon as I select an option, and refresh, the distorted view appears, please help.
[ed. note: ironchip last edited this post 14 years, 8 months ago.]
SOLVED: Seems the template I was using for certain resources did not agree with the TV's display.
When I changed back to the default home template, everything fell into place.
Still not sure where in template it broke though, but I'm sure I'll track it down.