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

(dev/core#4531) Afform Mail Tokens - Fix rendering for localized/individual email #27134

Merged
merged 1 commit into from
Aug 24, 2023

Conversation

totten
Copy link
Member

@totten totten commented Aug 24, 2023

Overview

While sending the localized email, some UF's may reboot the container mid-execution. This change ensures that the listeners will be re-registered.

For steps to reproduce and more analysis, see https://lab.civicrm.org/dev/core/-/issues/4531

ping @larssandergreen

Before

  • When you "Send email" to a contact with a preferred_language, the {afform.*} tokens do not render.
  • Afform's listeners are registered during the first container boot - but not during a second or third boot (as by Drupal::setUFLocale())

After

  • The tokens do render.
  • Afform's listeners are consistently re-registered, even if the container starts multiple times.

Comments

This also makes the code prettier.

The bug is technically a regression (circa 5.53/5.54), but it's a bit old. I think 5.65-rc makes sense. (Backporting to 5.64-stable is more debatable. If others want that, then I'd be OK with it.)

…vidual email

While sending the localized email, some UF's may reboot the container
mid-execution. This change ensures that the listeners will be re-registered.

It also makes the code prettier.
@civibot
Copy link

civibot bot commented Aug 24, 2023

Thank you for contributing to CiviCRM! ❤️ We will need to test and review the PR. 👷

Introduction for new contributors
  • If this is your first PR, an admin will greenlight automated testing with the command ok to test or add to whitelist.
  • A series of tests will automatically run. You can see the results at the bottom of this page (if there are any problems, it will include a link to see what went wrong).
  • A demo site will be built where anyone can try out a version of CiviCRM that includes your changes.
  • If this process needs to be repeated, an admin will issue the command test this please to rerun tests and build a new demo site.
  • Before this PR can be merged, it needs to be reviewed. Please keep in mind that reviewers are volunteers, and their response time can vary from a few hours to a few weeks depending on their availability and their knowledge of this particular part of CiviCRM.
  • A great way to speed up this process is to "trade reviews" with someone - find an open PR that you feel able to review, and leave a comment like "I'm reviewing this now, could you please review mine?" (include a link to yours). You don't have to wait for a response to get started (and you don't have to stop at one!) the more you review, the faster this process goes for everyone 😄
  • To ensure that you are credited properly in the final release notes, please add yourself to contributor-key.yml
  • For more information about contributing, see CONTRIBUTING.md.
Quick links for reviewers

@civibot civibot bot added the master label Aug 24, 2023
@totten totten changed the base branch from master to 5.65 August 24, 2023 07:57
@civibot civibot bot added 5.65 and removed master labels Aug 24, 2023
@larssandergreen
Copy link
Contributor

Works for me, looks good, thanks @totten!

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