Congrats, will be reviewing over the next couple of weeks
That makes sense, thank you for answering my question. @axelm
The upgrade to Groups can be a tough one for sure. We had to upgrade the groups module to version 2 on another project because we kept getting errors when upgrading to Drupal Core 10.2.2.
Could you please let us know what version of Drupal core you all plan to have Opigno 3.2 ship with?
I sympathize with the struggles you all must be having, especially with the way the Groups module has changed.
Our client's security policy requires us to make the update to Drupal 10, which will require an update to Groups module because of other systems on the site .
From other projects, we know that the Groups module version being used in Opigno on the 3.1 version is no longer the recommended version to use going forward and that users should move to Groups version 2 if they are using Groups already, and using Groups 3 if there is a fresh install.
Can you please let us know what version of the Groups module the next version of Opigno will ship with?
sascher → created an issue.
We are seeing this issue also. We have a new install of the module on Drupal v 10.2.0
We have run into this same problem on the project I am working on right now.
The workaround we have is to delete the users records from the database with drush.
If I had user with and ID of 666, then I would run these commands since there is no way yet to remove them thought the UI
drush sql-query 'DELETE FROM opigno_learning_path_achievements WHERE uid= '666''
drush sql-query 'DELETE FROM learning_path_result WHERE user_id= '666''
drush sql-query 'DELETE FROM opigno_latest_group_activity WHERE uid= '666''
drush sql-query 'DELETE FROM user_lp_status WHERE uid= '666''
drush sql-query 'DELETE FROM user_module_status WHERE user_id= '666''
drush sql-query 'DELETE FROM opigno_module_badges WHERE uid= '666''
Hello,
Thanks for you work on this.
I am trying to test out this patch as we would like to have this working on our project as well.
When I try to patch the 1.1.4 version of ECA with the following code in our composer.json file It says unable to patch.
"drupal/eca": {
"https://www.drupal.org/project/eca/issues/3347247": "https://git.drupalcode.org/project/eca/-/merge_requests/319.diff"
}
Can you tell me if I am missing something small?
Thanks!
Thanks @Jurgenhass I see the condition in there now!
Thanks @Jurgenhass. I tried applying the patch with composer to 1.1.4 version and got some errors. I will report back if I figure this out .
"drupal/eca": {
"https://www.drupal.org/project/eca/issues/3352393": "https://git.drupalcode.org/project/eca/-/merge_requests/349.patch"
}
some of the errors I got upon running cache clear were
In YamlSymfony.php line 40:
Duplicate key "eca.execution.render_subscriber" detected at line 107 (nea
r " - { name: event_subscriber }").
In Parser.php line 347:
Duplicate key "eca.execution.render_subscriber" detected at line 107 (nea
r " - { name: event_subscriber }").
Hi thanks so much for this module.
I am confused by something though, I can’t find this condition when using the UI and I don’t see the code for list contains in the 1.14 version of the module
I see that docs were started here https://ecaguide.org/plugins/eca/base/conditions/eca_list_contains/
Am I missing something simple?
Thanks
I have reported the same issue here https://www.drupal.org/project/opigno_learning_path/issues/3372077 🐛 Can not load learning path after upgrading to 3.1 Active
I moved the issue here because the maintainer said it would be better reported here
Patch from #7 worked for me, thanks
That is an excellent suggestion. I was able to bypass Opigno's composer json but putting that in one in the top level of our project directory under the "require:" section