Support Forum » User Profile

Forum Replies Created

Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • in reply to: Migrating from JetEngine to MetaBox #28565
    Patrick NelsonPatrick Nelson
    Participant

    Hey Jack,

    Haven't tried it yet. We have decided to use ACF for this project instead of MetaBox because ACF is better supported for some of the other plugins and functionality we need. I will be trying this method though to move from JetEngine to ACF. If it turns out to be relevant, I'll post my results here.

    Patrick NelsonPatrick Nelson
    Participant

    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.

    Patrick NelsonPatrick Nelson
    Participant

    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.

    Patrick NelsonPatrick Nelson
    Participant

    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.

    Patrick NelsonPatrick Nelson
    Participant

    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.

    Patrick NelsonPatrick Nelson
    Participant

    Page ID 1819 works fine - it always has. What doesn't work - and still doesn't work - is Page ID 1863 from above that should show a User Posts Dashboard for a CPT called speaker-profile. No matter what I change the attribute 'post_type' to, the dashboard only ever shows the default 'post'.

    Long, I provided the information you asked for and your response:

    ("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.")

    suggests that you are not even reading what I am writing. Once again, I have added the setting 'post_type' and I have set the slug to speaker-profile. All of this is clear from my most recent comment. It doesn't work! Can you not see what I have written in my previous comment?

    Patrick NelsonPatrick Nelson
    Participant

    Sure.

    This is 1819 which has the submit form - https://prnt.sc/12h3hm5
    Content is shortcode [mb_frontend_form id="speaker-profile"]

    This is 1863 which has the dashboard - https://prnt.sc/12h3k1g
    Content is shortcode [mb_frontend_dashboard edit_page="1819" post_type="speaker-profile"]

    I'm happy to supply login details if I can do so securely.

    in reply to: Migrating from JetEngine to MetaBox #27887
    Patrick NelsonPatrick Nelson
    Participant

    Thanks Long! That's a great help. I will read the article and give it a try.

    Patrick NelsonPatrick Nelson
    Participant

    Hi Long,

    This is exactly what I did (please read my previous posts in this thread) and it doesn't work.

    I have tried single quotes, double quotes, disabled all other plugins and changed theme to Twenty Twenty One. It simply doesn't work. Even if I change the post_type to page, it still shows the default post type.

    Patrick NelsonPatrick Nelson
    Participant

    Ok, just tried that, using a straightforward Gutenberg block:

    https://prnt.sc/12fjg7o

    The result, sadly, is still the same:

    https://prnt.sc/12fjhnq

    Patrick NelsonPatrick Nelson
    Participant

    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.

    Patrick NelsonPatrick Nelson
    Participant

    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.

    https://prnt.sc/12ffd8q

    I have tested by switching themes to Twenty Twenty-One as shown in the screenshot below and disabling plugins but nothing changes.

    https://prnt.sc/12ffdyk

    I have been through this forum discussion and applied everything suggested but still no luck.

Viewing 12 posts - 1 through 12 (of 12 total)