Let me know if you need me to provide a stack trace or anything else.
- 🇺🇸United States smustgrave
Since this could be a behavior change from some, probably will need a CR I would assume. Since we are denying something that was previously allowed.
- 🇺🇸United States smustgrave
Tested this manually following the steps and did notice the text would update.
Would note I did have to discard my changes in layout builder AFTER I applied the MR for the change to take hold.
- 🇧🇷Brazil thiagomoraesp
Hello everyone, the gist in the description didn't fixed the deprecated warning for me, @luke.leber logic also didn't worked (they execute but didn't changed anything in my database), so i adapted both to work together on a single logic that i want to share this change with you in this gist (working on 10.4.7):
https://gist.github.com/D41196829/1837b740e89f81c17277c072db6f3b1f
- 🇮🇳India libbna New Delhi, India
I followed the Scenario 1 steps to reproduce the issue and #81 is working fine.
Attached before and after screenshots.
- 🇮🇳India sd9121
I have updated the patch for the 11.x branch to include the recent changes and fixes. Please review and let me know if there’s anything that needs adjustment.
- @sd9121 opened merge request.
- 🇦🇺Australia acbramley
Extended the existing test coverage (since moved to LayoutBuilderBlocksTest)
Also replaced a few unnecessary HTTP requests with API and accessing the manage layout url directly.
- 🇦🇺Australia acbramley
Rebased the MR against 11.x. Still needs tests.
The previous issue added these in
LayoutBuilderTest::testLayoutBuilderChooseBlocksAlter - First commit to issue fork.
- 🇳🇿New Zealand danielveza Brisbane, AU
It would be good to get the 11.x MR up to date with these changes too, fixes should go there first :). Thanks!
