Missing UI in MB backend for CPT y Fields

Support MB Custom Post Type Missing UI in MB backend for CPT y Fields

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #46204

    I've just instaled MB in a site, and used Migration from ACF. Done without errors.
    In a second site, with similar plugins, I've done the same steps, and it worked fine.
    I see no errors in Firefox Console.

    I can see the list of CPT and Field Groups migrated, but when I try to edit, I can't see anything coming from MB on Screen.

    Don't know how to paste a image here, but this is the complete text I see on screen (beside the WP admin menu and bar):

    Status: Published Edit Edit status
    Visibility: Public Edit Edit visibility
    Published on: Aug 22, 2024 at 01:10 Edit Edit date and time
    Post Type: Post Type Edit
    Move to Trash
    Setup Schema

    Custom Schema

    #46205

    Same problem if I create a new CPT or field group from scratch, instead of opening the migrated ones.

    #46219
    PeterPeter
    Moderator

    Hello Oscar,

    You can upload the screenshots or a screen record to Google Drive and paste the URL here. Also, let me know if there is an error in the Console tab of the browser or in the debug log.
    https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/

    #46226

    Sorry, I can't upload screenshots, as I somehow "solved" the problem:
    - As for the screenshot, there was nothing to see: only the admin menu on the left and on top. Some text comming from a Schema Plugin, and nothing else. All the UI for custom fields and post types was missing.
    - First I disable thar Schema Plugin, being the only one in the crime scene made it suspectious :), but it didn't work.
    - Then I disables ACF, and it make the UI appear.

    One thing that could have caused this: before purchasing MB, I tried the free version of it, and of ACF migrate. As CPT where not show, I decided to purchase MB, and instaled it, but after migrating ACF.

    Re-runing ACF migration didn't help to solve the problem.

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.