Issues are for tracking broken functionality and are intended for managing development work to address these.
If you have an issue with usage or need general assistance using this module, or Fastly in general please use the support infomation.
This describes what content should be added to a issue to help with an expedient resolution.
A good bug report contains the data necessary to reproduce, identify, locate and address a problem in code. Where possible it should also indicate what steps have already been taken to address the issue and their result too.
A report should be reproducible on a base install of Magento to an up to date system with no additional modules.
At a bare minimum include:
- OS name and version.
- PHP version
- Database server name and version.
- Magento version.
- Composer version.
- Description of the problem. What is happening that shouldn't?
- Description of the expected behaviour.
- Exact steps to reproduce the error.
Additional data which can help:
- Logs showing errors or behaviour.
- Steps which have been taken to try address the issue.
- Other data which indicates what may be causing the issue.
- Stack trace if any error is seen.