Problem/Motivation
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
| Comment | File | Size | Author |
|---|---|---|---|
| #23 | classy-3461089-21.patch.txt | 7.85 KB | o_timoshchuk |
| #11 | upgrade_status.png | 8.16 KB | dileepkumargembali |
| #7 | classy-3461089-7.patch | 4.23 KB | eric-alexander schaefer |
| #5 | classy-3461089-5.patch | 682 bytes | alvarodemendoza |
Issue fork classy-3461089
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
silvi.addweb commentedHello,
I have tested MR !5 and it's applied successfully. I've also checked that into Drupal 11 and it's working as expected as well.
Comment #4
opiSame here, adding
https://git.drupalcode.org/project/classy/-/merge_requests/5.patchto my composer.json makes upgrade_status module happy ! And it works well with my theme.Comment #5
alvarodemendoza commentedAttaching the MR5 patch
Comment #6
ice70 commentedTried both patches just in case there was a difference:
https://www.drupal.org/project/classy/issues/3461089#comment-15720455
https://www.drupal.org/project/classy/issues/3461089#comment-15743743
but both gave the same result in upgrade_status 4.3.5: classy: 1263 warnings found.
They are all depreciation notices, nearly all of the first one in the list:
link-formatter-link-separate.html.twig 15 Since twig/twig 3.12: Twig Filter "spaceless" is deprecated. See https://drupal.org/node/3071078.
On php 8.3.11 & drupal 10.3.5
Comment #7
eric-alexander schaefer commentedAfter I upgraded to Drupal 10.3.6 all of the many "Getting node "filter" on a "Twig\Node\Expression\FilterExpression" class is deprecated" went away. Left were only the "spaceless" warnings. I tried to get rid of them though a combination of simply putting short passages onto one single line and in some cases I used "whitespace-control". After that all warnings were gone.
Please review the attached patch. I am not a twig expert and I might have screwed it up completely. Also, the last time I rolled a patch was probably more than a decade ago... :D
PHP 8.3.12
Drupal 10.3.6
Comment #8
eric-alexander schaefer commentedIs there anything I can do to move this forward?
Comment #9
miedward commentedTested successfully as a parent theme on 10.4.0
Comment #10
miedward commentedAt some point I did get some stack traces re: stable, so I did end up installing that theme and a patch for this issue (https://www.drupal.org/project/drupal/issues/3478628) which isn't strictly related to this issue but it might help out folks with old themes so I thought I'd mention it
Comment #11
dileepkumargembali commentedHi ,
I tested this theme in both Drupal10 and drupal11 its working as expected I am requesting you to please release the stable version for Drupal 11. upgrade status also showing its compatible for Drupal11.
Comment #12
abelpzlI test MR!5 on Drupal 11 with a custom theme that uses it as base theme. It works fine.
Upgrade status shows some errors to be fixed manually 'Since twig/twig 3.12: Twig Filter "spaceless" is deprecated. See https://drupal.org/node/3071078.' Patch #7 fixes this problem, but needs to be reviewed.
I move this issue to "Needs review"
Comment #13
marco.bpatch #7 works for me
Comment #15
sleitner commentedAdded patch #7 to MR!5 , please review. phpunit test fails because theme name in this issue is classy-3461089 and not classy
Comment #17
pcate commentedI applied MR #5 and after running the upgrade status module scan is showed the module as Drupal 11 compatible.
Comment #18
ikit-claw commentedI have also tested the patch could we get this merged?
Comment #19
jonasanne commentedtested and can cofirm it's ok.
Can we get a merge please?
Comment #20
steven jones commentedI applied the initial commit from MR!5 and that worked fine for my use-case on a simple Drupal 11 site.
Spaceless isn't gone in Drupal 11 afaik, it's merely deprecated, so it's probably optional if the maintainers want to commit that bit or not.
Comment #21
alexander tallqvist commentedTested MR!5 on a Drupal 10.3.14 site. Everything seems to be working fine.
Comment #22
alexander tallqvist commentedTested MR!5 on a Drupal 11.1.5 site with the same results - everything seems to be working.
Comment #23
o_timoshchuk commentedI made the patch file with the latest changes in the merge request
Comment #24
sleitner commented@bnjmnm, @davidhernandez, @lauriii : Please release a new tagged version which is Drupal 11 compatible
Comment #25
dark05 commentedHello,
I managed to build my Drupal project in Drupal 11.1.5 from my Drupal 10.4.5 version. My theme uses Classy as the base theme, but despite the patch, at each composer update, I get the error
Problem 1
- Root composer.json requires drupal/classy == 1.0.2.0 -> satisfiable by drupal/classy[1.0.2].
- drupal/classy 1.0.2 requires drupal/core ^9 || ^10 -> found drupal/core[9.0.0-alpha1, ..., 9.5.x-dev, 10.0.0-alpha1, ..., 10.5.x-dev] but these were not loaded, likely because it conflicts with another require.
Comment #26
sleitner commentedThis is normal behavior. The patch does not update metadata in composer or packigist, which composer update uses.
Comment #27
dark05 commentedAs a result, Classy will not be compatible with Drupal 11 until the patch is integrated into the module ?
Comment #28
sleitner commented@dark05 I think you have to take a look at https://github.com/mglaman/composer-drupal-lenient/
Comment #31
smustgrave commentedComment #32
alexander tallqvist commentedComment #33
opiThanks @smustgrave for the merges & release ! <3