Login

To vote or comment, enter your email and we'll send a magic link

Showing posts
1
Deep ACF Fields can't be indexed as of 4.0.8
open
There is an issue with FacetWP_Integration_ACF::index_acf_values(). Fields of any significant depth - 3+ fields would be affected it looks like - will not have the correct $sub_field object retrieved. I believe this line (95 in acf.php as of 4.0.8) is the problem: $sub_field = get_field_object( $hierarchy[0], $object_id, false, false ); $hierarchy[0] is going to consistently get the field information for the second level (as an earlier array_shift() already removed the first element). This will only be correct if the field being indexed happens to be at the second level. I haven't tested this extensively but I believe the correct call would be: $sub_field = get_field_object( end( $hierarchy ), $object_id, false, false ); Whatever the final field in the hierarchy is, however deep it may be, that's the actual target value we want to get field info for.
πŸ’¬ 0
0
Presets for query builder
open
I think having presets for query builder in a dropdown that cover a lot of the basics would make learning and using FacetWP much easier. Alternatively, a repository of example queries would help that isn't mixed up in gists and in the Facet UI on templates page you can link to it.
πŸ’¬ 0
0
Multiple search terms
open
Ability to add more than one search term in searches using a comma. For example: cars, trucks. Something like 'tagify' where the inputs become tags (https://yaireo.github.io/tagify/)
πŸ’¬ 2
1
Improve accessibility for slider element handles
open
Hi there. We're using axe DevTools to analyze accessibility issues. We noticed that the front-end slider element handles (with class .noUi-handle-lower & .noUi-handle-upper) do not have an accessible name. To solve this, axe suggests to fix at least one of these issues: 1. aria-label attribute does not exist or is empty 2. aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty 3. Element has no title attribute
πŸ’¬ 0
2
Add ascending/descending sort order
open
I would like to be able to switch between ascending and descending sort order in facets. The current "sort by" options are hardcoded. For instance, I would like to use fSelect & sort by descending term order (instead of the current default which is ascending).
πŸ’¬ 3
2
Sticky elements in Elementor
open
Currently, when a facet is added to a 'sticky' element in Elementor, so that it remains visible upon scrolling, that facet appears twice in the mobile flyout (because of how the sticky feature works in Elementor). So currently, we have to choose between making a facet sticky, OR providing a mobile flyout for our users. It would be great if we could do both.
πŸ’¬ 0
1
FacetWP automatic outlining items in layout / templates / builder
open
Atm, when you add multiple items below each other in the Layout Builder, and then make multiple columns, the items are stapled in each column separately. This is fine for some situations. However, for other situations, we might want to have each item in the column at the same height as the corresponding items in the other columns. It would be nice if FacetWP allowed for outlining the items in the layout, so that each item is on the same height, across all columns. Useful options would be to be able to outline each item to "top", "centered" or "bottom".
πŸ’¬ 3
2
FacetWP should work better with GiveWP
open
We use GiveWP as donation software on our website. It would be great if GiveWP would work better with FacetWP. For example, we would like to add to each form in the overview the nr of current donors and donations for that form and the total amount raised for that form. At the moment, this is doable via custom code snippets, but this is not ideal. It would be better if the number of donors, donations and the total donated amount could be selected in the elements that can be selected in the FacetWP settings. see also: https://feedback.givewp.com/feature-requests/p/facetwp-should-work-better-with-givewp
πŸ’¬ 2
4
Composer Installation
open
Ability to install via Composer w/ key and version number, so it works with Bedrock without having to hack it.
πŸ’¬ 3
0
Code Editor For Advanced
open
A basic code editor vs just a textbox would be welcome for editing longer queries. And perhaps a preview would be cool too for the current template as you make changes or if it breaks.
πŸ’¬ 0
4
Layout Builder - Copy Visual to Advanced
open
It would be real neat to build the visual layout and then, when you click to "Switch to advanced mode" the PHP and markup is written for the layout you just built.
πŸ’¬ 1
5
Add URL var to Load More pager
open
It would be great to add an option to display page numbers for the Load more pager. This way, archive pages location can be preserved when navigating to a post and back again.
πŸ’¬ 0
5
Preload + User selections
open
Preloaded facet choices should ideally show up in the `User Selections` box. Currently they aren't.
πŸ’¬ 1
1
Create a visual interface for duplicating facets and templates
open
duplicating facets and templates is possible atm (https://facetwp.com/how-to-clone-a-facet-or-template/) but it would be easier + more clear to new users if there was a visual interface for making a duplicate, e.g. with a 'duplicate' button behind each facet and template. Suggestion: replace the red cross that appears when you hover over a template/facet to delete it, with 3 items: 1) pencil for editing, 2) red cross for deleting, 3) the 'two pages icon' for duplicating
πŸ’¬ 1
2
Responsive layout options
open
The ability to set layout options at certain breakpoints or for the layout to act more like a bootstrap grid. I just noticed that one of the test sites we are working on with a facetwp layout is not responsive.
πŸ’¬ 0
2
Accordion behaviour for hierarchical checkbox facet
open
It would be nice if hierarchical checkbox facets would behave like an accordion instead of a toggle for each item separately. Now, if you click on a parent item, the children open. Then if you click on another parent item also those children open too. The list can get very long and it requires the user to make multiple clicks to contract all child lists again. It would be nice if a click to expand, contracts all the others. Maybe this behaviour could be optional.
πŸ’¬ 4
4
Conditional Logic improvements
planned
I have the following suggestions for improvement of the Facetwp conditional logic add-on. On a certain term archive page, I have set up some conditional action based on a chosen selection for a Type facet (based on post types). For example: if Facet Type is 'Accommodation' -> show several additional facets, to drill down in Accommodations. And else do the opposite. This works of course, but it has the effect that on my Accommodations archive page, the same 'drill down' facets are not shown, because the whole Type facet is not active/present there, and the 'Else do the opposite' is the cause of this. So what I would suggest is: - the condition that says IF Facet X is Y then A, should work like: IF Facet X EXISTS AND is Y then A. Or at least make it optional to add a condition that is actually exists. - The conditional 'Page URI' could help also in this case, but is unusable now, I have to enter a hard url. What I cannot say now, but would be very helpful: if page uri = taxonomy X, or = post_type_archive X. Or even more flexible, make a custom field where I can write WP conditional statements myself, selecting the exact archive pages this conditional ruleset or rule should apply to. Basically, this Conditional Logic add-on is not usable in my case because I have different types or term- and post type archives with different facets. And the 'else do the opposite' now prevents facets from showing up, purely because the 'conditional facet' is present on some pages and not on others. In one case I could solve it by making a 'counteract' ruleset with the page uri field set to NOT. But this does not work with taxonomy term archive pages for example. One unpractical workaround I did not try would maybe be to use the Custom selector option and write some jquery that selects a sibling, thus not selecting it if the sibling is not there. But this is getting unnecessarily complicated, as I have many facets and this situation is there for a lot of conditions I would like to build.
πŸ’¬ 4
17
Exclusion Filter
open
Allow the option to exclude items, for example if I have a recipe site and I want people with a food allergy (say nuts) to be able to show only items that don't include nuts, we have the option of adding an exclude facet.
πŸ’¬ 4
14
Openstreetmap / leaflet Support
open
An extension for the map facet that grants you the option to choose between OSM or google maps would be nice.
πŸ’¬ 7
11
Facet block support
open
Make facet features available from the WP block editor.
πŸ’¬ 9
6
Taxonomy facet - only show children of the archive term
open
If you're on a term archive page and you have a facet using that same taxonomy, the choices shown should **only** be children of the current term
πŸ’¬ 1
0
fSelect - selected value disappearing when limit is set
open
Prevent selections from disappearing if a display limit is set and the selection isn’t within that limit (#19583)
πŸ’¬ 0