Jan

Hi @zahardoc

Meanwhile, this went back and forth.

To fix the issue on my site I added this php temporarily:

// SSP - Temp to debug page freeze issue

add_action('after_setup_theme', function () {
    if (!post_type_exists('podcast')) {
        register_post_type('podcast', [
            'label' => 'Podcast (early fallback)',
            'public' => false,
            'show_ui' => false,
            'supports' => ['title'],
        ]);
    }
}, 5);

add_action('init', function () {
    add_filter('map_meta_cap', 'debug_map_meta_cap', 10, 4);
});

// Fix: Force SSP podcast CPT registration to priority 10 instead of 11
add_action('after_setup_theme', function () {
    // Make sure SSP class exists before manipulating
    if (class_exists('SSP_Post_Type')) {
        // Remove SSP registration at 11
        remove_action('init', [ 'SSP_Post_Type', 'register_post_type' ], 11);
        // Add SSP registration at 10
        add_action('init', [ 'SSP_Post_Type', 'register_post_type' ], 10);
    }
}, 9);

function debug_map_meta_cap($caps, $cap, $user_id, $args) {
    if (isset($args[0]) && is_numeric($args[0])) {
        $post = get_post($args[0]);
        if ($post && $post->post_type === 'podcast' && !post_type_exists('podcast')) {
            error_log('⚠️ map_meta_cap called for unregistered post type "podcast"');
            error_log('Capability: ' . $cap);
            error_log('User ID: ' . $user_id);
            error_log('Post ID: ' . $args[0]);

            // vollständiger Stacktrace
            ob_start();
            debug_print_backtrace(DEBUG_BACKTRACE_IGNORE_ARGS, 20);
            $trace = ob_get_clean();
            error_log("Backtrace:\n" . $trace);
        }
    }

    return $caps;
}

Is there anything else that you can suggest based on the testing done by mindctrl ?

Any advice is much appreciated.

Best,

Jan

Hi @zahardoc,

I’ve thoroughly reviewed my own theme and functions.php. None of my custom code touches the podcast post type directly, except for the standard filter ssp_register_post_type_args to add 'revisions' support — which is documented and used as intended.

From the backtrace, the error is triggered during a wp_ajax_heartbeat request inside the post editor for a podcast post. At that point, current_user_can('edit_post', $post_id) triggers map_meta_cap(), but the podcast post type is not yet registered — resulting in the error and backend freeze.

My suspicion is that the post type registration (register_post_type('podcast', …)) may not fire early enough for AJAX calls. Could you verify if the registration is hooked into init or runs earlier?

Thanks again!

Thanks for getting back @prasunsen.

The issue has been solved in the meantime. I was related to a question-specific setting. After removing the flag, the “Go Ahead” button appears as desired.

Nevertheless, I’ll review the related JS code and fix the suggested issue.

Best regards,

Jan.

Sure, this is the explanation behind the “Details” -button:

Chrome has built-in safety features to protect you while you browse – like Google Safe Browsing, which recently found phishing on the site that you tried visiting. Phishing sites pretend to be other sites to trick you.

Even sites that are normally safe are sometimes compromised by attackers. Let us know if you think that there’s been a mistake and that this site doesn’t pose a danger.
Only visit this unsafe site if you’re sure you understand the risks.

Hi Bob (@prasunsen),

just wondering if you could share your thoughts regarding the above.

Any advice is much appreciated.

Best,

Jan

@Bokaz,

with the help of the Theme developer we were able to take a step forward.

The issue was caused by the SVG-Icon that is attached to the button: “When you add a SVG Icon to a Button it will wrap the button label in a <span> tag.”

We therefore added a CSS snippet to address this:

.gb-button span {
    pointer-events: none;
}

When setting up a Klick-All-Elements trigger the related Tag does fire. In Debug-Mode we can also see that the css-class is being recorded (Variables / KlickClasses).

We then created a new trigger and tag to record a specific events for one button (Filter: KlickClass equal to css-class). This time the tag does not fire.

What else are we missing to make it work?

Thanks,

Jan

@matomoteam – just wondering if you had a chance to look into this topic in the meantime. Thanks in advance.

Hi @prasunsen,

wishing you a very happy New Year.

Just wondering if you had a chance to look into this in the meantime.

Kindly let me know how you would realize this use case.

Thanks,

Jan