New in version 1.1.1
BricksMembers now supports official language packs that can be installed and updated through the normal WordPress translation update system. That means translations no longer have to live inside the main plugin ZIP. The plugin update can stay smaller, and translation improvements can be shipped separately when labels, admin screens, checkout text, Bricks elements, or help text need better wording.
This is especially useful for membership sites that run in a language other than English, but it also gives site owners more control. Some teams want the WordPress admin to match their site language. Some prefer to keep BricksMembers in English because their internal documentation, support videos, or team training uses the English labels. Others use a translation plugin such as Loco Translate and want their own wording to stay in place.
Available Language Packs
Version 1.1.1 includes language packs for the following languages:
- Arabic
- Czech
- German
- Spanish
- Persian
- French
- Hindi
- Indonesian
- Italian
- Japanese
- Korean
- Dutch
- Polish
- Brazilian Portuguese
- Russian
- Swedish
- Thai
- Tagalog/Filipino
- Turkish
- Ukrainian
- Vietnamese
- Simplified Chinese
WordPress only installs a language pack when it matches your site’s language or one of the requested languages during update checks. If your site language is not in the list yet, BricksMembers still works normally and falls back to the original English text.
Where to Find the Plugin Language Setting
- Open your WordPress admin area.
- Go to BricksMembers → Settings → General.
- Find the Plugin Language setting.
- Choose the mode that matches how you want BricksMembers to behave.
- Click Save Settings.
The setting only controls BricksMembers translations. It does not change your WordPress site language, your theme language, or the language settings of other plugins.
Which Language Mode Should You Choose?
Use site language and BRM language packs
This is the default and recommended option for most sites. BricksMembers follows your WordPress site language and can receive official BRM language packs through WordPress updates.
Choose this when you want BricksMembers to be translated automatically wherever an official language pack is available. If you also use custom translations, those custom files are loaded first. The official language pack then fills in the strings you did not customize.
Use custom translations only
Choose this when you maintain your own translations and do not want BricksMembers to request or load official BRM language packs. This is useful if your team has specific wording for memberships, courses, groups, checkout labels, or admin screens and you want full control over the translated interface.
In this mode, BricksMembers still loads custom translation files from the custom translation location used by tools such as Loco Translate. It simply ignores official BRM language packs.
Keep BricksMembers in English
Choose this when you want the BricksMembers interface to stay in English, even if your WordPress site language is different. This can be helpful while following English documentation, working with an English-speaking support team, recording training videos, or troubleshooting menu labels and settings names.
In this mode, BricksMembers skips its own translation loading and does not request BRM language-pack updates.
How Custom Translations Are Protected
If you use Loco Translate or another translation plugin, store your custom wording in that plugin’s custom location. For Loco Translate, that usually means the custom folder, not the WordPress system language-pack folder.
The reason is simple: WordPress manages official language packs inside wp-content/languages/plugins/. Files in that location can be replaced when WordPress installs a newer language pack. Custom translation files in a custom/Loco location are separate from those official update-managed files, so they are the safer place for your own wording.
BricksMembers loads custom/Loco files before official BRM language packs. That means you can override a few labels without having to translate the entire plugin yourself. For example, you might keep the German language pack enabled but change “Membership Level” to wording that better fits your product. Your custom string wins for that label, while the official pack still translates the rest of the interface.
What Happens When BricksMembers Adds New Features?
When a new BricksMembers feature adds new labels or settings, older custom translation files will not automatically contain those new strings. That is normal. If you use the default language mode, the official language pack can translate the new strings while your custom overrides continue to handle the labels you changed yourself.
If you use Use custom translations only, then you are choosing to manage those new strings yourself. After updating BricksMembers, open your translation tool and scan for new or untranslated strings.
Are Translations Required?
No. Translations are optional. BricksMembers works normally without a language pack, with language packs disabled, or with only partial translations available. Missing strings fall back to English.
This also means you can safely update BricksMembers before a language pack exists for your language. The plugin will not break because a translation is missing.
Why a Translation Might Not Look Perfect Yet
BricksMembers has a large admin interface, many Bricks Builder controls, checkout screens, automation labels, email features, group tools, payments settings, and developer-facing wording. Some translations may need refinement over time, especially where a short English label has several possible meanings in another language.
If a translated label feels wrong for your site, you have two good options. You can override only that string with a custom translation, or you can switch to Use custom translations only if you want to fully control the plugin wording. If you find a translation that should be improved for everyone, send it to support so it can be considered for a future official language-pack update.
Recommended Setup for Most Sites
For most translated sites, start with Use site language and BRM language packs. This gives you the best balance: official translations for the plugin, custom overrides when you need different wording, and automatic fallback to English for any string that is not translated yet.
Switch to Use custom translations only when your site has a carefully managed vocabulary and you do not want official language-pack updates to influence the BricksMembers interface. Switch to Keep BricksMembers in English when documentation consistency, training, or support is more important than a localized admin interface.