KS

Thanks for the reply!

Ok I see, the callback overtakes most of the plugin settings. Then I don’t quite grasp if what I’m trying to do is possible.

I have one custom post type (leistungen) and two taxonomies (ltag and leistung).

1. In the plugin I set the to show all leistungen CPTs and filter on the terms of the ltag taxonomy.
2. I show the filter on my leistung taxonomy term pages, I can filter fine.

But because it outputs all CPTs and I only want to show the ones related to the current “leistung” taxonomy, I then created the callback, which limits the CPTs but breaks the ltag-taxonomy filter.

What I don’t understand is whether it’s possible to have a callback function that limits the CPTs output in the loop, but still allow for the taxonomy filter to function?

Hello, many thanks for the reply and the pointer about the callback!

I created a callback like this:

add_filter('ymc/filter/query/wp/allowed_callbacks', function($callbacks) {

  $callbacks[] = 'custom_query_leistungen';

  return $callbacks;

});

function custom_query_leistungen( $args ) {

  return [

    'post_type' => ['leistungen'],

    'posts_per_page' => -1,

    'tax_query' => [

      [

        'taxonomy' => 'leistung',

        'field' => 'id',

        'terms' => (int) $args['page_id'],

      ]

    ]

  ];

}

This picks up the taxonomy term page I’m on and I can limit the posts shown in the output to the current term, which is great. But I still don’t quite understand its limitations, because when I do this, the plugin filter – which is a different taxonomy – then no longer works.

How can I write the callback so that I limit the posts to the current taxonomy, but still allow filtration on the taxonomy I have defined in the plugin filter?

Thanks for the screenshot, I can see it now (partly). This is, however, a pro feature it seems, it’s not available in the free version of the plugin here in the repository and hidden behind a “PRO ONLY” blocker.

Hi Patrick, many thanks for the quick and informative reply!

1. This happens even on pages without footnotes.
2. 1,2… 10
3. No

I have tried the temporary workarounds you suggested, as well as the “Suppress Footnotes” options, but it provides no quick fix. I have also tried turning of all plugins apart from Footnotes Made Easy, as well as switching to the 2025 standard theme, but that also doesn’t help.

What’s interesting, is that the problem happens on pages that don’t have any footnotes, such as the frontpage. Also, it happens in the admin, sometimes when opening pages I get errors such as:

Fatal error: Maximum execution time of 30 seconds exceeded in /wp-includes/query.php on line 413

On a custom post type post (which is where I use the footnotes), I’m now getting an error relating to line another code line:

Fatal error: Maximum execution time of 30 seconds exceeded in /wp-content/plugins/footnotes-made-easy/footnotes-made-easy.php on line 308

But this might just be it timing out earlier.

I’m not sure what else I can do to test, or how I can help bugfix? I also don’t know if this is just related to my (pretty standard ) server setup, or a more general bug. Unfortunately, if I deactivate the plugin, everything else works fine and fast.

• This reply was modified 4 months ago by Yui.

Hello Archita, many thanks for the reply and also for making the screencast!

Block defaults are useful and I’ve used them in the past, but precisely because they only add settings to new blocks getting added, I find they lack usability a lot of the time, especially if you already have a lot of content on your site using Kadence blocks.

To my mind, it would be more powerful to be able to define generic defaults that apply to a block’s settings, unless those settings have already been defined for a specific block. That way, I could change the defaults for all specific blocks, not just new ones getting added.

In my specific case, what I don’t understand is why Kadence adds a margin-bottom of 0 to the unique class of the block and not just to the block in general? If it added the margin to the “kb-row-layout-wrap” class instead, it would be easy enough to override this in your stylesheet, but because it gets added to the unique class, it complicates settings real defaults..

A different question, but still about the maps – does anyone know to change the marker redirect, so that it doesn’t open in a new tab? I’m linking internally from the map, so would prefer to stay in the same tab.

Hello @bcworkz many thanks for your very useful reply! I hadn’t come across that filter before, very interesting.

Yes, the number slug restriction is due to pagination and in our case, it’s very unlikely to have pagination for 2024 pages, so that shouldn’t be an issue. I’m still in two minds about whether to disable the filter or not, it is useful to stop duplicates, especially if other people are working on the site and forgetting to be careful.

Either way, thanks a lot for pointing me in the direction of this filter!