Bugfix/legacy element namespace and bugs #18293
Merged
+8
−8
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
riasvdv
approved these changes
Jan 23, 2026
Contributor
riasvdv
left a comment
riasvdv
left a comment
There was a problem hiding this comment.
Ah damnit, thought I got all of those, thanks!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
The first commit replaces the old element namespaces with new ones in the twig files.
With the old namespaces, the wrong element type was set in the
ElementIndexesController::beforeAction(). This caused errors on e.g. entry index page. Trying to view entries in a section caused the “Move to section is only available for Entries” error, the “New entry” button was not loading when the “All entries” source was selected, etc.The second commit fixes an issue where it was not possible to create a new entry or edit an existing one due to an
Undefined property: stdClass::$siteIderror.The third commit fixes an issue where it was not possible to save a new nested entry due to
CraftCms\Cms\Element\Element::getEnabledForSite(): Return value must be of type ?bool, string returnederror.Related issues
n/a