Update 2.3.7

Hi Emile,

Yeah I’ve had some people expressing this issue (for some it seems to work fine).
I’m currently rewriting the permalink rules completely. I think I’ve found a solution which works stable but I’d love for someone else to test it too.
Could you post your email so I can send you a test copy (v.2.4)?

Sure!
You can reach me at [email protected]

Hello Jonathan,

I’ve got kind of the same issue:

I use your plugin to display a category created with “Custom Post Type UI”.
Until now everything worked fine, but since the update, the filter return nothing…

The strange thing is that if I use the filter (in front) after a research of the same “taxonomy” it display it!

For example:

myurl.fr/category/first/
Return blank content

myurl.fr/category/first/?s=first
Return the list!

Hope it will help…

Thanks for all!

• This reply was modified 6 years, 4 months ago by shkou.
• This reply was modified 6 years, 4 months ago by shkou.
• This reply was modified 6 years, 4 months ago by shkou.

@shkou

I’m working on a new version with a completely rewritten permalink structure.
In the meantime, could you try just resaving your permalink settings and see if that does it?

@jonathandejong

Just done but no changes.

@jonathandejong I tried the 2.4 beta, and it fixed my permalinks problems. On the downside: the conditional menu’s stopped working, Not sure if the 2 are related, tho.
I’ll might find some time later this week to do some more extensive testing on the permalinks issue. For now I downgraded tot 2.3.1 to the conditional menu working.

@emilipro thank you for testing it!

I’m currently working out the bug in the conditional dropdowns.
When I’m satisfied that should be stable I’ll push out 2.4 ??

Just to get some more meat on the bones.. What exactly is not working properly for you guys with the conditional dropdowns?

so far, what I’ve noticed is two things:
1. The “All” value are being disabled.
2. It does not take into account hierarchial terms. So a parent term is disabled even if children has posts in them.

The conditional dropdowns didn’t work at all. When changing a value in the first drowndown, the spinners spin, but the second one is updated. Alle values are still available and when you select a non-existing value you get redirected to an empty archive page (which is correct behavior of course).

Hmm interesting.. not what happens to me.
Emilio would you also be willing to send your complete WP DB to me for testing against? You can send it to the same email as before.

In my two test environments it works but with quirks.

EDIT:
Wowsa.. I had a look now in my code and just realized I’ve hardcoded the db prefix (wp_).. I deserve a good ole fashion beatin!
Is it possible that you are not using the default wp_ prefix for your DB tables?

• This reply was modified 6 years, 4 months ago by Jonathandejong.

You are correct. I was testing in a multisite environment, so my prefix was wp_4_.

I’ve just sent you an email with a new version to test ??
Hopefully it will work!

I’ve yet to fix the hierarchial issue but other than that I hope it works!

If you need another tester I would be happy to help. My sites using BTF are no longer working properly. One facet search only gives first page of results, and more than one facet gives a 404.

Thanks.

Same to me here like @debsher

Hi everyone,

So sorry for this issue!
Turns out I had some code in the pipeline which wasn’t ready and should not have been in the new version but it sneaked it’s way in…
I’m going to irresponsibly full on blame the fact that I’ve been stressing out finishing up my current projects before starting on a new job! ??

I’ve just now pushed up 2.4.0 which hopefully should fix the issue for you.
Since the rewrite rules are rewritten I’ve added an automatic flush of the rules when updating but if you still experience issues please try resaving permalink settings first before checking back here with a verdict on wether it worked or not.

In the meantime I will get drunk and try to forget this embarrassment!