Meta Box

Support Forum » User Profile

Forum Replies Created

Viewing 15 posts - 16 through 30 (of 40 total)
1 2 3
  • Author
    Posts
  • January 25, 2022 at 7:23 PM in reply to: ✅Can't save location for custom field groups, always reverts to POSTS #33446
    pzapza
    Participant

    It seems like I have this issue on 1 site. Any update/resolution? I also have a complex field group, which I'd rather not recreate.

    I can confirm, when saving in MB builder, the postmeta "settings" for this field group is set to "a:0:{}"

    If I copy the "settings" value from another field group (see below) the UI displays correct. But upon saving, gets reset/cleared.

    a:11:{s:11:"object_type";s:4:"post";s:10:"post_types";a:1:{i:0;s:7:"invoice";}s:7:"context";s:6:"normal";s:8:"priority";s:4:"high";s:5:"style";s:7:"default";s:9:"tab_style";s:0:"";s:18:"tab_default_active";s:0:"";s:5:"class";s:0:"";s:6:"prefix";s:0:"";s:11:"text_domain";s:16:"your-text-domain";s:13:"function_name";s:25:"your_prefix_function_name";}

    Fortunately the postmeta "fields" seems to be saved ok. Just not the settings.
    I can send the fields by email, if it helps?

    February 18, 2021 at 7:00 PM in reply to: ✅New version wiped my fields #24480
    pzapza
    Participant

    I'm having a similar issue, I don't know if it's the same as OP's.

    It is affecting a Field Group with nested + cloneable "groups" of fields. The custom fields don't load when editing the field group, ever since 1.13. I have tried the migration parameter and no luck. Other field groups load in the new interface (no nested groups)...

    So for now I'll keep using the previous version.

    December 11, 2020 at 5:40 PM in reply to: ✅Post type custom slug not updating #23517
    pzapza
    Participant

    Actually this seemed to work only for post types.

    But when editing my taxonomy, the slug still defaults to the Singular Name...

    To be clear the issue is the default field value for the slug when editing a Taxonomy in Meta Box > Taxonomies

    It's not actually changed in the database unless I accidentally save the default value, which is incorrect (I'm using custom taxonomy slug)

    December 11, 2020 at 5:36 PM in reply to: ✅Post type custom slug not updating #23516
    pzapza
    Participant

    Thank you, it worked. I've been quite busy and didn't catch this important upgrade notice.

    December 7, 2020 at 6:19 PM in reply to: ✅Post type custom slug not updating #23444
    pzapza
    Participant

    This is a new problem since the recent update with the new layout

    August 8, 2020 at 10:04 PM in reply to: ℹ️MB Relationships within Builder #21181
    pzapza
    Participant

    This would be a nice improvement

    June 30, 2020 at 11:28 PM in reply to: ✅Edit Field Group is sllow #20562
    pzapza
    Participant

    Hi if I understand correctly, I also have this issue.

    I believe OP means "more than 300 terms in a (any) custom taxonomy"

    And when editing (or creating a new field group) it loads very slow.

    Presumably because it's loading those terms for taxonomy-type fields, but this happens even when no taxonomy (or any) fields have been added to the field group.

    June 8, 2020 at 4:18 PM in reply to: ✅Meta Box builder not working after update #20272
    pzapza
    Participant

    Recent updates also broke my MB Builder. When I go edit a custom field group, no fields load and the {{variables}} are not updated.

    Console errors below.

    I have reverted to the last version I have which is 1.11.7 and works fine

    Thanks for looking into it.

    
Uncaught ReferenceError: hljs is not defined
    at builder.js?ver=3.2.7:697
