\DevOwl\RealProductManagerWpClientLocalization

getRootSlug()

getRootSlug(): string

Getter.

Returns

getPackage()

getPackage(): string

Get package name.

Returns

getPackageDir()

getPackageDir(): string

Getter.

Returns

instance()

instance(string  $rootSlug,string  $packageDir): \MatthiasWeb\Utils\PackageLocalization

New instance.

Parameters

Returns

clearMoCacheDir()

clearMoCacheDir(string  $slug)

Clear the MO cache directory for a given plugin.

Parameters

getLanguageFromFile()

getLanguageFromFile(string  $file)

Obtain language key from a file name.

Parameters

override_load_textdomain()

override_load_textdomain(boolean  $plugin_override,string  $domain,string  $mofile)

Never load `.mo` files from `wp-content/plugins/languages` as we do manage all our translations ourself.

TODO: make this configurable per plugin?

This filter is directly implemented in override_load_textdomain but keep for history.

Parameters

hooks()

hooks()

Add filters to WordPress runtime.

getPotLanguages()

getPotLanguages()

Get the languages which are available in the POT file. Why multiple? Imagine you want to use the pot file for `en_US` and `en_GB`. This can be useful for the `@devowl-wp/multilingual` package, especially the `TemporaryTextDomain` feature.

getMoCacheDir()

getMoCacheDir(string  $slug)

Get the cache directory for cached MO files after parsing. It also checks, if the directory is writable and create the path for a given plugin slug.

This function is expensive, so we cached it to $GLOBALS.

Parameters

instanceThis()

instanceThis()

Create instance.

__construct()

__construct()

C'tor.

getPackageInfo()

getPackageInfo(string  $type): array<mixed,string>

Get the directory where the languages folder exists.

The returned string array should look like this: [0] = Full path to the "languages" folder [1] = Used textdomain [2]? = Use different prefix domain in filename

Parameters

Returns