What to provide in a bug report:
Additional info:
- What errors are logged:
- in the Espo log in data/logs directory;
- in the web server error log;
- in the browser console (F12 key).
- Explicit unambiguous steps for reproducing the issue. As much detail as possible.
- EspoCRM version number. If your version is not the latest, it's possible that the bug is already fixed.
- PHP version number.
- Database platform name (MySQL, MariaDB, PostgreSQL) and version number.
- Bug reports that are not clear and don't have steps to reproduce are moved to another category or deleted.
- If you are not sure whether the issue is a bug, create the topic not in the Bug Reports category (e.g. in General Discussions, where the rules are more lax).
Additional info:
- Troubleshooting article may be helpful.
- If your problem is emails not being received, notifications/reminders not being sent, workflows not processed, for a start, make sure that cron is configured and running.
- If you use a not up-to-date EspoCRM version, consider upgrading. The bug might have already been fixed.
- Requests for help posted in the Bug Reposts category will be deleted. Requests for help presented as bug reports are strongly discouraged.
- Only issues related to the EspoCRM application and official extensions should be posted in the Bug Reports section. Issues related to the documentation or site should not be posted here.
- The issue may be not a bug, but a documented behavior. Checking the docs may be reasonable.
- The issue may be with a 3rd party extension. Checking with the extension uninstalled may be reasonable.
- Do not use our Demo to demonstrate the bug. Our Demo instances are refreshed every few hours. The data will be erased.
- Please avoid using phrases like "big problem", "huge issue", "very annoying", etc. No need to use multiple exclamation marks as well.
- The issue is considered as a "bug" only once it's proven to be it. We tend to initially use the word "issue".
- No need to hijack threads. Create a new topic for a separate issue.