Answers.Body: <p>Changing a focal point will delete all the transform files as well as transform index entries, so I suspect that you're just seeing cached data.</p>
  
  <p>The reason why it works when changing quality is that that will actually affect the path where the transform is located, so the browser will actually have to look for the new file instead of assuming that the cached version is safe to use.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-12-09T09:43:00.320Z
Answers.Text: If this is the case (and I'm not ruling it out), then the first call to the re-focal-pointed image would never be cached, since it's a direct (API?) call to Craft to regenerate the image, and the path is wildly different. I'll have to retest to see if this is happening.
Answers.UserDisplayName: Sandwich
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-12-07T13:18:00.123Z
Answers.LastActivityDate: 2018-12-07T13:18:00.123Z
Answers.UserDisplayName: Andris Sevcenko
Body: <p>I've got a basic image transform in a template:</p>
  
  <pre><code>{% set crop = {
      mode: 'crop',
      width: 560,
      height: 550,
      quality: 80
  } %}
  
  &lt;img src="{{ image.getUrl(crop) }}"&gt;
  </code></pre>
  
  <p>Once the transforms are generated for a page, it seems like changes to the focal point don't trigger a regeneration of the image transform. Altering the template code (eg. from <code>quality: 80</code> to <code>quality: 79</code>) <em>does</em> trigger the regeneration of the image.</p>
  
  <p>Is this expected behavior?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-12-06T21:13:13.160Z
Comments.Text: That isn’t expected behavior, no. We’ll look into it and get back to you.
Comments.UserDisplayName: Brandon Kelly
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-05-05T20:09:01.097Z
Comments.Text: @BrandonKelly Was this ever addressed? I have a related question: if I'm defining a transform in a template (eg. `{% set crop = { width: 640, height: 640 } %}`), do I need to specify the `position` parameter and somehow pass the focal point to it, or does an image transform automatically look up the focal point of the image?
Comments.UserDisplayName: Sandwich
Tags: <image-transforms><focal-point>
Title: Craft isn't regenerating the image transform when the focal point changes
ThreadText: # Craft isn't regenerating the image transform when the focal point changes
  
  (Asked by: username_0 on 2018-11-14)
  
  I've got a basic image transform in a template:
  
  ```
  {% set crop = {
      mode: 'crop',
      width: 560,
      height: 550,
      quality: 80
  } %}
  
  <img src="{{ image.getUrl(crop) }}">
  
  ```
  
  Once the transforms are generated for a page, it seems like changes to the focal point don't trigger a regeneration of the image transform. Altering the template code (eg. from `quality: 80` to `quality: 79`) *does* trigger the regeneration of the image.
  
  Is this expected behavior?
  
  **Tags:** image-transforms, focal-point
  
  > **Comments:**
  > **username_1**: That isn’t expected behavior, no. We’ll look into it and get back to you.  
  > **username_0**: @username_1 Was this ever addressed? I have a related question: if I'm defining a transform in a template (eg. `{% set crop = { width: 640, height: 640 } %}`), do I need to specify the `position` parameter and somehow pass the focal point to it, or does an image transform automatically look up the focal point of the image?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2018-12-07. Score: 1
  
  Changing a focal point will delete all the transform files as well as transform index entries, so I suspect that you're just seeing cached data.
  
  The reason why it works when changing quality is that that will actually affect the path where the transform is located, so the browser will actually have to look for the new file instead of assuming that the cached version is safe to use.
  
  > **Comments:**
  > **username_0**: If this is the case (and I'm not ruling it out), then the first call to the re-focal-pointed image would never be cached, since it's a direct (API?) call to Craft to regenerate the image, and the path is wildly different. I'll have to retest to see if this is happening.  
  
  ---
  
  