Closed (fixed)
Project:
Responsive Theme Preview
Version:
2.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
29 Aug 2025 at 09:39 UTC
Updated:
7 Feb 2026 at 14:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
fagoComment #3
fagocommenting out template_preprocess_item_list() in responsive_preview_preprocess_item_list__responsive_preview() removes the exceptoin but makes the responsive-preview list appear always empty for me
Comment #4
sourabhsisodia_ commentedComment #5
sourabhsisodia_ commented@fago the issue did not reproduced , i tried the above mentioned steps
Comment #6
sourabhsisodia_ commentedComment #7
fagorunning into this again now that 11.3 is out. See #3564252: Warning Preprocess callback is not valid: "attributes" is an invalid render array key leads to broken pages for more background.
I see it fixed when the item pre-processing is not used any more. Not sure whether it's needed in 11.3 still, everything seems to work fine without the pre-processing.
Comment #9
fagoComment #10
fagohere is a patch file for composer-patches usage.
Comment #11
drubbThanks, this patch solved multiple problems for me:
- Bubbling Assertion errors
- Missing preview icon in Admin Toolbar
- Missing Tools icon in frontend theme
- Missing links from Admin Toolbar Tasks
Comment #12
bohus ulrychThank you for the patch #10, without it my site was broken for reasons described in #3564252
Tested with Drupal 11.3.1
Comment #13
johnatas commentedHello,
Like the previous comments, I encountered similar issues when upgrading to Drupal 11.3.x, and the fix resolves all my problems correctly — thank you.
However, neither patch #10 nor MR !31 applies cleanly to version 2.3.0 of the module.
I am attaching a patch that applies successfully and works as expected on my side.
Comment #15
volkerk commentedAdded code from #3562810: NodeForm and NodeTypeForm have moved namespace to fix tests.
Comment #16
chr.fritschLooks good to me
Comment #17
codebymikey commentedAttached a patch which applies against 2.3.0
Comment #18
volkerk commentedComment #20
rajab natshahThank you :) for this fix.
Hopping for a tag release.
Not sure if it is recommended to use with Drupal CMS ~2.0
Comment #21
johnatas commentedMaintainers, don't forget to credit people who helped resolve this issue.
Thanks,
Comment #22
finn lewisConfirmed the bug in Drupal 11.3 and the patch in #17 fixes it.
Any chance we could get a release?
Thanks so much to everyone for this :)
Comment #23
rajeshreeputraReleased 2.3.1!
Comment #24
finn lewisAmazing, thanks so much @rajeshreeputra!