Getting help

Autograph's issues are tracked in public on GitHub, at nerdgency/ee-addon-issues, shared with Nerdgency's other add-ons and labelled autograph. That's the place for bug reports and feature requests.

Security vulnerabilities are the one exception. Never report one in a public issue. Email it instead (see below).

Before you report

1. Check Troubleshooting, including the known limitations.
2. Update to the latest Autograph 1.x release. The changelog says what's been fixed.
3. Search the open and closed issues. If someone has already reported it, add a 👍 or a comment with your details rather than opening a new issue.

Reporting a bug

Open a bug report and include:

1. Versions: Autograph, ExpressionEngine and PHP. Autograph's version is on the Add-Ons screen.
2. Where it happens: a Channel Form, a member form, the control panel, or a template.
3. What you did, what you expected, and what happened instead.
4. The template, if the problem is on the front end, with the tag as written.
5. Anything in the browser's console, whether autograph.js loads, and anything in the Developer Log (Tools › Logs › Developer).

Leave out anything private

Issues are public. Signatures are personal data, so don't post real ones: sign a test entry instead. Leave out credentials and your config.php too.

Requesting a feature

Open a feature request. Say what you're collecting signatures for, and where Autograph gets in the way. There's often more than one way to solve it, and knowing why helps find the best one.

Reporting a security vulnerability

If you think you've found a security problem in Autograph, email [email protected]. Don't open a public issue or share it anywhere else until a fix is released. Include the steps to reproduce it and the Autograph, ExpressionEngine and PHP versions you tested. The security policy says what happens next.

Please test only against your own installations, and never against a site you don't own or have permission to test.