Meta Box

Hello,

The compatibility with WPML supports translating the post type labels to other languages and it works properly. But I'm not sure if the breadcrumb in the frontend uses the post type label in a correct way and makes it translatable. Since it is not created by Meta Box so I'm not able to check it.
If you want to check the issue further, please share your site admin account by submitting this contact form https://metabox.io/contact/

Thank you.

Hello Sinisa,

Thanks for reaching out.

I suggest you follow the documentation https://docs.metabox.io/integrations/wpml/#custom-post-types
to translate posts and post type name using WPML. For the translation in the frontend, you can contact WPML support and ask them for more information.

Hello Nicole,

Thanks for reaching out.

The integration with Divi5 is on our development queue and we are working on it. I will let you know when there is an update for this integration.

That should be the issue. To access the admin area and fix this, please edit the table wp_posts in the database, find the post type mb-relationship and delete the new relationship created.

If you create a new relationship, please select the taxonomy for the Term connection.

Hello,

While waiting for the update of MB CPT, you can edit the file /mb-custom-post-type/src/PostTypeReorder.php, on line 266, clear the object cache after updating the post parent.

$wpdb->update(
    $wpdb->posts,
    [
        'post_parent' => $item['parent_id'] ? $item['parent_id'] : 0,
        'menu_order'  => $item['order'],
    ],
    [ 'ID' => $item['id'] ]
);
wp_cache_flush_group( 'posts' );

Let me know how it goes.

Hello,

I'm also not able to reproduce the issue on my side. If you have more information about this issue or steps to reproduce it, please let me know.

Thanks.

Hello Jon,

Currently, we don't support customization code like the custom field type. However, can you please let me know the issue that you have (screenshots or a screen record)? I will check it and see if there's something we can improve on our side.

Hello Lukas,

Our development team confirms that we don't have any restriction rules for the link https://packages.metabox.io/
I also notice that this URL isn't correct https://packages.metabox.io/<KEY>/packages.json as you can see in my demo code above. The correct URL is https://packages.metabox.io/<KEY>/ without packages.json.

Can you please share your composer file and a screen record of how you setup the Github action?