Support Forum ยป User Profile

Forum Replies Created

Viewing 15 posts - 46 through 60 (of 95 total)
  • Author
    Posts
  • in reply to: โœ…unserialize(): Error - When using custom admin column #47274
    CodogCodog
    Participant

    Hi Peter,
    thanks for your response. However, in my context I cannot use another field type such as the single_image as this provides access to the media library popup. My file_upload field is part of a frontend submission form that MUST prevent my users from accessing the media library.

    Are there any other work arounds or options to fix this error?

    Thanks!

    CodogCodog
    Participant

    Hi Anh,
    thats great news. Thanks for letting me know! Where will this new functionality be documented?

    Thanks ๐Ÿ™‚

    in reply to: Broken MB Conditional Logic - MB Group #46464
    CodogCodog
    Participant

    Hi Peter,
    thanks for letting me know. Look forward to the fix ๐Ÿ™‚

    in reply to: โœ…Metabox 5.10.0 / Metabox AIO 1.30.0 - Max_clone - Issue #46443
    CodogCodog
    Participant

    Hi Peter,
    the recent update appears to have resolved my highlighted issues. Thanks!

    However, there are now new ones...

    Issue - https://support.metabox.io/topic/broken-mb-conditional-logic-meta-box-group/

    CodogCodog
    Participant

    Hi Peter,
    has the 5.10.1 and 1.30.1 updates resolved the highlighted issues? I have not had a chance to test yet.

    CodogCodog
    Participant

    Hi Peter,
    that is good to know. Any likely future release date when these will be fixed?

    Thanks ๐Ÿ™‚

    CodogCodog
    Participant

    ....further to the above I have also spotted an additional issue.

    I am also using the MB Group inside a MB Frontend Submission form.

    When using the NEW 'clone_empty_start' => true, attribute within the MB Group settings any sub-field within the group which has the 'required' => true, attribute set gets an error validation BEFORE a clone has even been added/created? This prevents my MB Frontend Submission form from being successfully submitted!

    The Required Fix
    =================
    Sub-fields within an MB Group that have the 'required' => true, attribute set should NOT be validated until a NEW clone has been added/created.

    Steps to Reproduce
    ===================

    1) Create a MB Group with sub-fields.
    2) Within the MB Group settings use the 'clone_empty_start' => true, attribute.
    3) Within the first sub-field in the MB Group set the 'required' => true, attribute.
    4) Fill out ALL fields within an MB Frontend Submission Form (So there are no other errors) but DO NOT add a MB Group Clone.
    5) Attempt to submit the form and you will see that it is not possible and the "Please correct the errors highlighted below and try again." error message is shown.
    6) Then add a new MB Group Clone - You will see that the first sub-field is highlighted RED and throwing an error validation?

    Again, I assume this is a bug that will be rectified shortly?

    I look forward to the fix ๐Ÿ™‚

    in reply to: Bug Metabox 5.10.0 #46201
    CodogCodog
    Participant

    I am also experiencing an issue with MB Group clones after the upgrade to 5.10.0. See thread here - https://support.metabox.io/topic/metabox-5-10-0-metabox-aio-1-30-0-max_clone-issue/. They could be related issues?

    in reply to: Frontend Submission - Google Maps - Custom Binding #45753
    CodogCodog
    Participant

    Hi Peter, thanks for the response. Yeah this was the bit I was unclear about? I assume you mean adding this:

    
    'geo' => [
        'api_key' => 'xxxxxxxxxxxxxxxxxxxxxxx',
    ],
    

    To some field group? Do you mean I need to wrap my "Map Field, Address Field , Hidden field" in a "Field Group and add the above? Not clear to me?

    As I am strictly doing this with code I would be grateful if you could show me a simple example?

    CodogCodog
    Participant

    Hi Peter, thanks for the response. It's not a deal breaker but it would be a simple nice addition to the Metabox Group functionality.

    in reply to: โœ…Frontend Submission - Google Maps - Hide Controls #45733
    CodogCodog
    Participant

    Thanks Peter, understood. Custom JS solution it is!

    CodogCodog
    Participant

    Hi Peter,
    thanks! Thought this was likely the case but wanted to check first. Thanks for your time ๐Ÿ™‚

    CodogCodog
    Participant

    Hi Peter,
    thanks for your guidance ๐Ÿ™‚ Unfortunately your suggested method is not working for me right now? I tried a very simple implementation to see if I can target and output a simple message and update the hidden_field value within an individual clone.

    My test function:
    ==================

    function output_to_clone(){
    
    	$post_id = $_GET['rwmb_frontend_field_post_id'];
    
    	$group_values = get_post_meta($post_id, 'group_id', true); 
    
    	$msg = '';
    
    	foreach ( $group_values as $group_key => $group_value ) {
    		if ( $group_key == 1 ) {
    			$group_value[1]['hidden_field'] = 'Something New';
    			$msg .= '<div class="alert alert-danger" role="alert">Group Key = '.$group_key.'</div>';
    		} else {
    			$msg .= '';
    		}
    	}
    	return $msg;
    }

    Function output
    ================

    Then within the cloneable group fields I just added the function call:

                [
                    'id'                => 'group_id',
    				'add_button'        => __( 'Add more', 'text-domain' ),
                    'type'              => 'group', 
                    'clone'             => true,     
                    'sort_clone'        => true,     
    				'group_title'       => 'Title {#}',
    				'collapsible'       => true,
    				'save_state'        => true, 
    				'max_clone'         => 3,
    
                    'fields'     => [
    					[
    						'id'   => 'hidden_field',
    						'type' => 'hidden',
    						'std'  => 'Hidden Value',
    					],
                        [
    						'before'           =>   output_to_clone(), // Function output
                            'name'             => __( 'Field One', 'text-domain' ),
    						'desc'             => __( 'Add a unique name.', 'text-domain' ),
                            'id'               => 'field_one',
    						'type'             => 'text',
                        ],
                        [
                            'name'             => __( 'Field Two', 'text-domain' ),
    						'desc'             => __( 'Enter a unique reference.', 'text-domain' ),
                            'id'               => 'field_two',
                            'type'             => 'text',
    						'required'       => true,
                        ],
                    ],
                ],

    Expected Test Outcome
    =======================

    1) The $group_key == 1 conditional check would output the $msg value for the individual clone that matches the key. All other clones would return an empty $msg.
    2) The $group_key == 1 - hidden_field would be updated to "Something New".

    Actual Test Outcome
    =======================

    1) The $group_key == 1 conditional check outputs the same $msg value for ALL cloned fields (IE: Group Key = 1).
    2) The $group_key == 1 - hidden_field value is NOT updated.

    I am obviously misunderstanding something here? Can you help me understand where I am going wrong? Thanks in advance ๐Ÿ™‚

    CodogCodog
    Participant

    Hi Peter,
    thanks for escalating.

    I look forward to the fix!

    in reply to: โœ…Word count bar in wysiwyg meta boxes #44782
    CodogCodog
    Participant

    I would really like this feature too!

Viewing 15 posts - 46 through 60 (of 95 total)