Pono Press

Hello @ipstenu ,

Thank you once again for your valuable suggestions and sharing the code with with us.

We are excited to announce the release of version 0.1.0, which includes WP-CLI support. In addition to the command you provided, we’ve added new commands to delete and add specific documents by their IDs:

wp yuto add-documents post_type --ids=1,2,3

wp yuto delete-documents post_type --ids=1,2,3

As you suggested, we’ve implemented built-in support for multisite by appending the site URL to the index name, helping to prevent accidental deletions or indexing.

Please take a moment to check out the latest version and share your feedback.

We would love to hear any additional insights or suggestions you might have!

Regards,
Pono Press

That’s awesome! Huge thanks for whipping up the CLI command and sharing it with us.

We’ll definitely take a closer look at your implementation—really appreciate you making it GPL so we can incorporate.

Thanks again for your contribution—this will be super helpful for other users too with large sites.

If you have any other insights or tweaks, we’d love to hear them!

Regards,
Pono Press

Hello @ipstenu

Thank you for using the plugin and for your valuable feedback—it truly means a lot to us coming from you.

We will definitely implement the WP CLI command feature and are already working on it.

As for multisite support, we absolutely love your suggestion to use the site URL in the index name to prevent accidental collisions. This is a fantastic idea, and we’ll be rolling it out in an upcoming update!

Once again, we sincerely appreciate your feedback. If you have any more suggestions, please keep them coming—they help us make the plugin even better! ????

Regards,
Pono Press

Hello @vvaz ,

Hope you’re doing well.

Has the solution we provided using the hook resolved your issue? Please let us know.

If you need further assistance, feel free to reach out.

Regards,
Pono Press

Hello @rosigroupcom ,

Thank you for using our plugin!

We tested the plugin in a setup identical to yours, running WordPress version 6.7.2 and WooCommerce version 9.7.0. After importing the demo products and indexing them, the Autocomplete block functioned correctly on our end.

Please ensure that the product index is selected in the Autocomplete block settings, as shown in the screenshot here: https://tinyurl.com/2awkx33o

If the issue persists, could you share your site link with us?

Best regards,
Pono Press

• This reply was modified 3 days, 18 hours ago by Pono Press.

Hello @vvaz

Thank you for using the plugin and for your patience with our response.

To add a link at the end of the results list, you can insert it into the footer of the result template using the hook: yuto_autocomplete_${indexName}_footer_templates. You can find more details here: Yuto Hooks Guide.

Regarding the feature where pressing Enter redirects users to the search results page, it’s a great idea. However, since different post types have different search pages, we need to research the best approach. We’ll work on this and update you once the feature is implemented.

Regards,
Pono Press

Hello @djbox2018 ,

Kindly let us know if the solution provided resolves the issue you are experiencing.

Regards,
Pono Press

Hello @djbox2018

The problem arises because the anchor link doesn’t stretch to fill the full width of its container.

To make the entire region of the search result list item clickable, we have to stretch the width of the anchor link with CSS.

Simply add the following CSS to your theme or in the Editor’s “Additional CSS” section:

.aa-ItemWrapper {
  grid-template-columns: 1fr auto;
}

.aa-ItemLink {
   justify-content: start;
}

Although moving the anchor tag outside the list tag would resolve the issue, this isn’t feasible since the provided hook only allows modifications within the list tag only.

Regards,
Pono Press

• This reply was modified 1 month, 1 week ago by Pono Press.

Hello @djbox2018 ,

Thank you for using our plugin and for your patience while we addressed your concern.

The issue stemmed from the early invocation of the rest_{$this->post_type}_collection_params hook, which was introduced in version 0.0.7.

We’re happy to inform you that this has been resolved in the latest release, version 0.0.8, which is now available for update.

Regards,
Pono Press

Hello @zeonxkz

In version 0.0.7, we’ve introduced batch size indexing for each payload, addressing concerns about indexing large databases. You can learn more about this enhancement here. Additionally, we’ve updated the searchable attributes to improve search and indexing efficiency.

We’re actively working on partial synchronization and will share updates as soon as it’s ready.

We truly appreciate your feedback—it’s instrumental in making the plugin more efficient and functional. We look forward to hearing more of your thoughts and suggestions to continue improving!

Regards,
Pono Press

Hello @novaemployment ,

We inspected the site and looking at the console error shown, it seems like index is not set in the Autocomplete block setting.

Please make sure that once the block is inserted, you have selected the index in the right hand setting as shown in the screenshot here: https://tinyurl.com/228462e8

Regards,
Pono Press

• This reply was modified 1 month, 3 weeks ago by Pono Press.
• This reply was modified 1 month, 3 weeks ago by Pono Press.
• This reply was modified 1 month, 3 weeks ago by Pono Press.

Hello @zeonxkz ,

Thank you for using the plugin and sharing your valuable feedback! We truly appreciate it and welcome any other suggestions or improvements you may have.

We have primarily used a local server for testing and development, and we haven’t encountered the HTTP connection issue. Could you please provide more details about the problem? Specifically, are you able to establish a connection successfully from the configuration settings, or is the mixed content issue only occurring on the front end?

Regarding the large database synchronization, we greatly appreciate your insights on batch sizing and partial synchronization. We plan to implement batch sizing for each iteration, which should help address the issue with large database sync. As for partial synchronization, this requires further research since it would involve identifying already-synced and unsynced data, as well as determining specific data indices to ensure uninterrupted indexing.

We’ll keep you updated as we work on these improvements. While we can’t provide an exact ETA for this feature, we recognize the importance of enhancing batch indexing for large database synchronization and will prioritize it accordingly. At the same time, we are actively working on other features, such as the Instant Search block.

Thank you again for your feedback! We look forward to hearing any additional suggestions or ideas you might have.

Regards,
Pono Press

Hello @novaemployment ,

Thank you for using the plugin!

As this thread has already been marked resolved by the thread starter, it would be best to start a new thread for your issue. This will make it easier for us to assist you and for others to find relevant solutions.

Regarding the steps you followed, everything seems in order. However, we encountered a minor issue in version 0.0.5 related to saving the server URL, which has been resolved in version 0.0.6. Please update to version 0.0.6 and let us know if the issue persists.

If the issue continues after updating to version 0.0.6, kindly share the link where you are using the Autocomplete block so we can investigate further.

Regards,
Pono Press

Hello @harryleung ,

We are glad to hear the plugin has been helpful for you and that the issue you encountered has been resolved.

Regards,
Pono Press