Multi-site and translations
Plans and their user groups are global (a membership is to your whole Craft install), but everything a visitor sees follows their site:
- Checkout links are on the current site, and Stripe returns visitors to the Success/Cancel path on that same site.
- Stripe Checkout's language is the site's language when Stripe supports it (
fr-FR→ French,fr-CA→ Canadian French), else Stripe picks from the browser. - Guest checkout remembers the site the guest started on: their new account is affiliated with it, so Craft's activation email uses that site's URLs and language. A site handle Velvet Rope doesn't know is ignored — it never invents one.
- Gift emails link the redeem page on the site the gift was bought on, in that site's language.
- Dunning emails use the member's preferred language.
- Plan gates apply on every site; URI patterns are matched against the path within each site.
- Plan names go through Craft's translations with the
sitecategory, like your other site strings: add'Gold' => 'Or'totranslations/fr/site.php(orlang/fr/site.php). - GraphQL takes a
siteargument for translated names and that site's links.
Email wording is edited per language in Utilities → System Messages. Control-panel strings use the
velvetrope translation category (lang/en/velvetrope.php).