Email templates

Solidshop sends transactional emails for events like order confirmation, payment received, and shipping updates. All email templates are editable from the admin — no code changes needed.

Go to your store and open the Email Templates tab. You will see a list of template groups. Click any template to open it in the built-in code editor (with syntax highlighting) where you can edit the HTML content. Each template supports dynamic variables for order details, customer info, and store data.

You can preview a template before saving to see how it will look, and reset any template back to its default content if needed.

The Email Templates tab, and editing or previewing a template, is open to Solidshop administrators and to users allowed to manage shipping or payments — the same people who can open the store screen. Access to the administrator alone is not enough.

What a template can use

Templates are written in Twig, and an email template can use the part of it that shapes text and markup:

  • Tags: if / elseif / else, for, set, block, apply, with, and include for the parts Solidshop and its add-ons ship (such as the bank transfer details).
  • Filters: default, e / escape, raw, length, first, last, split, join, slice, replace, trim, upper, lower, capitalize, title, striptags, nl2br, format, date, number_format, round, abs and url_encode.
  • Functions: _('LANGUAGE_KEY') and sprintf('LANGUAGE_KEY', …) for translated text, currencyFormat(amount), dateFormat(date), and min, max and range.
  • Data: the variables the email is sent with — the order, its products, the customer and the store (store.name, store.params.email_accent_color, …) — and the usual tests such as is defined and is empty. Values can be read, but no method can be called on them.
  • Not your payment or carrier settings: the store’s payment and shipping-carrier settings hold your Stripe, PayPal, Square and Shippo keys, so templates never receive them. The bank transfer details an order confirmation shows come as bank_transfer (for example bank_transfer.iban), and the shipped bank transfer block already prints them.

Anything else — macros, extends, the map / filter / sort filters, source(), constant(), method calls — is refused. The template runs on every order and payment, so it is kept to what an email needs.

Save checks the template first, by rendering it with the same sample order Preview uses, and refuses it, naming the problem, if it uses something outside this list, has a syntax error or includes a file that does not exist.

A template saved before this check, or one whose problem only shows on some orders, is still sent: the email goes out with the default template for that email instead of yours, and the error is written to the Joomla log (category com_solidshop). Preview shows the same error, so preview a template after editing it and fix whatever it names.

Emails are sent asynchronously via a background queue (plg_task_solidshopemailqueue). Make sure your Joomla task scheduler is running — go to System → Manage → Scheduled Tasks and verify the Solidshop: Process Email Queue task exists, is enabled and has a recent last run. If you use cron-based task execution, ensure your server’s cron job runs cli/joomla.php scheduler:run --all --live-site=https://www.example.com/ with your site’s address, so the links in e-mails a task builds point at your site. See Set up the email queue.

The email queue

Every email Solidshop sends passes through the queue, and you can inspect it under Solidshop → System → Email Queue. Each row shows the recipient, subject, the context that produced it (order confirmation, shipment, cancellation, and so on), the related order, its delivery status — pending, sent, or failed — how many delivery attempts have been made, and the last error message when a send failed. Click a subject to preview the exact email body in a new tab.

A failed email is one that exhausted its retry budget — typically a mail server problem or an invalid address. Once you have fixed the cause, select the failed rows and click Retry in the toolbar: they return to pending with a fresh retry budget and go out on the next scheduled queue run. Rows you no longer need can be deleted from the same toolbar.

To send a customer their order confirmation again (for example after correcting their email address), use the Resend Confirmation button on the order detail page — see Orders. It re-renders the email from the order’s current state, so template fixes and order edits are picked up.