-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do not overwrite the issued_on field when copying a donation receipt #170
Conversation
The issued_by field is not overwritten when copying a donation receipt
@bjendres I'm not sure whether this should go into a 2.2 point release or a new 2.3 minor one. Would this silently introduce a change for people only using the default template (which might be very few, but still ...)? |
Here's my two cents: people should know that they need to read the release notes before upgrading. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good (and simple enough) to me.
@jensschuppe, would have another look?
Yes....but they don't :) |
This is actually not a problem as Donation Receipts profiles don't use "real" message templates anymore, so an update to the default template will not affect existing profiles. |
Just noticed that this was only merged into |
As discussed here, the
issued_on
field should not be overwritten when copying a donation receipt. This ensures that a copy bears the correct and original date of its issuance.Apart from preserving the original
issued_on
date this PR also adjusts the default template to use the$issued_on
variable instead of$today
. Otherwise the change wouldn't have any effect.Important
If you are using a custom donation receipt template, you will need to make the above adjustments yourself! You can edit your templates within the Donation Receipts Profiles (Administer -> Administration Console -> Donation Receipts Profiles -> edit). Find all
$today
variables and simply replace them with$issued_on
.fix #169