如何用RainLab Translate插件管理October CMS自定义插件字段翻译？

Absolutely, you can make this work—RainLab Translate is designed to handle custom translatable strings beyond core system text. Here’s how to switch your plugin’s 80 field labels from file-based translations to being managed directly via the backend interface:

1. Hook Your Plugin into RainLab Translate’s Database System #

First, you’ll need to modify your custom plugin to pull translations from RainLab Translate’s database instead of static files. Start with your plugin’s Plugin.php file:

a. Set Up the Translation Loader in the Boot Method #

Add this code to your boot() method to register your plugin’s translation group and override the default file loader:

use RainLab\Translate\Models\Message;

public function boot()
{
    // Get the Laravel translator instance
    $translator = \App::make('translator');
    
    // Create a custom loader that fetches translations from RainLab's database
    $translator->addLoader('rainlab_db', function ($locale, $group, $namespace) {
        return Message::translationsForGroup($group, $locale);
    });
    
    // Assign your plugin's translation group to use the database loader
    // Replace 'myplugin' with your actual group name (matches your lang file prefix)
    $translator->load('myplugin', '*', function ($loader) {
        $loader->addNamespace('myplugin', 'rainlab_db');
    });
}

b. Migrate Existing Translations (Optional but Recommended) #

If you already have translations in your lang files, you can import them into RainLab’s database so admins don’t have to re-enter everything. Create a one-time script (or run this via a plugin update hook):

use RainLab\Translate\Models\Message;

// Import English translations as an example
$locale = 'en';
$group = 'myplugin';
$existingTranslations = include base_path('plugins/my-plugin/lang/en/myplugin.php');

foreach ($existingTranslations as $key => $value) {
    Message::firstOrCreate(
        ['locale' => $locale, 'group' => $group, 'item' => $key],
        ['value' => $value]
    );
}

2. Update Your Field Labels to Use the Translator #

Make sure all your form labels (both backend and frontend) use the translation helper with your group:

• In your fields.yaml files, reference the translation key instead of hardcoding labels:

  user_name:
      label: 'myplugin::fields.user_name'
      type: text
  

• In any frontend or backend templates, use the translation function:

  echo trans('myplugin::fields.user_name');
  

3. Manage Translations via the RainLab Translate Backend #

Once set up, admins can navigate to the RainLab Translate section in the backend. Your myplugin group will appear in the list, and they can edit all 80 field labels for every enabled language directly in the interface—no more editing files!

4. Add a Friendly Group Name (Bonus) #

To make your group easier to find in the backend, hook into RainLab’s translation group registration event:

Event::listen('rainlab.translate.registerTranslationGroups', function ($manager) {
    $manager->registerGroup('myplugin', 'My Plugin Field Labels');
});

This will display a human-readable name instead of the raw group key.

Content of the question originates from Stack Exchange, question author David Galvis