In Open Atrium 2 we have had a situation with backwards compatibility where a message_type text fragment is updated to use a new hardcoded token like @{message:user:name}. However, existing messages in the database were not saved with this new fragment, so they don't have the token. Thus, views like Recent Activity end up showing the new @{message:user:name} text in all of the older messages.
We desire a patch that replaces any un-resolved hardcoded tokens with normal "live" tokens. For example, replacing @{message:user:name} with [message:user:name] for older messages that didn't have the hardcoded token. While the data displayed for the old message is not necessarily correct, it's a better way to handle a bad situation than just removing the token or showing the @{...} text itself.
Patch forthcoming...
Comment | File | Size | Author |
---|---|---|---|
#3 | message-token.jpg | 133.95 KB | amitaibu |
#1 | message-token_replace-2046591-1.patch | 905 bytes | mpotter |
Comments
Comment #1
mpotter CreditAttribution: mpotter commentedMight be a better way to do this, but here is a patch to start with. Might want to add some options for controlling this at some point.
Comment #3
amitaibuComment #4
bluegeek9 CreditAttribution: bluegeek9 as a volunteer commented