Getting help and support

Start with this documentation and the Troubleshooting guide—many setup and runtime issues are covered there.

Community (item comments)

• Best for: General questions, tips, and discussion with other buyers.
• Where: ElmapiCMS on CodeCanyon — Comments

Email

• Best for: Technical problems, bug reports, and license or purchase questions.
• Email: [email protected]
• Include when you can:
  • Your Envato purchase code or GitHub username
  • What you expected vs what happened
  • Steps to reproduce
  • Errors or excerpts from storage/logs/laravel.log
  • Environment: PHP version, database, hosting type (e.g. shared / VPS / Laravel Cloud)

GitHub Issues

If you have GitHub access, you can use GitHub issues to report bugs and feature requests.

• Best for: Bug reports and regressions—something in the product is broken and you can describe how to reproduce it.
• Where: Issues on the ElmapiCMS repository you have access to.
• Tips: Search existing issues first. One problem per issue, with version (tag or commit), environment, and minimal reproduction steps. Redact secrets and never paste .env contents.

GitHub Discussions

• Best for: How‑to questions, integration advice, and feature ideas that are not a confirmed bug.
• Where: Discussions

Releases and source

• Releases: github.com/elmapicms/elmapicms/releases for versioned ZIPs and notes.
• Security-sensitive reports (exploits, undisclosed vulnerabilities): prefer email to [email protected] rather than a public Issue.

We aim to respond as quickly as we can; including logs and reproduction steps speeds things up for every channel.