Support Forum
Support › MB Frontend Submission › front end submission dashboard with custom post typeResolved
Hi,
Follow the troubleshooting steps on this comment https://support.metabox.io/topic/front-end-submission-dashboard-with-custom-post-type/#post-22718, I've found that if I switch to the default theme of WordPress (Twenty TwentyOne), the frontend dashboard will show the post type correctly. Could you please confirm it?
Hi, I changed the theme to twentytwentyone - no change. I also deactivated plugin for plugin to see if one of them was causing problems - no change. Sad but true 🙁
Have you logged in and checked with the access data I sent you?
Hi,
Please see my screen record https://share.getcloudapp.com/yAuZpQEx.
It works with the Block editor as well. You can test again with two pages:
post
: https://geschenkkartendisplay.de/minis-bearbeiten/mini
: https://geschenkkartendisplay.de/minitest/Damn! ...You're right! I deactivated the Divi theme and it worked. Thanks for your support! 🙂
Which now leads to the next problem: I don't have the skills to explain to Divi that the Divi is causing a problem and certainly not the skills to make it clear to a developer like you that his plugin may be faulty.
What would your advice be? What should I do?
Hi,
You can just send this topic to Divi's support and the site information to let them see the conflict. I'm also going to create a feature request for the developer team to create an update to compatible with Divi.
For now, you can use another page builder such as Elementor or Beaver. There are two extensions to integrate Meta Box and that page builders: Meta Box – Beaver Themer Integrator, Meta Box – Elementor Integrator.
One suggestion:
For both of these issues, it is possible that you've done a copy and paste of the shortcode from a webpage into the WordPress visual editor. When this happens hidden html code, such span tags, can be carried along in the pasted content. This will result in some or all of your shortcode definition not being processed, even though visually it is correct.
To check for this, switch to Text mode in the editor and the html will be revealed. Alternately, delete what is there and re-type the full shortcode by hand.
Tested - that wasn`t the problem 🙁
Hello,
I have exactly the same issue.
Everything is well setup on website and the shortcode does not display the cutom post. Only the default post.
I use the shortcode like that:
[mb_frontend_dashboard edit_page="190" post_type="agent"]
with page id=190, the page where I have the form [mb_frontend_form id='fields-for-agent' ]
and post_type is "agent".
I have deactivated all my plugins (I have very few), my theme is very basic (hello theme). I use elementor and elementor pro. I tried to deactivate them and still get the same issue.
I don't know what to do.
Hi guys,
There is a difference between the double quote " "190"
and quotation mark ” ”190″
. Please type the double quote correctly.
[mb_frontend_form id="fields-for-agent" post_type="agent"]
and the attribute post_type
is used in the shortcode [ mb_frontend_form ]
Thank you. It works. Everything is now in double quote.
For your info, the shortcode given by the plugin uses simple quotes: [mb_frontend_form id='fields-for-agent' post_fields='title,content']
Here is a screenshot: https://prnt.sc/11apzkd
So it's very confusing.
Hi, I'm having the same problem. I am using the shortcode
[mb_frontend_dashboard edit_page='1819' post_type='speaker-profile']
to display a user dashboard of posts of the CPT speaker-profile but the output is of the standard WP posts.
I have tested by switching themes to Twenty Twenty-One as shown in the screenshot below and disabling plugins but nothing changes.
I have been through this forum discussion and applied everything suggested but still no luck.
Hi. Use double quotes instead of simple quotes and it should work.
Thanks Ulysse but that was one of the suggestions made during this discussion and I tried it already but it doesn't make any difference.
be aware there is a difference between ' '' and "
Ok, just tried that, using a straightforward Gutenberg block:
The result, sadly, is still the same: