Closed (won't fix)
Project:
Droopler
Version:
4.0.0-alpha3
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 Jun 2024 at 14:00 UTC
Updated:
20 Jan 2025 at 08:08 UTC
Jump to comment: Most recent
Comments
Comment #2
cilefen commentedCan you perform a
git bisectto find the regression commit?Comment #3
cilefen commentedThe release notes highlighted this: https://www.drupal.org/node/3440477
That’s certainly pertinent.
Is there custom code or contributed modules involved in reproducing the bug?
Comment #4
gauravvvv commentedComment #5
pingwin_cracow commentedI tried to update according to the given concepts and unfortunately the sticky header table does not work.
After updating Drupal to version 10.3.0, unfortunately the table headers are still static and the sticky application does not work.
Comment #6
cilefen commentedCould you explain what you tried?
Is this reproducible on a new Drupal install?
Comment #7
pingwin_cracow commentedI tried the solution https://www.drupal.org/node/3439580
but it produced no results.
I was hoping that the stable version 10.3.0 would solve this problem, but unfortunately it didn't.
Comment #8
cilefen commentedCan you perform a
git bisectto find the regression commit?Is this reproducible on a new Drupal install? https://simplytest.me is useful for testing.
Which theme is showing the bug?
Did you do the things in https://www.drupal.org/node/3440477? Explain exactly what you did.
This is the complete list of changes between those releases:
Comment #9
pingwin_cracow commentedI applied two fixes as suggested:
https://www.drupal.org/project/drupal/issues/3451738
https://www.drupal.org/node/3439580
Comment #10
cilefen commentedWhat fixes? Those changes are in 10.3.
Comment #11
pingwin_cracow commentedI applied these fixes in version 10.2.7 and they did not work. After updating to 10.3.0, I did not apply any corrections and the headers in the views block still do not work correctly.
I don't really know what's going on, because in my opinion it should work in 10.3.0, because the problem was reported earlier and from what I saw, it was apparently solved.
P.S.
For information, I will add that in views I have created a block that is to display data in the form of a table. Sticky option enabled. I have tried turning the cache option on and off several times. Unfortunately, the headers are still static.
All modules updated today and compatible with Drupal 10.3.0.
The console does not show me any errors in this topic.
I'm sad about this.
If you are able to help solve the problem that would be great.
Regards.
Comment #12
cilefen commentedIf you would answer the questions in comment #8 that would help toward resolving this bug.
Comment #13
pingwin_cracow commentedI only applied the fix mentioned in #8
https://www.drupal.org/node/3440477
I did not make any other corrections
Comment #14
cilefen commentedHere is what I did to try to reproduce this bug:
What other steps are needed to reproduce this bug?
Comment #15
cilefen commentedCan you explain exactly what you did with https://www.drupal.org/node/3440477? For example, which file did you edit? This information is necessary to understand this bug report rather than having an interview in comments.
Comment #16
pingwin_cracow commentedThe fix https://www.drupal.org/node/3440477 is already included in version 10.3.0 - so I didn't add anything.
I tested on https://simplytest.me (Umami) with an array both in the form of a block and a page - everything works. Unfortunately not for me.
Comment #17
pingwin_cracow commentedI see now where the problem is.
1 - Clean installation of Drupal 10.3.0 + devel (I generated 50 nodes) - the table with the sticky header works correctly
2 - I installed the new Droopler 4.0.0-alpha2 profile and the generated subtheme.
3 - default Claro skin - everything works fine
4 - default subtheme skin - headers are static
5 - my subtheme does not inject the sticky-header class, hence the static header when a theme other than Claro is set.
Is there an easy way to tweak the subtheme to make this work?
If not, I suggest closing the topic and contacting the Droopler designers on how to correct it.
Thank you very much for your help so far and valuable comments on what and how to check.
Comment #18
cilefen commentedI think they would have to implement https://www.drupal.org/node/3440477.
Comment #19
cilefen commentedComment #20
grzegorz.bartman commentedVersion 4.x will be no longer developed. I'm closing this issue.