Posted on

Sensei 2.0 and Translations

When upgrading Sensei 1.x to Sensei with WooCommerce Paid Courses, all official translations should continue to work. Although we’ve made a lot of changes under the hood, Sensei with WooCommerce Paid Courses ships with the set of translation files that were used with Sensei previously.

However, if your site has custom translations (for example, using the Loco Translate plugin) then you may run into some issues when you upgrade.

Submitting Community Translations

Before discussing per-site custom translations, it’s worth emphasizing that the best solution for translations is to submit them to the official translation repositories. This way, any translations you submit can be used by other Sensei LMS sites as well.

Strings for most Sensei LMS functionality should be submitted to the WordPress.org translation repository. Strings related to selling courses are part of the WooCommerce Paid Courses extension and should be submitted to its repository.

Sensei with WooCommerce Paid Courses will, by default, pull its translation files from the above two locations using the default WordPress update page. It’s important to note that translation files will not be built and served from WordPress.org (for Sensei LMS translations) unless the translation file is at least 95% complete. You can export the .po and .mo files and add them to your site manually for translations that do not meet this minimum threshold.

Custom Translations

If you have custom translations saved to your site, it’s possible that they may have stopped working after the upgrade to Sensei with WooCommerce Paid Courses. This is likely because those custom translations were added under the legacy woothemes-sensei text domain.

To resolve this:

  • Find the custom translation files on your server. They should be named something like woothemes-sensei-de_DE.po and woothemes-sensei-de_DE.mo. (Note that the de_DE is the language code, and may be different in your case, depending on the language you are using.)
  • Make a copy of both files.
  • Change woothemes-sensei to sensei-lms in one copy, and sensei-wc-paid-courses in the other. For example, for German translations (de_DE), you should end up with the following files:
    • sensei-lms-de_DE.po
    • sensei-lms-de_DE.mo
    • sensei-wc-paid-courses-de_DE.po
    • sensei-wc-paid-courses-de_DE.mo

Your custom translations should now work for Sensei with WooCommerce Paid Courses.

Managing Translations with Loco Translate

Some specialized setup is required in order to manage translations with Loco Translate:

You should now be able to manage all of the translations for Sensei with WooCommerce Paid Courses within Loco Translate.

Posted on

Take the Sensei 2015 Survey

It’s time for our annual Sensei customer survey, which helps us learn more about your Sensei needs, and refine our product roadmap based on your responses.

If you’re a Sensei user and you have 5 – 10 minutes to spare, please help us out by completing the survey. We really appreciate your feedback.

Take the survey

Posted on

New Development Workflow

Howdy,

If you have contributed to Sensei in the past, you would have noticed that we worked on release branches. We would branch out and accept pull requests specifically to these release branches ( e.g. release-1-9 ). This means that contributors had to keep track of the branches before submitting PR’s. This was overly complicated.

Today we have good news for you. You only need to follow the master branch. Sensei core developers will take responsibility for the complications around branching and creating specific releases. You only have to make sure that your pull requests are ready to merge.

We’ve seen a steady increase in pull request. Thank you for all your contributions so far.