Blog Sections Open

Understanding miniShop2 Email Template Placeholders for New Orders

How to reason about miniShop2 email placeholders when the expected customer email field does not appear under the name you assumed.

Email templates are one of the first places where integration assumptions show up. In miniShop2, order data may be available, but not always under the placeholder name a developer expects at first glance.

The practical lesson from this discussion is simple: email templates should be debugged against the actual order payload and placeholder map, not against memory or naming guesses. Fields like customer email often exist, but under the order structure or naming convention the package itself uses internally.

As an ecosystem topic, this is worth keeping because package integrations succeed or fail on small details like this, and the documentation trail is not always obvious.

Source: miniShop2 documentation and miniShop2 on GitHub.

Newer post

Evo Bootstrap Manager Beta: A More Responsive Manager UI for Evolution CMS

A look at the Evo Bootstrap Manager beta and how it modernized the Evolution CMS manager interface.

Older post

MobileTemplateSwitcher 1.4.1 for Evolution CMS: A Practical Mobile Routing Layer

An ecosystem note on MobileTemplateSwitcher 1.4.1 and the kinds of mobile detection and redirect control it brought to Evolution CMS.