Meta Box

Hi Jayron,

Thanks a lot for your contribution. We've updated the translations for the plugins that you sent.

Regarding the translation format, since WordPress 6.5, it supports a new and more performant format for translation file .l10n.php instead of the old-fashioned .mo file. We use this format in our plugins to have a better performance. We also converted all of your translations to this new format, so you don't have to do that and send us again.

Regarding translations for strings in JavaScript (which is used in UI), we have updated our .pot file. When you create a translation for it, please follow this step:

- Create a .po file from .pot
- Run the following command to create JSON file:

cd /path/to/plugin/folder
wp i18n make-json languages --no-purge

Unfortunately, I know the only way to do that is via wp-cli. I'm not sure if plugins like Loco Translate or WPML support creating JSON file for translating strings in JS.

Hi Nick,

We only enqueue dashboard.js on the Dashboard page, as you can see the source code here. We run the enqueue styles and scripts on load-$page_hook, which fires only on that admin page.

Is there any special set up on your site? Can you please try with a fresh install?

Hi, we have a fix for this bug here. Can you please try it and let us know if that fixes?

Hi,

"localhost" is always treated as dev domain (note, we verify by domain, not port, so "localhost" will work for all hosts like "localhost:8080", etc.). You can see the source code here.

We also added ".localhost" suffix so all domains *.localhost will be treated as dev domains.

The problem is that Meta Box AIO loads Meta Box at init hook (with priority -5). If you put the snippet to define rwmb_meta function in your theme's functions.php, then it will load **before**, which defines an empty rwmb_meta function.

This method was usually used for themes that are sold like on ThemeForest, to prevent errors of undefined function rwmb_meta when they haven't installed Meta Box yet.

In your case, I'd recommend removing that snippet, and it will work fine.

Hi Bomes,

The hook for group title will be added in the next version of Group. Once it's done, you can use the filter like this:

jQuery( function() {
    // Change "myVendor/myPlugin" to your unique namespace
    rwmb.hooks.addFilter( 'group.title', 'myVendor/myPlugin', function( title ) {
        // Change the title and return the value here.
        return title + ' Some random string';
    } );
} );

This is done and will available in the next version.

Hi Jackky,

After checking this issue, I found that it's probably the browser issue. The pattern regex is outputted correctly in the input, but the browser displays it as rendered entities.

When you view the source code of the page, you'll see the pattern attribute is outputted correctly. But when you *inspect* the input with the browser inspector, it will shows rendered entities. So, it seems to be an issue with viewing in the browser instead of a technical issue, which probably can't be fixed.

I created a demo with pure HTML for you to check here.