Hi @finaukaufusi .
Two Questions:
1. What is the value of the Result Output setting on the search configuration page? It should be 'Title and Snippet'.
2. When you say you don't see it returned on your search page, do you mean on the webpage itself, or are you stepping through the code to see what is coming back?
Thanks, Timo
timozura → created an issue.
@christian-deloach we added in some flood control functionality. I'll update the docs soon, but the 1.5.0-beta5 release adds some flood control options (threshold, time window, message) to the search page configuration. It's disabled by default, but if you get a chance to test it out, let me know how it goes. Closing this issue for now though - hoping it helps ward off the bots.
There is an MR that needs review. It adds some flood control to the vertex search service if the flood control is enabled on a search page's configuration page.
To configure, edit the Vertex search page...check the box to enable flood control and set the threshold, window, and message values. Perform enough searches to hit your threshold and no more vertex searches will be performed until the window closes.
timozura → made their first commit to this issue’s fork.
Permissions will be dynamically created whenever a new custom search page is created using the VertexAISearch plugin.
For existing users and Vertex custom search pages, there is an update hook that will grant access to anonymous and authenticated roles.
The issue discusses adding permission assignment capability directly to the configuration form for a Vertex search page, but I'd rather just have user go to the permissions page as per usual.
@ananya.k Thanks for the patch. I made some other changes and added your changes in with those. Will be in next release.
timozura → made their first commit to this issue’s fork.
timozura → created an issue.
Closing in favor of : https://www.drupal.org/project/vertex_ai_search/issues/3507216 ✨ Create a REST Resource for Vertex Search Active
timozura → created an issue.
timozura → created an issue.
timozura → created an issue.
timozura → created an issue.
timozura → created an issue.
TimoZura → created an issue.
TimoZura → created an issue.
A keyword can now be associated to multiple promoted results. Modifying copy to explain this.
TimoZura → created an issue.
TimoZura → created an issue.
TimoZura → created an issue.
TimoZura → created an issue.
TimoZura → made their first commit to this issue’s fork.
Closing. In 1.0.0-beta2 release.
Fixed
TimoZura → created an issue.
Updating with a new configuration element for enabling autocompletion on the core search block form.
TimoZura → created an issue.
TimoZura → created an issue.
TimoZura → created an issue.
TimoZura → created an issue.
Adding link to the vais_promos repo for an example of the SearchResults plugin.
Adding information about the SearchResult custom plugin type that allows modules such as Vertex AI Search Promoted Result to be created.
Adding information about the SearchResults custom plugin type.
TimoZura → created an issue.
Hi @sarwan_verma .
Thank you! Unfortunately, I could not use the patch. The text included for the hook_help is specific to the Profile module and does not apply to this module. There is also no use statement for the RouteMatchInterface argument.
I went ahead and forked the issue an added in the hook_help implementation through a MR.
Added documentation here: https://www.drupal.org/docs/extending-drupal/contributed-modules/contrib... →
Changing a heading title to reflect the configuration page.