mattea.turnbull → created an issue.
I'm currently testing content_lock module as an alternative to using the conflict module.
thank you Joseph I'm going to try out the scheduled transitions module as an alternative to this one which is not being maintained. (also for a multiingual site)
thank you this change fixes my issue.
With the patch I had been getting constant, 'you have a conflict' statements and stuff not saving in drupal 10.01. I have uninstalled conflict and that resolved those issues (previously in drupal 9.5 I never saw that dialog or had issues).
I also had to uninstall autosave_form (unrelated to this but it seemed to break in drupal 10.0.1 with multilingual site).
I am having issues where after I save French (my secondary language) it takes up to 5 minutes to display the saved changes onto the front end of the site (if you have any clue what updated with drupal 10 that would cause that?)
Mattea
You can switch back to 1 and use the following patch (updates the info file) .
Maybe someone can take over as maintainer and fix the 2.0 branch.
I found this in the merge requests, uploading here for other users.
Yes they forgot to include all of the 'non updated' files in the 2.0 version. I am going to have to apply a patch to the 1.0 version, I'll see if I can post it here after I get it working.
What does this module do and what are the consequences of uninstalling it. This was a major high stress event when this broke and I'd like to evaluate if I should drop it vs applying the patch.
Thank you so much to the OP for creating this issue report I broke my site a month ago and could not figure out which update it was.
For anyone with this issue, until their is a patch, use the alpha2 version by using
composer require drupal/conflict:2.0.0-alpha2