Forum Replies Created
-
AuthorPosts
-
August 22, 2024 at 8:30 AM in reply to: ✅frontend form shortcode to exclude certain custom fields #46196
Anh Tran
KeymasterHi guys,
This feature was implemented in the plugin. Please follow the docs on using it.
Anh Tran
KeymasterHi AnLip,
After debugging, we found the bug and fixed it. This fix will be available in the next version.
FYI: technically, it's kind of an edge case with Bricks. Bricks register a top-level menu with position = 2, which is the same as Dashboard. In this case, WordPress will modify this value to a number like 2.12345, e.g. a float number. In Meta Box, we use integers for menu positions as WordPress recommends, but it won't work in this case for Bricks. So, in the update, we allow to use float numbers for menu position, and filter the menu to force WordPress to accept them (cause by default WordPress doesn't accept menu position = float for custom post types).
Anh Tran
KeymasterHi Scott,
Please overwrite the template of the email confirmation template with templates in your theme, similarly to how overwrite WooCommerce templates. For details, please follow the docs:
https://docs.metabox.io/extensions/mb-user-profile/#email-templates
Anh Tran
KeymasterHi Andrew,
Can you please share the setup of the relationship (code or screenshot)?
Anh Tran
KeymasterDo you use the
wysiwygfield ortextareafield? We'll take a note on this and will let our devs check this.Anh Tran
KeymasterIt's okay to post your question here 🙂
June 8, 2024 at 9:23 AM in reply to: ✅Enhancement Request: Group fields in metaboxes using CSS GRID & FLEXBOX #45624Anh Tran
KeymasterHi,
Thanks for your suggestion. After a careful thought about this, we found that changing the markup + css for the fields is risky and might break thousands of websites. Note that currently Meta Box is using flexbox already (and when we changed to flexbox - which is a minor change - it also affected a lot of websites and we got some complaints about this).
Regarding your request about grid + groups + columns to build complex layout/styling, it's very hard to "just implement" the grid without knowing the requirements. It's not just about columns, but also about nested columns/grids/groups, which can be very complicated and hard to debug when something is wrong.
In this case, we'd like to suggest you to use these filters to change the markup for fields:
https://docs.metabox.io/filters/rwmb-wrapper-html/
https://docs.metabox.io/filters/rwmb-begin-html/
https://docs.metabox.io/filters/rwmb-end-html/Or better, write a custom field type that gives you the flexibility of defining your own markup:
Anh Tran
KeymasterCan you please share us how do you structure your plugin, and also the content of your
composer.json(without the license key)?November 29, 2023 at 5:48 PM in reply to: Rewrite permalink of CPT taxonomy to equal of archive page #43960Anh Tran
KeymasterHi,
It's confusing URL structure. If a user access
domain.com/information/security, is that a post or is that a category? We always don't recommend people doing that. Even if it works in some cases, it will be bad for performance, cause WP need to process through all posts and also terms.FYI: We don't process or generate the rewrite rules. We simply pass all the parameters to WordPress's
register_post_typeandregister_taxonomyfunctions. I don't think it works if you use code directly. It's mostly how to deal with the way WP handle rewrite rules than the plugin. I'll check more closely.Anh Tran
KeymasterOh, I see. Looks like Toolset store JSON differently from us, and when import, we imported them all. Let me take a note on this to prevent same thing happening in the future.
> I see the entry for "wpcf-post-type" in the wp_options table as a serialized array.
It's from Toolset. We don't use
wp_optionsto store post type configs.> is it safer/easier to just delete the post type using the MB Builder and re-create it without loosing any data.
Yes, it's the safer and better way to deal with conflicts.
Anh Tran
KeymasterHi Bluemoon75,
I replied in the other thread, I think it's useful to repost it here as I think it's related to your issue.
---
Regarding your issue, I think the problem was in the 2.6.x version of MB Custom Post Types & Custom Taxonomies plugin. We released version 2.6.0 which had a new feature to allow you to edit post types registered in WP core (like post and page) and post types registered by other plugins. The way it works is replicating those post types in the plugin's post type list, so you can edit them as usual.
I *guess* in your case, when you upgraded the plugin, it replicated some post types registered by other plugin. Those post types had some rewrite options that were available in MB Custom Post Types & Custom Taxonomies and caused the bug.
We reverted this feature in 2.6.2, but the replicated post types are still in the DB.
One way to resolve this is go to Post Types and remove all post types that were not created by you manually. The other way is what you did by updating the settings for them.
I hope this clarifies things and what happended behind the scene.
November 25, 2023 at 3:39 PM in reply to: ✅PHP 8 Error after activating "MB Custom Post Types & Custom Taxonomies" #43918Anh Tran
KeymasterHi AJ,
> Also, just curious, but it seems that I don't need "MB Custom Post Types & Custom Taxonomies" or "MB Relationships" as separate plugins if I have Meta Box and Meta Box AIO activated. Is that correct?
Yes, that's right. AIO already includes those plugins.
Regarding your issue, I think the problem was in the 2.6.x version of MB Custom Post Types & Custom Taxonomies plugin. We released version 2.6.0 which had a new feature to allow you to edit post types registered in WP core (like post and page) and post types registered by other plugins. The way it works is replicating those post types in the plugin's post type list, so you can edit them as usual.
I *guess* in your case, when you upgraded the plugin, it replicated some post types registered by other plugin. Those post types had some rewrite options that were available in MB Custom Post Types & Custom Taxonomies and caused the bug.
We reverted this feature in 2.6.2, but the replicated post types are still in the DB.
One way to resolve this is go to Post Types and remove all post types that were not created by you manually. The other way is what you did by updating the settings for them.
I hope this clarifies things and what happended behind the scene.
Anh Tran
KeymasterWe've just released a new version with a fix for this. Please update.
Anh Tran
KeymasterWe've just released a new version with a fix for this. Please update.
-
AuthorPosts