Closed (fixed)
Project:
Quick Tabs
Version:
8.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
21 Apr 2023 at 08:36 UTC
Updated:
9 Jan 2024 at 09:59 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
viren18febs commentedChecking the issue!
Comment #3
viren18febs commentedHi Austin986,
I have checked the issue in Drupal 10.1 & followed the steps for reproduce. I have placed the Quick tab block with TwigTweak. but it's working for me as per expected. I have attached the images for reference, please review.
Comment #4
themasoodahmad commentedSame for me, it is not working. The second tab is not showing up there. My Drupal version is 10.1.4.
Comment #5
nmangold commentedI could not reproduce this issue either.
Comment #6
nmangold commentedComment #7
drupgirl commentedSame. To reproduce you have to have ajax enabled, which makes me think this is a duplicate of 2926105.
If views use ajax then this module doesn't work.
The path redirect is quicktabs/nojs/[view_name]/1, quicktabs/nojs/[view_name]/2, etc.
Comment #8
jonodunnett commentedSome problems for me (NOW RESOLVED: SEE UPDATE) after update to D10 when one of my tabs contains a Webform.
- If Quicktab setting is to use Ajax, then the tabs show up but the content does not load properly when clicked ("Loading content..." message forever.)
- If Quicktab setting is to NOT use Ajax, then none of the tabs show up (not even the tab names).
Functionality returns if I delete the Webform Quicktab.
UPDATE: The webform had some css added via the webform configuration page, and this was failing to load. The simple solution was to remove this css (which can be included in the theme css instead). All tabs now working both in Ajax and non-Ajax mode.
Comment #9
fgvlasov commentedAlso not showing new Blocks created from Quicktabs.
Drupal core 9.3.6
ebt_core 1.4.12
Only first Tabs (core)
Comment #10
nikolay shapovalov commentedIt would be great to have tests to reproduce this issue.
Comment #11
bsfajardo commentedI was facing the same issue. In my case, the problem seemed to be with
#theme_wrappersnot being rendered correctly. I replaced two of these wrappers with#prefixand#suffixin the render array, and the issue was fixed. Not sure yet what caused the original wrappers to stop working, or what is missing for them to work properly in Drupal 10.Patch attached.
Comment #12
themasoodahmad commentedThe was resolved while debugging the twig code, the wrapper div was open but not closed somewhere. If anyone face problem like this, please do check the opening and closing divs.