angular.min.js?ver=1.6.9:42 Uncaught Error: [$injector:modulerr] http://errors.angularjs.org/1.6.9/$injector/modulerr?p0=Builder&p1=Error%3A%20%5B%24injector%3Anomod%5D%20http%3A%2F%2Ferrors.angularjs.org%2F1.6.9%2F%24injector%2Fnomod%3Fp0%3DBuilder%0A%20%20%20%20at%20https%3A%2F%2Fdomain.com%2Fwp-content%2Fplugins%2Fmeta-box-aio%2Fvendor%2Fmeta-box%2Fmeta-box-builder%2Fassets%2Fjs%2Fangular.min.js%3Fver%3D1.6.9%3A7%3A76%0A%20%20%20%20at%20https%3A%2F%2Fdomain.com%2Fwp-content%2Fplugins%2Fmeta-box-aio%2Fvendor%2Fmeta-box%2Fmeta-box-builder%2Fassets%2Fjs%2Fangular.min.js%3Fver%3D1.6.9%3A26%3A408%0A%20%20%20%20at%20b%20(https%3A%2F%2Fdomain.com%2Fwp-content%2Fplugins%2Fmeta-box-aio%2Fvendor%2Fmeta-box%2Fmeta-box-builder%2Fassets%2Fjs%2Fangular.min.js%3Fver%3D1.6.9%3A25%3A439)%0A%20%20%20%20at%20https%3A%2F%2Fdomain.com%2Fwp-content%2Fplugins%2Fmeta-box-aio%2Fvendor%2Fmeta-box%2Fmeta-box-builder%2Fassets%2Fjs%2Fangular.min.js%3Fver%3D1.6.9%3A26%3A182%0A%20%20%20%20at%20https%3A%2F%2Fdomain.com%2Fwp-content%2Fplugins%2Fmeta-box-aio%2Fvendor%2Fmeta-box%2Fmeta-box-builder%2Fassets%2Fjs%2Fangular.min.js%3Fver%3D1.6.9%3A42%3A332%0A%20%20%20%20at%20r%20(https%3A%2F%2Fdomain.com%2Fwp-content%2Fplugins%2Fmeta-box-aio%2Fvendor%2Fmeta-box%2Fmeta-box-builder%2Fassets%2Fjs%2Fangular.min.js%3Fver%3D1.6.9%3A8%3A7)%0A%20%20%20%20at%20g%20(https%3A%2F%2Fdomain.com%2Fwp-content%2Fplugins%2Fmeta-box-aio%2Fvendor%2Fmeta-box%2Fmeta-box-builder%2Fassets%2Fjs%2Fangular.min.js%3Fver%3D1.6.9%3A42%3A180)%0A%20%20%20%20at%20gb%20(https%3A%2F%2Fdomain.com%2Fwp-content%2Fplugins%2Fmeta-box-aio%2Fvendor%2Fmeta-box%2Fmeta-box-builder%2Fassets%2Fjs%2Fangular.min.js%3Fver%3D1.6.9%3A46%3A250)%0A%20%20%20%20at%20c%20(https%3A%2F%2Fdomain.com%2Fwp-content%2Fplugins%2Fmeta-box-aio%2Fvendor%2Fmeta-box%2Fmeta-box-builder%2Fassets%2Fjs%2Fangular.min.js%3Fver%3D1.6.9%3A22%3A19)%0A%20%20%20%20at%20Uc%20(https%3A%2F%2Fdomain.com%2Fwp-content%2Fplugins%2Fmeta-box-aio%2Fvendor%2Fmeta-box%2Fmeta-box-builder%2Fassets%2Fjs%2Fangular.min.js%3Fver%3D1.6.9%3A22%3A332)
    at angular.min.js?ver=1.6.9:7
    at angular.min.js?ver=1.6.9:43
    at r (angular.min.js?ver=1.6.9:8)
    at g (angular.min.js?ver=1.6.9:42)
    at gb (angular.min.js?ver=1.6.9:46)
    at c (angular.min.js?ver=1.6.9:22)
    at Uc (angular.min.js?ver=1.6.9:22)
    at we (angular.min.js?ver=1.6.9:21)
    at HTMLDocument.<anonymous> (angular.min.js?ver=1.6.9:336)
    at i (load-scripts.php?c=0&load[chunk_0]=jquery-core,jquery-migrate,utils,underscore&ver=5.4.1:2)
    January 26, 2020 at 10:33 PM in reply to: ✅User Profile and display_name #18017
    pzapza
    Participant

    By the way in case it helps anyone, here's what I ended up doing:

    • custom text field named display_name in user profile
    • for user profile, a field group with ID user-profile
    • the following code to update user info after saving the MB profile
    add_action( 'rwmb_profile_after_process', function( $config, $user_id ) {
    if ( $config['id'] == 'user-profile' ) {
        if ( $uname = $_POST['display_name'] ) {
            $args = array(
                'ID' => $user_id,
                'display_name' => $uname
            );
            $update = wp_update_user($args);
        }
    }
}, 10, 2 );
    • and this to update the default profile field value in case it was changed elsewhere (ie. Edit account page)
    add_filter( 'rwmb_display_name_field_meta', function( $meta, $field, $saved ) {
    $current_user = wp_get_current_user();
    return $current_user->display_name;
}, 10, 3 );
    December 28, 2019 at 6:07 PM in reply to: ✅User Profile and display_name #17655
    pzapza
    Participant

    I never could figure this out. User "display name" can not be updated via user profile?

    November 28, 2019 at 4:15 AM in reply to: Fatal error: Allowed memory size of # bytes exhausted #17203
    pzapza
    Participant

    So I'm still assuming this is related to this topic (sorry if not) but I found the conflict in my case.

    • First I tried disabling all plugins except MB & MB AIO. I also tried changing to 2020 theme. My problem persisted: "Edit field group" window completely freezes and uses up 100% of CPU. No errors in the logs.

    With WP Debug on, I see only this warning

    Notice: Undefined index: taxonomy in /wp-content/plugins/meta-box-aio/vendor/meta-box/mb-custom-post-type/inc/taxonomy/register.php on line 113

    But this warning shows with MB AIO 1.10.7 as well, which does not freeze up.

    Next I started disabling AIO Extensions 1 by 1. The one that fixed it was disabling "MB Include Exclude". Then my "edit field group" loaded fine. It didnt matter which field group I'm editing (whether it's using include/exclude or not).

    I'm just happy I know how to avoid it, as it was locking up my whole site. I hope this can help!

    November 25, 2019 at 8:14 AM in reply to: Fatal error: Allowed memory size of # bytes exhausted #17099
    pzapza
    Participant

    After the latest update, also on a site with thousands of posts & taxonomies, editing or creating any field group in MB Builder is causing my browser to stall/crash

    October 17, 2019 at 3:57 PM in reply to: ✅Dot notation for MB Geolocation "type" #16566
    pzapza
    Participant

    Ohh, I feel silly now. Thank you!

    September 6, 2019 at 3:30 PM in reply to: ✅Dot notation for MB Geolocation "type" #16010
    pzapza
    Participant

    I tried this also but no results show in autocomplete. Perhaps it's just not valid to pass two arguments here? For my purposes address will work for now. Thanks Anh.

    August 24, 2019 at 5:03 PM in reply to: ✅Seeing an Uncaught TypeError with twig in AIO 1.9.2 #15834
    pzapza
    Participant

    Where can I download the version of MB AIO that doesn't have this "Twig" issue?

    This also broke one of my sites due to, I believe, a conflict with WPML and unfortunately disabling that plugin is not an option.

  • Author
    Posts
Viewing 15 posts - 16 through 30 (of 40 total)
1 2 3