Meta Box

Where in the docs is it mentioned that the validation does not work with the group field? Afaik the documentation only says "add a key validation to the field group settings". Since the group field has its own 'fields' key it should work according to the docs.

Hey Peter,

I switched to the 2023 theme, deactivated all plugins except

MB Custom Post Types & Custom Taxonomies
MB Settings Page
MB User Meta
Meta Box
MB Builder
MB Group

The MB Builder PHP Export is:

<?php
add_filter( 'rwmb_meta_boxes', 'your_prefix_function_name' );

function your_prefix_function_name( $meta_boxes ) {
    $prefix = '';

    $meta_boxes[] = [
        'title'  => __( 'Paten-Profil', 'your-text-domain' ),
        'id'     => 'user-profile',
        'type'   => 'user',
        'fields' => [
            [
                'name' => __( 'Profil-Bild', 'your-text-domain' ),
                'id'   => $prefix . 'profile_image',
                'type' => 'single_image',
            ],
            [
                'name'       => __( 'Fragen und Antworten', 'your-text-domain' ),
                'id'         => $prefix . 'qa',
                'type'       => 'group',
                'clone'      => true,
                'sort_clone' => true,
                'fields'     => [
                    [
                        'name'       => __( 'Frage', 'your-text-domain' ),
                        'id'         => $prefix . 'question',
                        'type'       => 'taxonomy_advanced',
                        'field_type' => 'select_advanced',
                    ],
                    [
                        'name' => __( 'Antwort', 'your-text-domain' ),
                        'id'   => $prefix . 'answer',
                        'type' => 'wysiwyg',
                    ],
                ],
            ],
            [
                'name'              => __( 'E-Mail', 'your-text-domain' ),
                'id'                => $prefix . 'email',
                'type'              => 'email',
                'label_description' => __( 'Abweichende E-Mail-Adresse', 'your-text-domain' ),
                'desc'              => __( 'Wenn keine E-Mail-Adresse eingetragen wird, wird die E-Mail-Adresse dieses Kontos verwendet.', 'your-text-domain' ),
            ],
            [
                'name' => __( 'Crew United ID', 'your-text-domain' ),
                'id'   => $prefix . 'cu_id',
                'type' => 'text',
            ],
            [
                'name'       => __( 'Patenschaft', 'your-text-domain' ),
                'id'         => $prefix . 'mentoring',
                'type'       => 'taxonomy',
                'field_type' => 'select_advanced',
                'multiple'   => true,
            ],
        ],
    ];

    return $meta_boxes;
}

the problem still persists

It is not about what data I collect, but which data will be processed by third parties, especially outside the EU. If I transfer visitor data like ip addresses without legitimate interest to google analytics, or another third parties, I have to ask the visitor before doing so to be GDPR-compliant. In Germany, we have recently had problems with lawyers who have issued legal warnings to website operators for the use of fonts hosted by google because of a recent judgment wich condemed the website owner to pay the visitor for "personal indisposition" (sounds crazy, I know). Technically, using unpgkg.com this is not different. It is advised to sign a CP-contract with third parties who is processing visitor data, or rely on corporate binding rules, which are heavily disputed over here since there are judgements that EU equivalent level of data protection could not be provided from a CDN concerning Cloudflare, so I can't agree with your statement that "Cloudflare rule is very strict about GDPR compliance, so you don't worry about that." Also transferring data outside the EU for displaying a tooltip, is hardly arguable as legitimate interest. As a web design provider, I don't want to deal with this legal complexity if I don't have to, and you should not force your customers to do custom coding to get around this. Hosting the necessary JavaScript locally makes it so much easier to be GDPR-compliant, and I can't see why it is beneficial to use Cloudflare unless I want to serve a high traffic website to visitors worldwide.

As long as there is internet available, everything works, of course. I guess one could unregister your script and register them again using a local copy. Why is it beneficial to use a CDN? It's easy to violate GDPR this way, using mb front end submission. I would not do this, and suggest you include your dependencies locally. In my point of view, there is no harm in doing so.

Meta Box website, plugin and all extensions are 100% GDPR-compatible. (https://metabox.io/privacy-policy/)

This is not true, since you should ask for consent before IP addresses are transferred to third parties. I think no one cares if that happens on the backend of a content management system, but for the front end, it's another story.

Thanks Peter, I did know about the workaround.
I would appreciate it, if you update this thread when this is fixed. I like the idea of being subscribed per mail to issues I report.

Thanks for your guidance so far. I did take a look at Memory's wp-content/themes/memory/inc/customizer/customizer.php and noticed that

	$wp_customize->add_control(
		'site_description',
		array(
			'label'   => esc_html__( 'Site Description', 'memory' ),
			'section' => 'title_tagline',
			'type'    => 'checkbox',
		)
	);

is used to add a checkbox inside the Site Identity Panel below the 'title_tagline' inputs. So i guess i can't define this position inside the meta box custom fields definition?

Currently, my field is defined as follows:

$fields[] = [
    'title' => __('Copyright', NAME_SPACE),
    'id' => PREFIX . 'copyright',
    'panel' => '',
    'fields' => [
        [
            'name' => __('Copyright', NAME_SPACE),
            'id' => PREFIX . 'copyright',
            'type' => 'text',
            'label_description' => __('Text after copyright. Appears in the footer.', NAME_SPACE),
        ],
    ],
];