TV bug: doesn't store to DB if the value == default value

I don’t know it it’s intended to do as such, but this behavior returns [[!getResources? ... &tvFilters=`tvName==defaultValue` ...]] as an empty result.
http://bugs.modx.com/issues/3353

Quote from: goldsky at Jan 06, 2011, 12:32 PM

I don’t know it it’s intended to do as such, but this behavior returns [[!getResources? ... &tvFilters=`tvName==defaultValue` ...]] as an empty result.
http://bugs.modx.com/issues/3353

I’ve thought about reporting that myself a time or two. I can confirm the behavior, but I don’t know if it’s by design, but I suspect that it is.

It’s not good if it is.
Well, TV’s default value becomes cripple.

*deleted all the default values*

FWIW: this is simply an issue with the way getResources does tv filtering. In the documentation, it is noted that this will ONLY work with explicit values set for each Resource, and not with the default values or with calculated values. getResources chose efficiency over features, but other Snippets can certainly find ways to handle the default values as well—just will be a little less efficient.

I don’t understand the concept, then.

• If a user does not choose any [checkbox] because the TV has set the default value, it is not her fault if getResources does not fetch that resource.
• If MODX does not store the value because it is the same with the default value, it makes more problem.

One of them should change that basic concept.