Troubleshooting

If you're encountering an issue with Ansel take these steps before submitting a support ticket.

Check the Developer logs

Ansel 3 does a bit more logging of potential error messages than previous versions of Ansel. If you're encountering an issue hopefully it is getting logged. Please share the log messages when reporting an issue if they are available.

Missing rendered images

If an image is not rendering (it is returning a 404) but it has a URL there are a couple things you can check. In your're using the :resize modifier in your Ansel tags the Ansel Saves folder should contain an _ansel_image_cache folder. If there is not then the Saves folder may not be writable or someone or something deleted the _ansel_image_cache folder. If the _ansel_image_cache folder exists but you do not see the resized image in that folder then you should check the user/cache/ansel_persistent directory. In an effort to reduce overhead and unnecessary image generation Ansel creates a simple text cache file in the user/cache/ansel_persistent directory that correlates to the usage of an Ansel field or module tag. Delete all the contents of the persistent directory, then try reloading the page containing your Ansel tags. If this was the issue you were experiencing then your resized images should be regenerated and display as expected.

Using in Channel Form

Ansel does not currently work in channel:form tags. As far as we can tell this is not an an issue with the new 3.0 version. The old 2.3.4 version also does not work in channel:form tags in ExpressionEngine 7.5.x. It appears something has changed in ExpressionEngine that affects Ansel's usage in channel:form tags but we have not found a fix.