Support Forum » User Profile

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 36 total)
  • Author
    Posts
  • in reply to: Fatal error: ($object_id) must be of type int, null given #46758
    Alaan TVAlaan TV
    Participant

    test

    in reply to: Load tab content on demand #46757
    Alaan TVAlaan TV
    Participant

    Hello team,

    It’s been over 10 months since this ticket was opened, and I wanted to follow up to request the addition of a feature that allows saving only the current tab fields when the Save button is clicked.

    This feature has become essential, especially when a team of editors (e.g., in a newsroom) is working on the same settings page, where each editor is responsible for fields in a specific tab. Currently, when one editor clicks Save, changes made by another editor in a different tab are overwritten.

    Once the feature for opening each tab individually is implemented, the process would be as follows:

    • The default tab page will open when the settings page link is visited.
    • Only the fields for the current tab will be loaded.
    • Only the fields for the current tab will be saved when the Save button is clicked.

    This could later be enhanced to lock the tab being edited by another user, similar to the post editing feature:

    • The tab label will be grayed out or display the avatar of the editor working on it.
    • A popup will allow users to take over the tab, just like how it works with posts.

    I understand you have your priorities and roadmap, but I wanted to share these thoughts and suggestions for future releases. I would greatly appreciate it if you could consider these improvements or some of them in your next updates.

    Best Regards,

    Alaan TVAlaan TV
    Participant

    This is fixed after updating Meta Box AIO plugin to 1.25.0. Thank you!

    in reply to: Required fields are not working with taxonomies #42651
    Alaan TVAlaan TV
    Participant

    Any updates, please!

    in reply to: Empty Fields after UPDATE #41912
    Alaan TVAlaan TV
    Participant

    This is resolved after updating to version 5.7.1. Thank you!

    in reply to: Empty Fields after UPDATE #41898
    Alaan TVAlaan TV
    Participant

    I encountered the same issue; the recent plugin update 5.7.0 has some issues.
    I have reverted the version until this is fixed.

    in reply to: Required fields are not working with taxonomies #41782
    Alaan TVAlaan TV
    Participant

    A gentle reminder!

    in reply to: Required fields are not working with taxonomies #40690
    Alaan TVAlaan TV
    Participant

    A gentle reminder, any expected date to release the fix, please?

    in reply to: Required fields are not working with taxonomies #40325
    Alaan TVAlaan TV
    Participant

    Any expected date to release this fix?

    2 releases were rolled out after this ticket was opened, and none included a fix for this issue.

    in reply to: Required fields are not working with taxonomies #40030
    Alaan TVAlaan TV
    Participant

    Thank you, Peter! But it seems you misunderstood me.

    This happens when I create a new term, not when I add a term to the post. The custom taxonomy has a required field, so I'm expecting to get a warning before creating the new term that stops the creation procedure. But what happens is the term is being created even when the required field is blank.

    Here's how to reproduce the issue:

    Try to create a new custom taxonomy MY_TAXONOMY, then create some fields for it and make one of them required. Then visit this page:

    example.com/wp-admin/edit-tags.php?taxonomy=MY_TAXONOMY

    Now try to add a new term without filling in the required field; the term will be added directly without warnings or stopping the creation procedure.

    in reply to: Show or Hide Fields Based On Role #39913
    Alaan TVAlaan TV
    Participant

    I found a solution that may help; you can set the type of the field based on the role, like this:

    [
        'name' => 'My field',
        'id'   => 'my_field',
        'type' => current_user_can( 'administrator' ) ? 'text' : 'hidden', // Show only for admins.
    ],
    

    Here, the type of the field will be hidden for none admin users and text for administrators.

    Alaan TVAlaan TV
    Participant

    Thank you! Please do it ASAP 🙏🏻. It breaks some features here!

    in reply to: Terms meta are not being deleted after deleting the term #39523
    Alaan TVAlaan TV
    Participant

    And this issue was resolved after updating the plugin, thank you so much!

    in reply to: Disabled radio buttons are editable #39522
    Alaan TVAlaan TV
    Participant

    You can run this code once the admin page is loaded to make the readonly radio buttons uneditable:

    document.querySelectorAll('input[type=radio][readonly]')
            .forEach(item => item.addEventListener('click', e => e.preventDefault()));
    
    Alaan TVAlaan TV
    Participant

    You have deleted these lines from the file wp-content/plugins/meta-box/inc/fields/file.php, after putting them back the error disappeared:

    /**
     * Add data encoding type for file uploading
     */
    public static function post_edit_form_tag() {
        echo ' enctype="multipart/form-data"';
    }
    

    Could you please fix this ASAP!? 🙏🏻

Viewing 15 posts - 1 through 15 (of 36 total)