Are those Archive Pages still posts in the “page” post type? If so, you can probably create a filter hook on relevanssi_content_to_index that would use the custom query to provide the archive page content for Relevanssi.
Thread Starter
Anonymous User 12905264
(@anonymized-12905264)
Hello Mikko,
Thanks for your answer. Bricks uses a separate space (post-type) for template usage.
Normal Page: https://staging.fotohof.org/ausstellungen/
Archive Template: https://staging.fotohof.org/shop/buecher/
Reader Access: https://staging.fotohof.org/wp-admin/?wtlwp_token=4bd42695ff03a638f9d0e640364994ff06c730059ddae9e88eb7db0a51c39340409f7fc4ac6e3ecebd8c2ed5d1daab720b8753002b6fb59f78aebb927f663568
On the archive template page are two issues, loading takes really long and when you select a facet it messes up the order imposed by Bricks query builder.
I would be happy to give you admin access if it would help to find why it is not working on archive pages.
Bricks has multiple filters regarding the query as well. I don’t know if these could help to make Relevanssi fully compatible.
https://academy.bricksbuilder.io/article/filter-bricks-terms-query_vars/
I hope there is a way to make these two fantastic resources work together!
So the archive page is just a taxonomy term archive? Relevanssi Premium can index those. Relevanssi Premium indexes the term title and description, and if you have other content on the archive page you want to include, there are filters for that. But the free version of Relevanssi cannot index term archive pages; that’s strictly a Premium feature.
But based on what you’re saying, I think we may not be discussing the same thing. Please explain in more detail how Relevanssi is not working on the archive pages. What kind of results are you expecting, and what is wrong?
I can’t comment on the interaction between Bricks and FacetWP. That’s something for FacetWP support; Relevanssi isn’t involved in that.
Thread Starter
Anonymous User 12905264
(@anonymized-12905264)
Hello Mikko,
thanks for the answer. I try to explain it better.
I am using WPGridbuilder for the Facets, which can use Relevanssi for the search facet. I have already talked to WPGridbuilder’s support and also tested it myself. When using only WPGridbuilder’s facets everything also works on archive pages, but when using Relevanssi the issue starts. So it is not a WPGridbuilder issue.
This behavior you can see at: https://staging.fotohof.org/shop/editionen/ Here there is the “normal WP search” hooked into the search facet and not Relevanssi.
On the Bricks site I am using their query builder to create the base query: https://academy.bricksbuilder.io/article/query-loop/
Then I use GridBuilder’s Bricks Widget to connect the Facets to Bricks query.
On the search facet I set the search provider to Relevanssi.
On the normal page (https://staging.fotohof.org/ausstellungen/) everything now works as expected.
On the page where the archiv template is running (https://staging.fotohof.org/shop/buecher/) Relevanssi does not take Bricks query loop into account.
In the bricks query loop I have e.g. set up the order to a meta_field, but when starting using the facets, it resets the query loop to the standard archive query (I guess).
You can see the behavior when you open the page above in a fresh browser it starts with “Hansgert Lambers”, but when you press on “Monografien” it changes the order. Also when you then reset the facet “Alle” the order is now different than when you first open the page.
My guess is that Relevanssi doesn’t get the information from the bricks query loop to know, what the “start query” should look like.
It also is extremely slow compared to the normal page.
I am happy to pay for premium, but it must work in conjunction with bricks and the speed should also be fine.
I hope this explanation is bette now.
Thanks a lot for your time!
Thread Starter
Anonymous User 12905264
(@anonymized-12905264)
Maybe here are some docs which could help: https://academy.bricksbuilder.io/topic/filters/
-
This reply was modified 1 year, 6 months ago by
Anonymous User 12905264.
I’m sorry, but I can’t provide support on this. This combination of Bricks, WPGridBuilder, FacetWP and Relevanssi is too complicated. I know nothing of WPGridBuilder and only a little of Bricks and FacetWP. I can support Relevanssi, but I can’t support Relevanssi in combination with three products I don’t know.
Upgrading to Relevanssi Premium won’t help. I can’t promise anything here, and I can tell right away that all this is too much for Relevanssi Premium support. If everything works well without Relevanssi, perhaps the best solution here is to remove Relevanssi.
If you are interested in debugging this closer yourself, I can give some pointers.
Thread Starter
Anonymous User 12905264
(@anonymized-12905264)
Hello Mikko,
Facet WP is not used.
The issue only lies between Bricksbuilder and Relevanssi. I guess that Relevanssi is not getting the “right” loop, and reverts back to the normal WP archive loop.
I need to tell Relevanssi somehow to “listen” to the loop, which is created by Bricks query loop builder.
I still don’t know what WPGridBuilder does. It claims to be compatible with Relevanssi, which means it should invoke Relevanssi and hopefully in a way that respects the other parameters.
Since WPGridBuilder says it’s compatible with Relevanssi, I would recommend you take this up with them. They’ve implemented the Relevanssi compatibility in the plugin, so that means they know how WPGridBuilder works and they also know how Relevanssi works. Thus, they are much better suited to answer your questions.
