🇺🇸United States @tzura

dmundra → credited timozura → .

timozura → created an issue.

timozura → created an issue.

Reviewed.

Reviewed

Reviewed.

samlerner → credited timozura → .

Changing a few headers.

timozura → created an issue.

Could use review. It updates some help text and groups the various filtering-related mechanisms together on the search page configuration form. (Configurable JavaScript Plugins, Exclusion List, Filter Expressions).

Adding links to the Developer Documentation where appropriate.

Adding more information/examples about custom Plugin types provided by vertex_ai_search module.

Adding information about new plugin types provided by the vertex_ai_search module.

Updating to reflect new configuration provided by the module.

More configuration options have been added to the vertex_ai_search module.  Updating documentation to reflect.

Adding a description of the page.

There is a link to a Google page in the text.  Updating the link to reflect a change of title on the Google Page.

Edited for a bit more brevity and more accurate information.

timozura → created an issue.

@christian-deloach ... Good catch. I'm closing this as a duplicate though because I noticed it in the course of addressing Issue 3525955 ✨ Modify pager operation based on total Active .

In the MR for that issue, I changed the fieldset label to 'Advanced Settings'.

Thank you!

timozura → created an issue.

_Error_: Maximum call stack size of 10436608 bytes (zend.max_allowed_stack_size - zend.reserved_stack_size) reached. Infinite recursion? in _Google\ApiCore\CredentialsWrapper->Google\ApiCore\{closure}()_ (line _244_ of _/var/www/html/vendor/google/gax/src/CredentialsWrapper.php_)

...this was the error we were seeing.

https://www.drupal.org/project/vertex_ai_search/issues/3525837 💬 Is gRPC a new dependency? Active

There is an issue with PHP8.3 and the gRPC extension. I ran into this in a new environment where the gRPC extension was installed.

If gRPC is supported, then that will be used first. If not, then it uses REST. We hadn't encountered this issue until working in an environment where the gRPC extension was actually installed. So we added the option.

Perhaps the REST option should be the default instead.

Reviewed with @samlerner.

timozura → created an issue.

timozura → made their first commit to this issue’s fork.

Tested by @dmundra and @npoku. Merged.

Tested on a fresh site and on an established site. Nice approach. Ran into no issues so I merged it.

timozura → created an issue.

timozura → created an issue.

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.

Updating a header style.

TimoZura → created an issue.

TimoZura → created an issue.