Closed (outdated)
Project:
Quick Tabs
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
18 Jun 2008 at 16:55 UTC
Updated:
12 Dec 2024 at 16:52 UTC
Jump to comment: Most recent
Comments
Comment #1
katbailey commentedHmm, I'm not sure what you mean. You mean if you had a block as a tab within a QT block that tab would only show up according to that block's visibility settings?
Comment #2
pasqualleI think you mean tabpage visibility
Comment #3
pasqualleMoving new features to 3.x version
Comment #4
Anonymous (not verified) commentedHi,
I'm not sure wether this is the right subject, but I think rapsli thinks of this:
QuickTabs should provide an option to recognize the visibility setting of an used block. For example, if you define a specific block like "who's online" to be visible only on the front page, this setting will be actually ignored by QuickTabs, if you use this block as part of QuickTab.
I hope this helps
Comment #5
Skirr commentedAlso visibility of some blocks depends on roles. And if this block is in QT, than some roles see just a tab without a block.
Comment #6
infojunkie+1
Comment #7
1kenthomas commentedAny progress? It's problematic to have blocks visible via QT, which are otherwise violating their visibility settings.
Comment #8
jukka792 commentedAny progress?
Currently, a block which is used in the quick tabs is respecting only the user role settings, but not the URL visibility settings.
This change should be done probably in the "QuickBlockContent.inc" -file ? Actually there is already similar function related to user role "accessBlock" but not related to block url settings.
Comment #9
smustgrave commentedWith D7 EOL approaching in a month I'm starting to triage the D7 side of quicktabs queue.
If still an issue or needed for 4.0.x (latest branch) feel free to reopen