route content_lock.break_lock.XYZ not working? Wrong form_op?

I found the same problem with the module and after some debugging I identified the same line of code being at fault.

The $form_op is the lock that needs to be broken, so if this is called from the content admin page then it contains a "*", which means to "break all locks". This string makes no sense to the database query since we are trying to delete any operations that are called "*" for this entity.

I think this solution to detect for the presence of the "*" and ignore the condition works and should be merged. The patch also passes coding standards checks.

Does appear #3073565: Unable to release the lock on /admin/content/locked-content view → was marked fixed without a commit. Turned #2 to an MR.

Rebased

It'd be great to add an automated test for this. It's a condition so easy to break in the future.

Actually wonder if this could be covered in ✨ Option to lock all form operations together without the black listed ones Needs work ?

Wonder if still a bug actually. Following the steps but the lock appears to be deleted.