Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Got it! Thank you for the answer!

    Do you have a timeframe for the development of this addon?

    Hi! I also need to do the same thing 🙂

    I need to render several Collections ( seperate post types ) as 1, whithout switcher by CollectionMenu.

    As I understand I need to create another Collection with all post types togeter. I managed to do that. But faced with the issue that Post on update is not pushed its changes to Typesense. So I would have to manually Delete and Index all posts after a single change on any post.

    Can you please give me a hint how to push single Post changes in update?

    Thread Starter sbdev1stepan

    (@sbdev1stepan)

    Hello @codemanas ! Thank you for the answer)

    Yes setMutableTerms and setImmutableTerms work. There are 2 filters set :
    1. mutable – Article-topics: Residential. Yes it can be closed
    2. immutable – Article-types: tierra-grande . It is hidden form user.

    The issues I would like to improve :
    1. I have to add immutable terms on each render Event.
    swtInstance.helper.addDisjunctiveFacetRefinement(taxSlug, term);
    Maybe there is a way to add that params to the request.

    2. I can change filter request on render Event only. I have to call the following function several times in order to set my mutable/immutable terms
    swtInstance.helper.search()
    Maybe there is a better way to do it

    Thread Starter sbdev1stepan

    (@sbdev1stepan)

    ( 3 ) When you change post type all changes are lost and don’t work again. Can you help with it eigther?

    Thread Starter sbdev1stepan

    (@sbdev1stepan)

    Here your are the link.

    I have several taxonomies. I need to make some Terms to be mutable some immutable. Due to your help I managed to achieve this the following way :

    1. I store the mutable/immutable terms in data-attributes in .cmswt-InstantSearch.

    2. add params :

    1. for the first render I add mutable Terms swtInstance.on(‘render’, setMutableTerms). Mutalbe means the user can close it.
    2. on each search click I add immutable params swtInstance.on(‘render’, setImmutableTerms) . Immutable means the user can’t close it. And also hide HTML for .cmswt-Filter and .ais-CurrentRefinements-item.

    3. After adding mutable/immutable params call swtInstance.helper.search();

    On the example page ( link ) you can find both mutable and immutable Taxonomy terms.

    But it in my opinion it is not the best way to do it.

    (1) The filters are still there though invisible and there are several searches

    (2) The search function is called several times on each click

    Can you please help me with the above question?

    • This reply was modified 2 years, 8 months ago by sbdev1stepan.
    Thread Starter sbdev1stepan

    (@sbdev1stepan)

    Thank you for the response!

    The code you provided does the same as swtInstance.renderState[postType].refinementList[taxSlug].refine(term);
    So they are added to CurrentRefinements. And

    1. Is there a way to imitate the exact behaviour of data-additional_search_params?
    2. I need to do it on each Filter click. I found just swtInstance.on('render', setPresetTerms); Event. Maybe there is better Event for this purpose?
    3. Can you please share Docs for this plugin JS or Git if it is public? Because your site doesn’t containt detailed info and Instant search JS ( site ) is not all present in the plugin script. Or the only way is to ask you?))
Viewing 6 replies - 1 through 6 (of 6 total)