Forum Replies Created
-
Posts
-
Hi Knut,
No worries, I have manually changed the domain for you, it should be visible on your products page too. No further action is needed at this point, if it asks for a license it should automatically see the correct domain.
In case of any issues, please add temporary back-end login and (s)FTP details and I will take a closer look.
Hi Ernest, an additional question related to the missing terms in the dropdown list. How are the terms that I exclude from the taxonomy removed from the filter dropdown?
Basically their IDs are passed along to be excluded from the
get_terms()function call via a paramater. So the list is requested from WP first, then processed further.Hi David,
The only thing visible from this log is that the interaction registration when clicking on a search result fails for some reason.
Are there any more detailed logs in the PHP error log on this by any chance? Error 500 is very generic, usually it is returned by the server when there is a fatal error during script execution and is usually logged in the PHP error log with exact details revealing the exact problem.
Very interesting, I have no clue whatsoever why is it happening. Could be some sort of a weird bug somewhere, but the plugin requests the terms from WordPress internally in the first place, so it may actually be something in the WP core.
The back-end redesign is going slowly but surely. Recently the search cache and the search statistics interfaces were rebuilt. Next comes the rest of the menus and finally a completely new search configuration interface – in fact it is going to be separated to 3 different “template” areas, one for the search bar, one for the filters and one for the results – and each different search/filter/result configurations can be paired with each other.
It is still a long way to go though, no estimate at this time.Hi Matt,
Sounds like something went wrong in the builder. Perhaps a margin or a padding was added at the end of an element there, or the element order has changed.
Without seeing the issue I can’t tell unfortunately, but even then it is likely related to the Divi builder, which is out of the scope of our plugin.I believe Divi does backup draft saves to which you can revert back, I would try that first for sure.
Directorist is a pretty solid solution in my opinion, I am not aware of any other one, although I am no expert in this field. The only downside is that filtering by the custom fields is problematic due to the separate fields, but aside from that everything should be okay.
The names issue I assume is likely due to some taxonomy terms being selected to be returned as results. Make sure that nothing is selected here. Those settings are to return the actual taxonomy terms as results, which is likely not something you are looking for.
Hi!
My guess is that the higher level term is not associated with any posts only the lower level ones? That may explain the issue, WordPress gets a bit funky when returning the terms list, it tends to exclude parents when all their child terms are also excluded.
I see Matt.
The shortcode
[wpdreams_ajaxsearchpro_results id=1 element='div']is to move the live results container that comes with Ajax Search Pro from below the search bar to a custom position on the page, so it is not what you are looking for.Results page customization should be done via the page builder, search plugins have no control over the results archive layout, it is all controlled by the theme/builder. I am sure divi 5 has a capability to customize the results page loop and to also include ACF fields in there. Here is their official guide on the baseline. If you need more help with that, you may have to ask their support on how to include certain fields as I am no expert with divi 5 building unfortunately.
Hi,
The results page is completely up to the theme or the page builder – in your case the Divi theme builder. The plugin has no effect on that, it is entirely controlled by the theme builder.
Each site has a single results archive, however you can use the search to filter a custom divi5 loop, just follow this guide. That is likely very close to what you are looking for.
I see, I guess they have some sort of a list to which field goes to which label.
Searching these shouldn’t be an issue. However I don’t know if this type of structure is usable for meta-type filtering, as each value is also associated to a separate field (as far as I can tell), and that’s something I have not seen before in the past 15 years. So for example instead of having a single “languages” field to store the languages for each post, there is multiple completely separate fields scattered like “_checkbox-1”, “_checkbox-2” which signify which languages the given post is associated to. So if you were to make a checkbox filter for that, it’s very problematic, as each checkbox should also be attached to a different meta key, which is not how meta filters work.
Normally you make a filter for the “languages” field and filter plugins will fetch the values for that field across the database and generate a checkbox filter for it. But here every checkbox is tied to a different field and a different value, which is something no plugin search/filter can deal with.
Their out of the box solution is likely coded to this exact structure.Hi!
I am back. After some looking around and examining the source code I have found the custom fields. They have a very generic title scheme, basically all custom made text, checkbox and other fields are stored as “_custom-checkbox-1”, “_custom-text-1” etc.. so it was not trivial to find them. It is impossible to tell which one is which, but it does not matter much, I selected everything I could find for indexing.
The keyword count went up greatly, the values are nicely stored in the fields, so they are searchable.Now in case you create more search engines, then make sure to select the index table engine, and you are good to go.
