Use Attribute instead of Annotation to define route. Add pimcore_admin_element_islocked #1014
+24
−19
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…the pimcore_admin_element_islocked route as GET
muratbinerbay
force-pushed
the
fix-is-locked-bug
branch
from
bee5912 to
5d31251
Compare
|
Had to call 
|
kingjia90
reviewed
Oct 8, 2025
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pimcore 12.2.1 with admin-ui-classic-bundle 2.2.0 fails to check if an element is locked because the route
pimcore_admin_element_islockedwas never defined in ElementController:As Symfony Annotation is deprecated the route definition for
lockElementActiondoes not workRelated to #724