Closed (fixed)
Project:
Content locking (anti-concurrent editing)
Version:
8.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
31 Jul 2019 at 16:40 UTC
Updated:
9 Oct 2024 at 13:19 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
Keith Caulkins commentedNevermind, do not use this patch
Comment #3
Keith Caulkins commentedThis patch should do the trick on 8.x-1.x-dev
Comment #4
Keith Caulkins commentedComment #5
Keith Caulkins commentedComment #7
Punk_UnDeaDi think we need fix
because all other inner function used langcode
Comment #8
Punk_UnDeaDComment #9
spadxiii commentedLast patch seems to do the trick, in the correct location.
Comment #10
chr.fritschSince tests are failing, this can not be considered as done.
Comment #11
smustgrave commentedThe change makes sense, but I'm not able to replicate the error. Are there additional steps needed?
Comment #15
astonvictor commentedthanks for the report.
I was able to reproduce it:
1. Enable content_lock 8.x-2.x, conflict 3.0.0.
2. Enable the 'Lock only on entity translation level.' config for nodes on the /admin/config/content/content_lock page.
3. Execute the 'Break lock node' action on the /admin/content page.
as a result, I had
Error: Object of class Drupal\Core\Language\Language could not be converted to string in PDOStatement->execute()error.Comment #16
astonvictor commented