Hi! I have another custom posts plugin, and I have created many custom posts there. The plugin stopped work on my site so I decided to change it to this MB Custom Post Types & Custom Taxonomies. Do I need to create all the posts again or is there any way to export / import these old ones to this plugin ? Thanks in advance.
]]>Hello there,
Please, i need help ?? . Can you tell how i can make all CPTs private for all users, except for its author and the Admin ? Of course the author must be log in to be able to read his own post.
Regards,
]]>Hi,
I’ve been encountering an error that breaks some of the custom post types created by the Total theme on my site:
2024/08/20 15:38:22 [error] 1821340#1821340: *1033378 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /var/www/staging.flemingmartin.com/htdocs/wp-content/plugins/mb-custom-post-type/src/PostTypeRegister.php:183
2024/08/20 15:47:16 [error] 1821339#1821339: *1034838 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /var/www/staging.flemingmartin.com/htdocs/wp-content/plugins/mb-custom-post-type/src/TaxonomyRegister.php:189
I have disabled all other plugins and custom code on the website, except Meta Box plugins and the Total theme core plugin. So the issue is definitely a conflict between them. I was able to fix these two files by editing the if statements as follows:
PostTypeRegister.php, line 178: if ( defined( 'MBB_VER' ) && is_array( $settings ) && isset( $settings['slug'] ) )
TaxonomyRegister.php, line 183: if ( defined( 'MBB_VER' ) && is_array( $settings ) && isset( $settings['slug'] ) )
Would it be possible to have this fixed in the next release, please? Thank you!
]]>Hi,
I’m testing this plugin. So far so good, but I’m running into a little issue.
I created a custom post type (CPT) and a custom taxonomy (CT). On the page I set up to display the CPT content, I’m using a tag cloud for the tax taxonomy, as I want an easy way to filter the content with the custom taxonomy.
The CT is correctly assigned to the CPT. The reverse is also true. The CPT ‘has archives’ enabled (advanced settings).
The tag cloud is also showing the right tags.
The problem is that whenever I click on each of the tags I’m shown my blog page (without the content). What I was expecting was for the right CPTs (with the assigned tag) to show!
I’ve gone to Settings ? Permalink to re-save the settings multiple times, cleared cache… What am I missing?
Thanks!
Eva
]]>[23-Nov-2023 11:13:52 UTC] PHP Warning: Trying to access array offset on value of type null in l/wp-content/plugins/mb-custom-post-type/src/TaxonomyRegister.php on line 117
[23-Nov-2023 11:13:52 UTC] PHP Warning: Undefined array key “slug” in /wp-content/plugins/mb-custom-post-type/src/PostTypeRegister.php on line 88
Please fix it
]]>Hi! The latest update of plugin have alot of issues and dont work with woocommerce, Please check it out. As soon as i roll back to old version everything works
]]>after update to 2.6.2
all my Woocomerce orders is disappear
i must rollback to v2.6.1
please fix
]]>Hi guys,
The latest update to the plugin makes all custom created post types disappear from the Customiser and in some cases it breaks the archive layout.
This is reproducible on all themes that support individually customising post types, for example Blocksy.
Fyi. ??
]]>Warning: Undefined array key “slug” in /home3/host1839650/gkvent.ru/htdocs/www/wp-content/plugins/mb-custom-post-type/src/PostTypeRegister.php on line 88
Warning: Undefined array key “slug” in /home3/host1839650/gkvent.ru/htdocs/www/wp-content/plugins/mb-custom-post-type/src/PostTypeRegister.php on line 88
Warning: Undefined array key “slug” in /home3/host1839650/gkvent.ru/htdocs/www/wp-content/plugins/mb-custom-post-type/src/PostTypeRegister.php on line 88
All types of records created through your plugin flew off and we get errors
The error was corrected, but it is not clear why this happened. And now how to recover lost records?!
]]>After installing and trying to add a new taxonomy there’s an error:
Fatal error: Uncaught Error: Class 'MetaBox\Updater\Option' not found in /var/www/u0835731/data/www/siteadress.top/wp-content/plugins/mb-custom-post-type/src/Edit.php:116 Stack trace: #0 /var/www/u0835731/data/www/siteadress.top/wp-content/plugins/mb-custom-post-type/src/Edit.php(24): MBCPT\Edit->is_premium_user() #1 /var/www/u0835731/data/www/siteadress.top/wp-includes/class-wp-hook.php(310): MBCPT\Edit->register_upgrade_meta_box('mb-taxonomy') #2 /var/www/u0835731/data/www/siteadress.top/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array) #3 /var/www/u0835731/data/www/siteadress.top/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #4 /var/www/u0835731/data/www/siteadress.top/wp-admin/includes/meta-boxes.php(1701): do_action('add_meta_boxes', 'mb-taxonomy', Object(WP_Post)) #5 /var/www/u0835731/data/www/siteadress.top/wp-admin/edit-form-advanced.php(271): register_and_do_post_meta_boxes(Object(WP_Post)) #6 /var/www/u0835731/data/www/siteadress.top/wp-admin/post-new.php(75): require('/var/www/u08357...') #7 {main} thr in /var/www/u0835731/data/www/siteadress.top/wp-content/plugins/mb-custom-post-type/src/Edit.php on line 116
Hi
I’d like to create a page model for a cpt i created with MB in Divi’s theme builder, but it doesn’t appear in the assignment :
Can you please tell me how to enable MB cpt support in Theme builder ?
Thank you !
]]>I’ve had who sites crash with critical errors when updating to 2.5.3. I rolled back to 2.5.2 and everything is working ok.
]]>Hi,
Loving this plugin so far. Noticed just a handful of minor issues when creating a new CPT. Some of the titles aren’t capitalized. I can go through and capitalize these myself, however, would save a minute or two to have these done each time a new CPT is created.
Thank you so much! Really liking the clean, easy to understand UI!
Hi
Is there a performance benefit to exporting the PHP code and using it in a custom plugin vs not doing so? Presumably, at least one database query is removed?
Can/should the plugin be deactivated if the generated code is used?
Thanks
Jamie
An error of type E_ERROR was caused in line 29 of the file /var/www/vhosts/{site}/httpdocs/wp-content/plugins/mb-custom-post-type/mb-custom-post-type.php. Error message: Uncaught Error: Class ‘MBCPT\PostTypeRegister’ not found in /var/www/vhosts/{site}/httpdocs/wp-content/plugins/mb-custom-post-type/mb-custom-post-type.php:29
This happened with an auto update to version 2.3.0
The website is showing a “critical error” message
]]>Hi,
When updating MB Custom Post Types & Custom Taxonomies form version 2.2.5 to 2.2.6, all my dashicons are replaced with the default icon. The order of the dashboard is messed up as well:
Before update: https://rzfg.co/zGONl4
After update: https://rzfg.co/JSXxe4
Is there a way to easily fix this. I have tested on multiple sites and have found the same issue on all of them.
I’ve been waiting for an update, but since it’s been a month since the update was released, I figured it was time to ask about it. Hopefully it’s an easy fix.
Thanks ??
]]>Hi,
I’ve been playing with this for hours and I cannot seem to figure out what I’m doing wrong. I have a custom post type “Events” and a custom taxonomy “Event Categories”. When I create a new post, it generates mydomain.com/event/event-name. It doesn’t add the event category so that it’d be mydomain.com/event/category/event-name.
Is there something special I need to do to get this to kick in?
Thanks,
AJ
Hello,
I have created custom post “case studies” without an archive page. I then created a page with this same urls to display the custom posts, see the link below.
https://www.youandus.events/case-studies/
The issue I’m having is that google seem to be struggling to index the case studies posts, even showing one as 404 error.
When I run a visualisation tool to see site structure these posts don’t appear in there either as if they didn’t exist.
Is this something you can advise on?
Thanks
Celina
Hello,
I have created a post type with a slug case-studies. I have selected for it to not have archive page.
My question is, would it be now possible to have a page with a slug case-studies, where i would display the posts of that type or could this create issues for the custom posts with that slug?
Am I better off just having a different slug for the page I want to display these posts on?
Thanks
Celina
Hello,
I have created a custom post type, then went to create first post. I was able to preview the page when it was a draft but once I pubslished it, it shows 404 error.
I didn’t select for this post type to have an archive. Could that be the reason?
I also didn’t select Query var and Prepended permalink structure as didn’t know what they do. Could this be a reason?
Are you able to advise what could be the problem.
Thanks
Celina
Custom Post Type UI
How can I migrate from this plugin?
]]>How to display post in hompeage
]]>Hi,
I need to display custom post type in frontend like home page, I did not find any information about that in this plugin documentation and plugin page. Please let me know how to do this or please point the page which has that information (how to display custom post type in frontend). I hope I will get a reply soon. I am waiting for your reply
Please be a little more clear you need Metabox to use this. I didn’t know about Metabox and was looking for something simpler for the UI of my CPTs and CCTs. So this wasn’t a good fit at all, I think.
Wasting my time puts me off plug-ins. We don’t always want complicated solutions that can do anything, but simple and focused solutions that do few things well.
]]>I am not seeing functionality to add the CPT as a sub-menu in the admin menu.
Did I miss it?
]]>I created a custom post type. Then I created a custom taxonomy using the taxonomy plugin you provide as well. But when I edit the post type, where it says “Default Taxonomies”, there are none listed to choose from, namely the one I created so I’m not sure what is going on.
]]>Hi there at Meta Box,
I have a massive problem with the “mb-custom-post-type” extension after using the “custom taxonomy” feature: The name of my custom post has changed to {{labels.all_items}}, “Add new” has changed to {{labels.add_new}} in the siedebar menu, plus the extenion now creates a php-error “__clone method called on non-object” that prevents the application from loading any lists/overviews in the CSS (posts, pages, media). All Post, All pages, etc simlpy return a blank white page. Any idea of how to fix this?
thanks!
Hi,
I’m using this plugin to make plant/herb and recipe website.
There will be a lot of info, so I’ll need a good search functionality.
Can you recommend a custom post search plugin that works well with this one?
The ideal result would be a page where there is 3 sections of results, one per custom post type.
Is there a way to make automatic links to for example other recipes (Custom post types) withe the same ingredients (meta box)?
Regards,
Remco
Nice plug-in. I love how it sets up an admin area.
I’m converting a Drupal site to WordPress. Your plug-in has allowed me to set up on the WP site with some custom post types and preparing for taxonomies to come over.
When I import the Drupal database and run some MySQL scripts to convert the posts to WP terminology, my intent would be to convert the post-type names from one platform to the other… and maintain the existing taxonomies for each post type.
When I convert the post-types in the database, will your plug-in automatically “grab” the correct post-types and also populate the new taxonomies I’ve set up in WP via your plug-in?
Before I try a big database conversion via scripts, I’d like to get your input. Perhaps you can tell me something to avoid, or to do to make my situation work better. (And I know, I can always restore the database with a “before” copy if I fail or it gets messed up).
Thanks for your time.
]]>Hi,
is there a way to restrict access to the post types editor, so that only admins can edit them?
I have a few authors and don’t want them to mess up the post types. Actually I don’t even want them to see the menu entry, so hiding it entirely for any role below admin would be great.
]]>