I found that s2Member’s translation loading could be more explicit and more compatible with current WordPress behavior, so I’ve patched that.
s2member-v260320.0101.zip (1.4 MB)
It may improve reliability for custom .mo files placed in either of these locations:
- modern standard
wp-content/languages/plugins/s2member-LOCALE.mo
- legacy fallback
wp-content/plugins/s2member-LOCALE.mo
That said, if a specific .mo file still fails after this change, the next likely cause is the file itself or a site-specific conflict, rather than the load path.
