Things doesn't always go according to plan. If you experience issues with Imager, here are some things you can do to investigate and find a solution yourself, or get more information for when you submit an issue.
# Is it cached?
By default, caching is turned on in Imager, via the
setting. If caching is turned on and a transform already exists in
imagerSystemPath, most of the transform handling will be skipped.
When debugging certain types of issues, like issues wit optimizer or external
storages, it's essential to either turn off caching, or clearing the relevant
caches if that's preferable.
Also note that download of external files is cached accurding to the
cacheDurationRemoteFiles config settings. This
works seperately from the transform-caching and must be disabled/cleared
if your issue involves files downloaded from an external source.
This should give you an hint of what went wrong. If you submit an issue, please provide as much of the stacktrace as possible, but make sure that you anonymize any sensitive details.
# Debug toolbar and logs
Not all errors result in an exception, and you can't always enable
So the next step is to enable the debug toolbar in the "Preferences"
section on your user.
With the debug toolbar enabled, go to the "Logs" section, and filter the logs by either choosing "Error" in the "Type" column dropdown, or filter the category column on "imager".
The debug toolbar is nice for debugging errors that occur during a normal
page load. But sometimes things happen at odd times. For those, you need
to comb through your logs. They are located in
storage/logs, and the
relevant ones are:
web.logfor errors that occur during normal web requests.
console.logfor errors that occur during console requests.
queue.logfor errors that occur during queue jobs.
phperrors.logfor errors cast by PHP itself.
Again, you can search for "[error]" or "imager" to find relevant errors.
# Reduce the complexity
Sometimes there's a lot going on in a single transform. Try removing some
of the complexity, and maybe you'll be able to more accurately pinpoint
what the underlying issue is. Maybe removing that watermark solves it?
Or maybe try running optimizers during runtime (through the
config setting), instead of as a queue job? Or turning off optimizers
altogether? Does it happen for all images, or just a specific one?
When you post an issue, let us know what you've tried.
# Did anything happen?
If there isn't anything in the logs, make sure to check what's going on in
imagerSystemPath. Did the file get created? At least this will give
you an idea if the transform works or not, and maybe it's just an issue with
imagerUrl or upload to an external storage.
# Post an issue
If you're still stumped, please post an issue in the github repository. Make sure to supply as much information about your issue as possible, and make sure to follow the issue template.