• Resolved bonafidengo

    (@bonafidengo)


    Hi, we are having an issue in making the Premium Staatic Search to work in a fully static site hosted on S3+Cloudfront in AWS.

    In this page ([ redundant link deleted ]) you can notice a standard search input.
    If you type “fly” then a search result shows below it and clicking on it works fine.

    The problem is if you press the Search button. The site generates correctly the standard search query “s=fly” but the site does not go to the Search Results page as expected, instead goes to the home page.

    Both WordPress and Staatic are the latest version. We are also using the free WENS template and the Polylanguage pluginfor having the multilingual paths (like /en/).

    If we test the site from the wordpress server, then all works fine, the issue is only ith the Staatic export and the Search integration enabled.

    Thanks for any help.

    • This topic was modified 3 days, 21 hours ago by bonafidengo. Reason: mispelling

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Frank

    (@staaticfrank)

    Hi Lorenzo,

    Thanks for opening the topic.

    I noticed we also replied to your email this morning with more detail, but to summarize here: the Staatic Search integration is working in the sense that the autocomplete suggestions are being loaded correctly and selecting a suggestion redirects to the indexed static page.

    The part that does not work is the standard WordPress search form submission using ?s=fly. That is a dynamic WordPress search results request. It works on the WordPress server because WordPress/PHP handles the query, but on the exported static site there is no WordPress runtime to generate arbitrary search result pages for ?s= requests.

    For a static deployment, the recommended options are:

    1. Use the Staatic autocomplete results and adjust the search form/button so it does not submit to the normal WordPress ?s= URL.
    2. Replace the submit button with a non-submit search/icon button so visitors select from the autocomplete results.
    3. If you need a full search results page, create a custom client-side static search page that queries the Staatic Search API and renders the results in JavaScript.

    Since this concerns the Premium Search integration, let’s continue through the email thread for specific implementation guidance. Happy to help you get this demo-ready.

    Moderator Support Moderator

    (@moderator)

    Hi, we are having an issue in making the Premium Staatic Search

    For pro or customer support, please contact the developer on their site. This includes pre-sales information.

    As the developer is aware, customers may not be supported on this site.

    https://wordpress.org/support/guidelines/#do-not-post-about-commercial-products

    Moderator Support Moderator

    (@moderator)

    @staaticfrank Don’t support customer on this site again. Direct them to your site instead. I am closing this topic.

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

The topic ‘Premium Search not working’ is closed to new replies.