Support

A person answers these, and that person wrote the code. Your message becomes a numbered ticket so neither of us loses track of it — but there is no call centre behind it.

Open a ticket

Everything technical goes through the help desk: it keeps the whole conversation, the versions and the attachments together, and gives you a tracking ID so neither of us loses the thread.

Open a new ticket

Name, email, subject and what is happening. Attach a screenshot or an error log if you have one.

Takes a minute

Check an existing ticket

Enter the tracking ID from your confirmation email to read the reply or add to the conversation.

Tracking ID required

What is covered

  • Getting it running on your hosting. If a script you bought will not install, we work out why. That is the deal.
  • Bugs. If it does not do what this site says it does, that is our problem to fix, and the fix reaches you as an update.
  • Questions about how something works. Ask.

What is not

  • Custom development. Changing a script to do something it was not built to do is paid work, not support. Ask and we will quote.
  • Your server. We cannot fix a host that has no cron, blocks outbound SMTP, or runs PHP 7.4. We can tell you that is what is wrong.
  • Other people's code. If the script works alone but breaks inside your framework, we will help you look, but we cannot debug the framework.

What to send

Support gets dramatically faster when a ticket arrives with these four things:

  1. Which script and which version. The version is at the top of the file and in the dashboard footer.
  2. The exact error text. Copy and paste it, from the page or from the server's error log — not a description of it. Most of these scripts write their own log beside themselves; that is the best source.
  3. PHP and database versions. php -v, or a phpinfo() page.
  4. What you did just before it happened.

A good bug report gets fixed in one reply.
A vague one takes four.

Try this first

  • A blank white page is almost always a PHP fatal error with display switched off. The server's error log has the real message and the line number.
  • A 500 right after installing is usually a wrong require path. The error log names the file it could not open.
  • "Headers already sent" means something printed output before the script ran — often a blank line or a byte-order mark before the opening <?php in one of your own files.
  • A database connection failure on Linux is frequently capitalisation: MariaDB database names are case sensitive there and not on Windows, which catches people moving from WAMP to a live server.
  • Nothing is sending in the Autoresponder means cron is not running. Check the heartbeat panel in its settings.

Other ways to reach us

For anything that is not a support case — a question before you buy, a feature request, a testimonial — the contact form is quicker and reaches the same person.

The manuals are worth a look first — every script also carries its full documentation in its own file header, which is always the version that matches the code you actually have.