Forum Replies Created
- pridigitalParticipant6 months, 1 week ago in reply to: Add debouncing to the suggestions field #37369
Is there a way you could give us early access to this feature? Our live website is crashing because of this. Thanks!
pridigitalParticipant7 months ago in reply to: Bug when the term name includes the word “OR” #36986Thanks! That solved the issue.
pridigitalParticipant7 months ago in reply to: Bug when the term name includes the word “OR” #36952PS: The same issue occurs if the word “and” is used.
pridigitalParticipant7 months, 2 weeks ago in reply to: Custom sorting facet values #35892Yeap, that did the trick. Thanks!
pridigitalParticipant7 months, 3 weeks ago in reply to: Bug when filtering taxonomy term as a non logged in user #35814You were right! I’m sorry for the confusion. The Yoast SEO has a new experimental feature called “Remove unregistered URL parameters”. That was causing the bug. Thanks for your support anyway!
pridigitalParticipant7 months, 3 weeks ago in reply to: Bug when filtering taxonomy term as a non logged in user #35812Are you using a custom taxonomy and a custom post type in the demo? I think the bug is happening in that scenario only.
pridigitalParticipant8 months ago in reply to: Custom sorting facet values #35707Also, it would make sense to have an option to define the order. Here’s an example
2021 – Books
2022 – Books
2023 – Booksmight look better showing 2023 first 😉
pridigitalParticipant9 months ago in reply to: Custom sorting fields doesn’t seem to work properly #35378I see the “Item number” in both taxonomies. Which is why I was trying to use the WPSOLR_Events::WPSOLR_FILTER_SORT_FIELDS filter.
pridigitalParticipant9 months, 1 week ago in reply to: Custom sorting fields doesn’t seem to work properly #35376Hi there 🙂 the field name is irrelevant. Those were just examples, but yeah. Let’s say then:
Tax 1
– Item Number (should be hidden)
– Date
Tax 2
– Item Number (should NOT be hidden)
– Price
– DatepridigitalParticipant9 months, 1 week ago in reply to: Custom sorting fields doesn’t seem to work properly #35362Yes, if I remove my code I see the it. However, it also shows other items that are not supposed to be shown.
Let’s say I have the following scenario:
Tax 1
– Item Number
– Date (should be hidden)
Tax 2
– Price
– DateIf I remove my code then both taxonomies will show the date sort.
pridigitalParticipant9 months, 1 week ago in reply to: Custom sorting fields doesn’t seem to work properly #35311No, I don’t. I’m using the “Default View”.
pridigitalParticipant9 months, 1 week ago in reply to: Custom sorting fields doesn’t seem to work properly #35308Yes, but item_number is already an active sort in my sort screen. You can see it in the screenshot I shared before. Am I missing something?
pridigitalParticipant9 months, 1 week ago in reply to: Custom sorting fields doesn’t seem to work properly #35298As you can see here the item number would be my “acf_1” field.
Also for reference this is what I get from the default sort fields variable before overwriting it.
array(2) { [0]=> string(17) "sort_by_date_desc" [1]=> string(16) "sort_by_date_asc" }
pridigitalParticipant9 months, 1 week ago in reply to: Custom sorting fields doesn’t seem to work properly #35296Nope. Only after I manually add it in the code. Which is the weird part because I’ve added it in the backend through the WPSolr interface.
pridigitalParticipant9 months, 1 week ago in reply to: Custom sorting fields doesn’t seem to work properly #35286I’m using the WPSOLR_Events::WPSOLR_FILTER_SORT_FIELDS filter because I want to show different sort options for different post types. However, by doing that the HTML select returns the key for the label instead of the translation.
- This reply was modified 9 months, 1 week ago by pridigital. Reason: more details