Meta Box

Do you use the wysiwyg field or textarea field? We'll take a note on this and will let our devs check this.

Hi,

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:

https://docs.metabox.io/creating-new-field-types/

Hi,

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_type and register_taxonomy functions. 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.

Hi 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.

We've just released a new version with a fix for this. Please update.

Hi,

You must put the credit on your project page. If you have a product page on your website, you need to put it there. Or if you sell on Envato, you should put on the item's page.

You don't have to put on the front end of all your users's website (as you're using MB Frontend Submission extension).

If you sell the product to a 3rd party, if they only use for themselves, then it's ok. But if they release a product that is sold to users, they'll have to follow this rule as well.

Hi Arno,

I'm trying to replicate the bug on my localhost but I don't see the error. I recorded a screencast, please take a look:

https://mega.nz/file/rvgFFAbL#DRCDlXxp4MIdjAx37dpL6T0v2W_DPXavAv42GeSGTns