inconsistent interpreting of inclusion markup
Any idea why http://www.fortzedchallenge.com/wagn/Invitation+*type+email_config+*to gets rendered as an inclusion but http://www.fortzedchallenge.com/wagn/Invitation+*type+email_config+*subject (and http://www.fortzedchallenge.com/wagn/Invitation+*type+email_config+*message ) as markup?
Status:
closed
Not sexy, but maybe the dev time will be spent debugging...
mentioned this in the other support ticket. *subject and *message are exceptions. no other fields are set to use special inclusion behavior.
--Ethan McCutchen.....Thu Dec 02 21:49:26 -0800 2010