front end submission dashboard with custom post type

Hi Patrick,

The post type attribute should be added in the shortcode frontend submit to make the dashboard works.

[mb_frontend_form post_fields="title,content" post_type="speaker-profile"]

Get more details here https://docs.metabox.io/extensions/mb-frontend-submission/#creating-post-forms

Hi Patrick,

Can you please share the screenshots of two pages?

• The page ID 1819 has the shortcode frontend submit [mb_frontend_form post_fields="title,content" post_type="speaker-profile"]
• The page has the shortcode frontend dashboard [mb_frontend_dashboard edit_page="1819"]

Hi Patrick,

Frontend Submit shortcode attributes:
id: is the meta box ID, if you do not assign a meta box ID to this post type, please remove it.
post_type: is the slug of your post type speaker-profile or you can change to page. You have to add this setting if you want to make the shortcode Frontend Dashboard edit this post type.

[mb_frontend_form post_fields="title,content" post_type="speaker-profile"]

Please read more on the documentation https://docs.metabox.io/extensions/mb-frontend-submission/

Look, I have just applied a number of other attributes to the shortcode as you can see here: https://prnt.sc/12ijlnh

And, as you can see here, those attributes all work: https://prnt.sc/12ijmcd

The dashboard has changed - only the title column, renamed to "Speaker", the welcome message has gone and the add new button now reads 'Add new speaker'.

All of these attributes work. Every one EXCEPT the post_type attribute which I have entered correctly as you can see from this screenshot of the MetaBox Edit Post Type screen: https://prnt.sc/12ijrnm

I don't know what else I can do to demonstrate that the attribute 'post_type' does not work correctly.

I subscribe to the Developer Bundle of MetaBox and I am considering cancelling this. Not because of the technical problem but because of the support problem.

How are you "seeing" that in my reply?

My screenshot at https://prnt.sc/12ijlnh clearly shows the shortcode is mb_frontend_dashboard not mb_frontend_form.

The screenshot also shows that the value speaker-profile is assigned to the attribute post-type not the attribute id.

OK, thank you Long. That now works and I now understand.

However, I notice that these forms do not respect editing or posting capabilities. I have a user who should not be able to add, publish or delete this CPT but the Add New button and the delete Action are freely available which means the user can carry out actions that they should be denied.

I appreciate the help getting this working but this does render the functionality useless for us.

That's not the issue, Long.

We're using PublishPress permissions to set custom capabilities for CPTs for custom user roles. So we have a role called Speaker who can edit a Speaker post that is assigned to them (they are the author) but they don't have permission to create a new Speaker post or to delete any post.

These permissions are recognised and obeyed by WordPress. So in the backend admin screen, for example, they don't see the Add New option for Speaker posts and they don't have an option to delete their assigned post.

However, your frontend dashboard has an 'Add new' button and a 'delete' action. Both of these allow the user to bypass these permissions and create new posts or delete their assigned posts.