MU-Plugins: No strings can be extracted from source code

nevermind, seems I messed up the text doamin…

• This reply was modified 2 years, 7 months ago by SoN9ne.

Actually, even with fixing the text domain, it still says

No strings can be extracted from source code

I am able to do the string translations in my PO files but it’s not seeing any changes in my code.

MU-plugins are single files by convention. If you have a folder of source files which you auto-load from the stub file then you will have to configure your bundle to scan this directory.

See https://localise.biz/wordpress/plugin/manual/bundle-config and note the “Source file paths” option.

Thanks for your response.

It seems mu-plugin support is minimal.

WordPress recommends using a proxy loader which then loads the mu-plugin from a folder which acts like a normal plugin.

This is implemented as:

mu-plugins
├── 1-olymp-wp-core.php
├── 2-oly-ott-core.php
├── 3-oly-ott-features.php
├── olymp-wp-core
├── oly-ott-core
└── oly-ott-features

Whereas every folder is a proper WordPress plugin.

Using loco.xml for mu-plugins is not possible unless I build a loco.xml in the mu-plugins folder and configure them all in it (not ideal at all). It also seems that adding “Source File Paths”, it still gives:

No strings can be extracted from source code

I even tried configuring it in the backend interface and it still never seems to work.

I tried with using the main directory:

<source>
    <directory>oly-ott-core</directory>
</source>

Then I also tried declaring every directory that has translatable files but it just doesn’t seem to work.

I then tried to specify a single file and still nothing. I tried relative at first then even tried absolute path (I know it’s not recommended, just trying to get this to work) and still nothing.

Do you have any suggestions?

There are 2 design patterns most commonly used with mu-plugins:

1. Single PHP file in the mu-plugins directory that is the simple plugin
2. A proxy loader that loads the plugin from a sub-directory in mu-plugins (WordPress recommended way).

It seems that the first way is supported but I cannot prove this. The second way would be nice to have supported as this is the recommended way by WordPress.

This is the way I was able to add mu-plugins support to Polylang for the wpml-config.xml (awaiting review to have it put into Polylang):

        // Mu-Plugins
        // Search for top level wpml-config.xml, not ideal or best practice but these exist.
        if (file_exists($file = WPMU_PLUGIN_DIR . '/wpml-config.xml')) {
            $files[basename(WPMU_PLUGIN_DIR)] = WPMU_PLUGIN_DIR . '/wpml-config.xml';
        }
        // Search for proxy loaded mu-plugins
        foreach (new DirectoryIterator(WPMU_PLUGIN_DIR) as $file_info) {
            if ($file_info->isDot()) continue;
            // Check if a directory (proxy loader method)
            if ($file_info->isDir()) {
                if (file_exists($file = $file_info->getPathname() . '/wpml-config.xml')) {
                    $files[$file_info->getFilename()] = $file;
                }
            }
        }

Perhaps this is worth checking out for this plugin too?

I really like the work done on this plugin and I would like to have my mu-plugins integrated into it properly. I hope this is possible to get done.

Thanks

• This reply was modified 2 years, 7 months ago by SoN9ne.
• This reply was modified 2 years, 7 months ago by SoN9ne.
• This reply was modified 2 years, 7 months ago by SoN9ne.

I understand the autoloading design pattern.

I have no problem configuring directories inside mu-plugins for including in source string extraction. I did this via the backend interface. If you set the correct information (including the text domain) it will work.

Not sure how this isn’t correct, am I missing something?

<?xml version="1.0" encoding="utf-8"?>
<bundle name="Oly OTT Core">
    <domain name="oly-ott-core">
        <project name="Oly OTT Core" slug="oly-ott-core">
            <source>
                <directory>oly-ott-core/views</directory>
                <file>oly-ott-core/views/olyrecommends-sync.php</file>
            </source>
            <target>
                <directory>oly-ott-core/languages</directory>
            </target>
            <template>
                <file>oly-ott-core/languages/oly-ott-core.pot</file>
            </template>
        </project>
    </domain>
</bundle>

I can’t know if your config is correct without the files you’re configuring. If you post them I’ll look.

Thank you.

oly-ott-core folder structure in the mu-plugins:

oly-ott-core
├── assets
├── index.php
├── js
├── languages
│?? ├── oly-ott-core-en_US.mo
│?? ├── oly-ott-core-en_US.po
│?? ├── oly-ott-core-es_ES.mo
│?? ├── oly-ott-core-es_ES.po
│?? └── oly-ott-core.pot
├── lib
├── metabox-views
├── oly-ott-core.php
├── readme.md
├── templates
├── Third-Party
├── views
│?? ├── olyrecommends-sync.php
│?? ├── user-profile.php
│?? └── woocommerce-pricing-updater.php
└── wpml-config.xml

Plugin Header

/**
 * Plugin Name: Oly OTT Core
 * Description: Core resources for Oly OTT Platform
 * Version: 1.7.4
 * Text Domain: oly-ott-core
 */

This should be enough to see the text domain and the folder structure.

The olyrecommends-sync.php is using standard WP i18n:

_e('Translatable String', 'oly-ott-core')

• This reply was modified 2 years, 7 months ago by SoN9ne.

No issue for me here:

View post on imgur.com

This using your exact XML config and the file names and content you’ve posted.

Whatever you’re doing differently from me, it is not present in your description.

Thank you for your response.

Could you please check the Debug tab and see if you see the message:

No strings can be extracted from source code

I never checked past seeing that error.

I just tested now and I am actually able to get the translations to work. So perhaps this is working but that error is not accurate.

It would be nice to be able to use the loco.xml in the sub-folders but this works for my needs.

Thank you so much for your time. I truly appreciate it. Thank you

Yes, you’re right. The debug tab seems to have a problem. Off the top of my head I don’t know why. I’ll have to look into that and fix. But you’ve got extraction working. Good news.

Awesome, I will close this ticket then. Seems this was all a false-flag due to that error but it is working. Thanks again!