• Resolved James Joseph Finn

    (@jamesjosephfinn)


    Hello team. Hope you’re well. I’m wondering on compatibility of this plugin with SimplyStatic. They have native integration with Algolia, but I’m partial to supporting open source whenever I can. Thank you for making this software, and I look forward to giving it a try on this SimplyStatic project.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor digamberpradhan

    (@digamberpradhan)

    Hi @jamesjosephfinn
    We haven’t officially tested the plugin with it yet, so we can’t confirm full compatibility at this time. That said, if you decide to give it a try and run into anything unexpected, feel free to reach out — we’d be happy to take a look and help where we can.

    Thread Starter James Joseph Finn

    (@jamesjosephfinn)

    Awesome, thank you; and will do! Based upon your reply, is it correct for me to presume that the code you ship to the frontend communicates only with the Typesense API; i.e., it doesn’t make requests dependent upon a dynamic connection to WP? @digamberpradhan

    Plugin Contributor digamberpradhan

    (@digamberpradhan)

    @jamesjosephfinn

    Yes – the output is just html – and js and css ofcourse.
    The output is determined by php – but once that’s done – if the js and css is enqueued technically it should work.

    Does not make request to WP – just the initial html

    Thread Starter James Joseph Finn

    (@jamesjosephfinn)

    @digamberpradhan very exciting and good news! I’ll be testing this soon in the Bricks+SimplyStatic setup, and will report back. Based upon what you’ve said, I don’t anticipate any issues, but we shall see.

    Thread Starter James Joseph Finn

    (@jamesjosephfinn)

    @digamberpradhan Aside from having to write a simple function which hooks to cm_typesense_data_before_entry to filter the permalink prior to indexing, the plugin works like a charm in a SimplyStatic setup. I left a 5 star review which has the details.

    I have a question: Is there a way to customize the InstantSearch router? We need to utilize the router, which is a great feature, but the InstantSearch.js default URL format is absolutely not going to work for us. Can we pass a custom router config using something like cm_typesense_additional_config or cm_typesense_routing?

    Or are we stuck having to override history.pushState and history.replaceState in the browser? The problem with that approach is then having to also handle incoming requests server-side using template_redirect. A most cumbersome and brittle code pattern, and one which I would like to avoid.

    I greatly appreciate any pointers you can provide in this regard.

    Thread Starter James Joseph Finn

    (@jamesjosephfinn)

    Hello again, @digamberpradhan ! I hope you’re doing well in this crazy world.

    Quick question today: Could you please direct me to the repo which contains the source files? Hoping it’s available! That would be an immense help to me, and I would be most grateful.

    Thanks in advance!

Viewing 6 replies - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.