After upgrading from Scout 10.11.4 to 10.11.6 I started having issues with Algolia.
Cannot use object of type Algolia\AlgoliaSearch\Config\SearchConfig as array
I believe the issue is due to bugs introduced in #872 which added support for Algolia v4, but also broke support for Algolia v3. #881 has also been opened as other people have run into the same issue.
When I first saw the error I thought it was because I still had Algolia v3, so I bumped straight to v4 and then got another error.
Undefined array key "batch_size"
I've tested these fixes locally using both Algolia v3 and v4 and my search results are working again where previously they were not.
It appears the PR made mistakes:
It attempted to access config keys directly when previously the config helper was used,
It attempted to give the an array of configuration to the v3 search config object, when previously the id/secret were provided as separate arguments,
It confused local variables $config (the Laravel configuration array) and $configuration (the Algolia search config object)
brocard
commented
1 week ago
After upgrading from Scout 10.11.4 to 10.11.6 I started having issues with Algolia.
I believe the issue is due to bugs introduced in #872 which added support for Algolia v4, but also broke support for Algolia v3. #881 has also been opened as other people have run into the same issue.
When I first saw the error I thought it was because I still had Algolia v3, so I bumped straight to v4 and then got another error.
I've tested these fixes locally using both Algolia v3 and v4 and my search results are working again where previously they were not.
It appears the PR made mistakes:
confighelper was used,id/secretwere provided as separate arguments,$config(the Laravel configuration array) and$configuration(the Algolia search config object)