When you change the message type at one point all the already existing messages are also affected.

For example you make a message type node_created:
A node with title %title was created.

Then later you replace this with:
A node with title %title was created by %author.

All the old messages will also display "...by %author". This could be solved by using versioning on the message text and link the message table by this version id. Because if it isn't done that way the only solution is to create a new message type everytime you modify the message type.

Since I can imagine the need to change a message text sooner or later is pretty common I wonder if this module is actually useful without that feature?

Comments

amitaibu’s picture

Status: Active » Closed (works as designed)

This can be considered as a feature, not a bug :)

The messages are not hardcoded in the database, only the arguments of the message. So, yes, when you change the message-text, it will apply to old and new messages.

DigitalFrontiersMedia’s picture

Category: Bug report » Feature request
Issue summary: View changes
Status: Closed (works as designed) » Active

Changing this to a Feature Request and re-opening. This "feature" pretty much kills any usefulness this module might have for archival fidelity. An option to turn on/off revisioning on this would definitely be a boon to its usefulness and satisfy both needs without killing existing expected behavior.

DigitalFrontiersMedia’s picture

Title: Modifying the text of the message type affects existing messages » Add revisioning option to allow for archival message fidelity

Changing title to reflect request...

bluegeek9’s picture

Status: Active » Closed (outdated)