Answers.Body: <p>This is expected behavior. This feature was changed due to a security vulnerability and is mentioned in the <a href="https://sprout.barrelstrengthdesign.com/docs/email/installing-and-updating-craft-3.html#upgrading-to-email-v4-2-0" rel="nofollow noreferrer">upgrade notes</a>.</p>
  <p>To create similar behavior you will need to confine your dynamic variables in the Control Panel to the <em>Subject</em> or <em>Default Body</em> fields. Any other custom variables will need to be added and managed in a <a href="https://sprout.barrelstrengthdesign.com/docs/email/template-overrides.html" rel="nofollow noreferrer">custom email template</a>.</p>
  <p>We will consider adding back improved functionality in the CP workflow if we can find a way to do it safely.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-12-01T13:46:28.897Z
Answers.LastActivityDate: 2020-12-01T13:46:28.897Z
Answers.UserDisplayName: Ben Parizek
Body: <p>I upgraded my whole system: Craft Pro (2.9.2 to 3.5.15.1), Sprout Email Pro (2.4.7 to 4.4.8), and several others.</p>
  <p>After fixing many errors, most occurred with Sprout Email, I now have only one major problem with Sprout Email: object variables will not resolve in text and redactor field in emails, although it has worked for several years before!</p>
  <p>Object variables in the subject line will resolve and be shown in emails, all others are output as text: <code>{ myObjectVariable }</code></p>
  <p>I changed the syntax to <code>{{ object.myVariable }}</code>, but it doesn't work with that either!</p>
  <p>One interesting thing: When I click on preview in the notification email list, the <code>{{ object.myVariable }}</code> are replaced with the values from the last submitted form (= saved entry), the <code>{ myObjectVariable }</code> are not.</p>
  <p>What is going wrong?</p>
  
Tags: <plugin-sproutemail>
Title: Sprout Email: object variables will not resolve in text and redactor field since upgrade
ThreadText: # Sprout Email: object variables will not resolve in text and redactor field since upgrade
  
  (Asked by: username_0 on 2020-11-21)
  
  I upgraded my whole system: Craft Pro (2.9.2 to 3.5.15.1), Sprout Email Pro (2.4.7 to 4.4.8), and several others.
  
  After fixing many errors, most occurred with Sprout Email, I now have only one major problem with Sprout Email: object variables will not resolve in text and redactor field in emails, although it has worked for several years before!
  
  Object variables in the subject line will resolve and be shown in emails, all others are output as text: `{ myObjectVariable }`
  
  I changed the syntax to `{{ object.myVariable }}`, but it doesn't work with that either!
  
  One interesting thing: When I click on preview in the notification email list, the `{{ object.myVariable }}` are replaced with the values from the last submitted form (= saved entry), the `{ myObjectVariable }` are not.
  
  What is going wrong?
  
  **Tags:** plugin-sproutemail
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-12-01. Score: 2 | Accepted answer
  
  This is expected behavior. This feature was changed due to a security vulnerability and is mentioned in the [upgrade notes](https://sprout.barrelstrengthdesign.com/docs/email/installing-and-updating-craft-3.html#upgrading-to-email-v4-2-0).
  
  To create similar behavior you will need to confine your dynamic variables in the Control Panel to the *Subject* or *Default Body* fields. Any other custom variables will need to be added and managed in a [custom email template](https://sprout.barrelstrengthdesign.com/docs/email/template-overrides.html).
  
  We will consider adding back improved functionality in the CP workflow if we can find a way to do it safely.
  
  
  ---
  
  