Remove WPDiscuz styling from WordPress head

Hi  lostnotstranded,

I'm really sorry, but there is no any way to do it. We'll take it into consideration for future releases.

I stumbled over this thread while searching for a solution for this problem.

To solve it I now iterate over the "wp_head" callbacks and search the right one to remove it:

function remove_wpdiscuz_custom_css()
{
    global $wp_filter;

    $priority = 10;
    $hooks = $wp_filter['wp_head']->callbacks[$priority];
    foreach ($hooks as $hook) {
        if (isset($hook['function'][0]) && $hook['function'][0] instanceof WpdiscuzCss && $hook['function'][1] == 'initCustomCss') {
            remove_action('wp_head', $hook['function'], $priority);
            break;
        }
    }
}

add_action('wp_head', 'remove_wpdiscuz_custom_css', 8);
 

@mirsch

I followed your suggestion and Query Monitor is showing that the hook is no longer registered inside wp_head, and yet... the inline CSS gets printed inside my document head regardless.

(no i'm not using a caching plugin)

Has anyone figured out how to stop initCustomCss from firing? Is the plugin doubling down on the method somewhere else?

@luboslives,

We've just checked on our test website and don't find such an issue. Everything works fine.
Could you please check one more time.

I've figured it out – I missed a small detail! I didn't realize @mirsch was using a hook priority of 8. I had it at 10 in my theme functions file. It might seem counterintuitive in a way, but it needs to have a higher priority than the initCustomCss hook so that it can deregister it before it's executed by WordPress.

I guess Query Monitor can't figure out whether something actually executed before being removed by a function that happens to have the same priority.