Skip to content
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

Payment notification formatting, move greeting into table #13669

Merged
merged 1 commit into from
Feb 23, 2019

Conversation

eileenmcnaughton
Copy link
Contributor

@eileenmcnaughton eileenmcnaughton commented Feb 22, 2019

Overview

Align greeting in payment notification email

Before

screenshot from 2019-02-22 11-26-17

After

Technical Details

Comments

per #13655 (comment)

@civibot
Copy link

civibot bot commented Feb 22, 2019

(Standard links)

@magnolia61
Copy link
Contributor

magnolia61 commented Feb 22, 2019

I tested it, it does not show the greeting.
When I exhange the code:
{if $emailGreeting}<tr><td>{$emailGreeting},</td></tr>{/if}
to the line in most other templates is used it works ok (and in other templates it is not in its own tr/td
{assign var="greeting" value="{contact.email_greeting}"}{if $greeting}<p>{$greeting},</p>{/if}

@eileenmcnaughton
Copy link
Contributor Author

@magnolia61 hmm - I guess we just merged support for $emailGreeting into master branch for that template & you might not have that locally yet?

@magnolia61
Copy link
Contributor

You are right. I can confirm the template works fine on current master

@eileenmcnaughton
Copy link
Contributor Author

@monishdeb are you good to merge this follow up per @magnolia61 request

@monishdeb
Copy link
Member

Agree with the fix. Merging now.

Thanks, @magnolia61 for your review.

@monishdeb monishdeb merged commit 23fa832 into civicrm:master Feb 23, 2019
@eileenmcnaughton eileenmcnaughton deleted the payment_format branch February 23, 2019 06:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants