Cheap Shared Hosting

Wednesday, April 2, 2008

Weird MTIfNonEmpty bug

Had a problem today with MovableType 3.2 - MTIfNonEmpty kept insisting that a field coming out of the database was empty. I sanity-checked it to death, and that damn string was not empty, but MTIfNonEmpty just wouldn't work. No idea why.

So I tried a work around using another comparison tag (sorry it's late, and I don't remember what it was) - basically comparing the tag to an empty string... And this time it decided that even empty strings were not empty... WTF?

I ended up fixing it by just having the MT template write out PHP to do the comparison, which of course worked fine. The only thing I could figure was that the fact that field I was doing the comparison on was an "extra field", that somehow screwed it up. Who knows?

No comments: