Closed (duplicate)
Project:
Quick Tabs
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
26 May 2008 at 15:47 UTC
Updated:
20 Nov 2009 at 12:22 UTC
Hi,
first of all I want to say thanks for this awesome and very useful module!
And, as there always is, there's something to make it even better! ;-) Currently the module always shows all the tabs and their associated blocks. It would be handy to have the tabs take the visibility settings of the block they show. So that a tab would show up only to authenticated users and on the front page because the block's visibility setting say so.
Thanks again for this module!
Comments
Comment #1
pasqualleI don't understand this request
1. the quicktabs block accepts block's visibility setting, so it does not show up every time
2. if you want to control tabpage visibility then this issue will be a duplicate of #272084: Tabpage visibility settings
Comment #2
giorgoskA think a simple scenario would be the following
insert the Login Block as part of a tab
the anonymous user sees it as it should
but after he/she logs in the login tab is still there
meanwhile the login block has no content
resulting in an TAB WITH EMPTY CONTENT
thus visibility settings and/or block visibility compliance
would be very much welcomed in this project
Comment #3
giorgoskHope the previous makes it more clear
Comment #4
pasqualleThe tab content can be empty from various reasons. If block is the tab content then the block visibility is only one of the reasons. The login block content has this condition:
This is not a visibility setting it is a hard coded condition in the login block.
To know that the tab content (like the login block) is empty then it is required to load that content first and check. This could work with non-ajax quicktabs but it is in contrast with ajax quicktabs, where you do not want to load anything unless you clicked on the tab. Hiding the tab after you clicked on it and found that it is empty, is not a nice functionality..
So this needs a serious rethink about how could this be achieved, without making it worse as it is..
Comment #5
pasqualleThe block visibility setting will not be considered as tabpage visibility, that does not make sense. Block visibility applies only when a block is displayed in theme region, should not be used for anything else..
Marking as duplicate of
#292150: Hide empty tabs
#272084: Tabpage visibility settings
Comment #6
rc2020 commentedReplying to #1, "the quicktabs block accepts block's visibility setting, so it does not show up every time"
This does not seem to be true in my case. On block visibility setting (a view, with block display), the block visibility setting does not seem to be respected.
My php code is
return FALSE;andWith block visibility set as such for each block in admin/build/block, they still show up in quicktabs. Is there something I am doing wrong? Is there a switch to respect block visibility settings that I missed?
I'm trying to have quicktabs respect visibility settings.
Thanks!
Comment #7
pasquallewith "quicktabs block" I mean the entire quicktab block, not the blocks inside quicktab
the block visibility setting is not used for blocks inside the quicktab.. that is by design..
Comment #8
rc2020 commentedIs there any way to only show the quicktab based on some type of access rule or snippet, in any capacity?
Please let me know.
Thanks!
Comment #9
pasquallethe only way for now is: #332895: render quicktab programatically
and I am planning to add #292150: Hide empty tabs, which might be useful in other cases..