Jonathandejong

@grwebadmin

Hi!

Thank you for reporting this. I think the error is actually that for some reason the option don’t get loaded or you have never saved the settings and the plugin assumes it will exist as an array.

Either that, or you have made modifications using the beautiful_filters_post_types and do not return an array to it but rather a string.

<?php

$post_types = get_post_types(

array(

'public' => true,

'_builtin' => false

),

'objects'

);

$activated_post_types = apply_filters( 'beautiful_filters_post_types', get_option('beautiful_taxonomy_filters_post_types') );

?>

<?php if($post_types): foreach($post_types as $single_post_type): ?>

// HERE IS WHERE THE ERROR OCCURS BECAUSE $activated_post_types is not an array.
<?php if(in_array($single_post_type->name, $activated_post_types)): ?>

I’ve just pushed a new bugfix version 2.4.6 which should resolve this by both adding a fallback value to get_option and a type coercion into an array.

Still, I would suggest you check that you don’t use the filter and return a string.

Hi Giannis,

Yes there is a planned rework of the codebase which would include support for PHP 8.3. I can’t give you a timeline of this right now however. In the meantime if you’re as sick of deprecation notices as I am you might want to make some noise in this PR: https://github.com/WordPress/wordpress-develop/pull/5494 (disclaimer that this is mine)

Hi @bncpeter 🙂 please see https://ww.wp.xz.cn/support/topic/current-status-security/

Hello tony Tigerton 😉

Yes of course, will remove that with an update!

Hi!

Apologies for a long overdue answer and I hope you managed to solve it!

But I think this is probably caused by the fact that BTFs custom archive URLs are essentially the “core” archive with lots of parameters that we use custom rewrite rules to make it look pretty.

So while it says /business-directory/location/london/ in the background it’s a URL like /business-directory?location=london

So I’m betting that the third party plugin you use to work with these sticky posts don’t actually use the query parameters to determine what taxonomy or term is shown, but rather goes by the core built-in functions like is_archive() and is_tax() . Which isn’t wrong in itself! But it probably means it won’t work out the box with BTF.

Unfortunately I don’t think there’s a whole lot that I can do in BTF to help with this.. unless you have found something? If you are capable of a bit of coding you could probably do some custom checks using the pre_get_posts filter to supress sticky posts where you want to.

https://developer.ww.wp.xz.cn/reference/hooks/pre_get_posts/

Best of luck!