-
☆ A M B ☆
- 24,524 Posts
Hi Susan, you are wonderful at tracking this down! That did the trick!
To answer your other question, it is a checkbox TV, not a radio TV. If you look at the image on the first post you will see the TV as it is set up.
Thank You!
"Remember what Bilbo used to say: It's a dangerous business, Frodo, going out your door. You step onto the road, and if you don't keep your feet, there's no knowing where you might be swept off to."
-J.R.R. Tolkien from The Lord of the Rings
-
☆ A M B ☆
- 24,524 Posts
Ah, that answers my question
Anyway, what happens is the the fields from the site_content table are all loaded into the documentObject array. Then as the document is parsed, in time TVs are evaluated, and the values relevant to the document are also loaded into the documentObject array, but each TV is itself an array of TV data. When it’s time to cache the page, it checks to make sure its type is "document". But since your TV is also named type, its array overwrote the type field’s value from the database.
There are a few ways this kind of thing could be prevented, but probably the easiest will turn out to be having the save_tplvar.processor do a check against the database fields and return to the TV form with an error if the TV name is in conflict. I suspect it hasn’t come up before because the database field names aren’t what would usually be used for a TV name, and even an upper case variation such as Type wouldn’t conflict.
Thanks Susan, I am a left-handed Dyslexic, so you should be sure we will find these sort of things.
"Remember what Bilbo used to say: It's a dangerous business, Frodo, going out your door. You step onto the road, and if you don't keep your feet, there's no knowing where you might be swept off to."
-J.R.R. Tolkien from The Lord of the Rings
-
☆ A M B ☆
- 24,524 Posts
I know the feeling well. I also have a tendency to find the "corner cases", although I had my left-handedness slapped out of me by the time I was 5 or 6. Just don’t ask me for directions!
MODX Staff