@mrdalesmith https://www.drupal.org/project/ai_agents/issues/3499719 🐛 Use Interfaces instead of Class names in AgentHelper::construct Active is for the 1.0x.dev version. Doesn't look like the code made it into the 1.1-dev version?
@mrdalesmith agreed, that other issue addresses this. Do I mark this as Closed (duplicate) or does someone else do it?
@mrdalesmith Nice one, the changes in the MR resolves the issue for me.
tim corkerton → created an issue.
I get the same error when installing the 1.1 dev version. In order to progress I needed to
1. uninstall the dev version
2. composer remove to completely remove the agent module (just in case).
3. install the 1.0 version and enable
4. composer require the 1.1 dev version.
5. drush cr
Bingo it works !
Nice, Naive RAG here we come.
We had the same experience. We ended up abandoning Opigno altogether and rewriting our own LMS using the latest groups module ourselves. It's not that hard if you break down what is required for a minimal delivery of courses without the bloat. This did however cost us considerable extra unpaid effort since there was no viable upgrade path and we were committed to a security upgrade with our existing client. I still love Drupal after over 20 years working in it. Personally I don't think I'll ever go near another Drupal ready made distribution again.
@sanderjp I'd like to get rid f it but at the moment I suppress it in crontab using
drush --uri=sitename -q cron | ack -v '^({| "command":"buildAll"})$'
Nice, this solves my issue. Thanks
@scott_euser I can confirm that I am seeing the same kind of random behavior when trying to ai search view using exposed taxonomy terms.
I have added the taxonomy into the search api field list and set "Filterable attributes" as the Indexing option.
This issue however is not confined just to Milvus/Zilliz. I have both a Zilliz account and also a Pinecone account. I am seeing identical behavior using Pinecone. it feel like it is an issue with the search ai module. This issue might be better moved to another thread or at least duplicated in the Pinecone provider.
Scott, I have just watched your video where you discuss the workaround suggested above. https://youtu.be/WZEh4JOGhhM?t=5989 (Great video by the way!) Can you confirm how this approach works? Does it simply prepend results from the ai search to the results of a solr search. If so I don't think that really solves my use case. Any suggestions on how we can help fix this? Can you point to where the exposed filters are handled in the code base?
tim corkerton → created an issue.
I have just run a security test and see that this is still an issue with the php folder within sites default files.
i.e. drwxrwxrwx 3 apache apache 18 Jan 4 10:47 php
Can someone summarise if this is something to worry about? Is there a fix without patching core?
Thanks
I can confirm that I am experiencing the same issue as 1 above but not 2.
Has anyone ever managed to import multiple images on each variation?
I have the same after search_api_solr update too. Is it actually a problem?
Search api solr still appears to function ok
I have Better Exposed Filters 6.0.5 and Views exposed form layout 8.x-3.1
I have tried these two patches
https://www.drupal.org/project/vefl/issues/3161777
🐛
Compability issue with BEF 8.x-5.0 and BEF 6.0.3
RTBC
https://www.drupal.org/project/vefl/issues/3385119
🐛
Compability issue with BEF 6.0.3
Needs review
with no success
I have this error when module is unpatched:
ArgumentCountError: Too few arguments to function Drupal\better_exposed_filters\Plugin\views\exposed_form\BetterExposedFilters::__construct(), 6 passed in /var/www/web/modules/contrib/vefl/modules/vefl_bef/src/Plugin/views/exposed_form/VeflBef.php on line 78 and exactly 8 expected in Drupal\better_exposed_filters\Plugin\views\exposed_form\BetterExposedFilters->__construct() (line 84 of modules/contrib/better_exposed_filters/src/Plugin/views/exposed_form/BetterExposedFilters.php).
Tim Corkerton → created an issue.
Can you please give us a realistic date as to when this will happen?
We are desperate to know an actual date for this as it is holding up our development.
One thing that would help is if you could say if the theme will still be based on Bootstrap 4 or will you be upgrading to Bootstrap 5?
We are seeing exactly the same thing. It doesn't seem to happen to all trainings or all users and there are no errors in the drupal log of the server log. I'll try and provide more information when I can
Tim Corkerton → created an issue.
Hi @axelm that's great to hear, thanks for the update
Tim Corkerton → created an issue.
My client is asking for advice on the timings for Opigno's move to Drupal 10. Any updates on this?
Thanks.
Tim Corkerton → created an issue.
Thank you. I can confirm this works well with PHP7.4
I am on PHP7.4 Obviously I'd like the latest version but I am encountering this issue.
What is the recommended approach given that upgrading to PHP8 is not an option right now?
+1