[development] whats the best way to have tabbed panes in drupal 6.x and 7.x

Dave Reid dave at davereid.net
Thu Dec 23 15:47:25 UTC 2010


This is now the third time you've posted this to both the development and
support lists. Please stop until you receive a reply.

Dave Reid
dave at davereid.net


On Thu, Dec 23, 2010 at 4:44 AM, Kamal Palei <kamal.palei.1975 at gmail.com>wrote:

> Hi All
> I have very limited knowledge on Drupal.
> I have installed Drupal 6.x, I have made the front page.
>
> Once user logs in, it lands in my login destination panel page (configured
> usning login destination module).
> I want in my login destination page, I should have around 3 tabbed panes.
>
> I downloaded quicktabs module, using quicktabs module created a block
> (having 3 tabs).
> Added the block to login destination panel page. I am able to see the
> tabbed panes as expected.
>
> Now please clarify
> ---------------------------------------------
> 1. Is this the preferred way to have tabbed panes in Drupal 6.x ?
>
> Here I face a minor problem. I am using CTI-Flex theme (a zen sub-theme), I
> have configured different colors for header, footer, background etc (I have
> installed color picker module).
> The login destination page (that has tabs), looks bit odd, it does not have
> the configured colors for header, footer and background. So my front page
> headr/footer/background color, login destination page
> headr/footer/background color are entirely different. Any idea what needs to
> be done.
>
> 2. What is the preferred way to have tabbed panes in Drupal 7.x, as my plan
> is there to upgrade to Drupal 7.x
>
> 3. Will quicktabs work with Drupal 7.x
>
> Regards
> Kamal
>
> On Thu, Dec 23, 2010 at 9:51 AM, Marty Landman <
> mlandman at face2interface.com> wrote:
>
>> Yeah I was afraid of that. Wish there was something like overriding
>> the tpl.php files but nooo. And alas I didn't write the site to begin
>> with so too late for doing things right to start with.
>>
>> Marty
>>
>> At 08:44 PM 12/22/2010, Brian Choc wrote:
>> >You could use 'diff' or something similar to find out what's changed
>> >and put just those lines of CSS in a file in your theme
>> >folder.  Generally, I find the best way to avoid this problem is not
>> >to get into it in the first place by keeping the custom CSS in the
>> >theme folder to begin with.  :)
>> >
>> >Brian
>> >
>> >On Wed, Dec 22, 2010 at 5:52 PM, Marty Landman
>> ><<mailto:mlandman at face2interface.com>mlandman at face2interface.com> wrote:
>> >I've upgraded a D5 website for a client and the CSS files for
>> >nice_menus had been customized within the nice_menus module's
>> >directory, which obviously got overwritten by my upgrade.
>> >
>> >Which I understand is why this wasn't the right way to do things. I'm
>> >sure that copying the old css files fixes the problems, because I
>> >did. Want to do things according to best practice. I could just take
>> >those entire css file contents and append them to the style.css file
>> >for the theme. That'd work I think, but is there a better way, w/o
>> >actually picking all the lines apart to see what's needed?
>> >
>> >Marty
>> >
>> >--
>> >[ Drupal support list | <http://lists.drupal.org/>
>> http://lists.drupal.org/ ]
>> >
>> >
>> >
>> >
>> >--
>> >[ Drupal support list | http://lists.drupal.org/ ]
>>
>> --
>> [ Drupal support list | http://lists.drupal.org/ ]
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20101223/a72e139e/attachment.html 


More information about the development mailing list