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!
Thanks for coming back to me. Yes I ended up using an Advanced Custom Fields field to indicate premium listings (didn’t use ‘sticky’ with the other plugin).
I then built in my own form, populated with tax terms, and used pre_get_posts as you suggested. I had greater control over other requirements that way in any case.
Was impressed with your plugin though, and thanks for the follow up!
Best regards.
Alright well I’m glad you managed to solve your requirements either way!
I’m due for refactoring this plugin, the work has started, but it’ll take some time given other priorities.
For that reason, what would you say is missing from the plugin today?
More hooks?
I know some “obvious” things like a block-based approach rather than widgets, update the design to fit the times etc.
It was a while ago now, so apologies, but I can’t remember the specifics of your plugin enough to offer feedback. I recall it worked great though straight out of the box.
On a general note, working with all kinds of sites every day, a couple of bug bears with plugins in general:
1) Plugins that add their own top-level menu item in the dashboard, particularly when it’s just their brand name. Worse, when they add to the top nav. Most plugins could comfortably fit their options under ‘settings’ or ‘tools’.
2) Over-styling their front-end. I can usually tell if a plugin is written well or not, by whether they leave their mark-up as vanilla html tags, to pick up theme styling, or whether they add lots of their own styling, requiring lots of overriding on my part with greater and greater css specificity. Some plugins offer a checkbox to apply plugin styling or not, which is fine too.
I’m almost certain your plugin did neither of these things, and it did the job as intended, so no complaints from me. Thanks again for your time developing it.
