Loading...
 
Themes

Themes


Override display of left column on one wiki page or solve toggle pb

United States

Hi, is there a way to override general layout options on one wiki page? ex. not display the left column?

I would like to display the menus on the wiki page itself on my home page. The problem: there is a conflict when the same menu is twice on the page -once in the left column and once on the page, it only toggles in one place, random... same problem in admin menu options, whith the preview menu displayed. Is there a fix for that?

A solution on either issue would help me a lot.

Thanks for your help

Helene.

Japan

> Hi, is there a way to override general layout options on one wiki page? ex. not display the left column?

One way (and this is like riding the subway several stops away and back just to get across the street, but it would work wink) would be to make a new theme (i.e., CSS file and any necessary associated template files) that's identical to the one you are using, except for one thing: the left_column td selector is given the property "display: none". Then, using the Theme Manager, your home page is assigned this theme. The left column won't be displayed, for this page only.

I'm sure there is another way to do this, by modifying the templates to load a specific wiki page, but am not sure offhand how to do that.

> I would like to display the menus on the wiki page itself on my home page. The problem: there is a conflict when the same menu is twice on the page -once in the left column and once on the page, it only toggles in one place, random... same problem in admin menu options, whith the preview menu displayed. Is there a fix for that?

I can't help you on the toggling question, but I am wondering if it's really necessary to have the menu in the page itself if it is already in the left column. If there is a particular need for a menu in the body of the home page, another idea is to make it different in some way from the menu in the column — a custom menu. This would both avoid the information redundancy and solve the random toggling problem since the new menu wouldn't have the same menu id.

-- Gary

United States


Hi Chibaguy,

Indeed I wish to eliminate redundancy at all levels in the menus. And I would also like our home page - a different display of the menu- to be updated when our content admins change a menu. Right now, with a tiki html home page created to skip the left menu bar, and no way -from what I understand- to plugin a wiki menu in an html page, I update the homepage in hard code everytime the menus change, which is not what I strive for!

Curently I can edit css files but cannot save them as such. I am entitled though to save them under another name. So how do I make a new theme and what are the "necessary associated template files" I need to change in order to implement an effective solution? I have not dared touch the css yet.

Thanks in advance.
Helene

>
> I'm sure there is another way to do this, by modifying the templates to load a specific wiki page, but am not sure offhand how to do that.
>
> > I would like to display the menus on the wiki page itself on my home page. The problem: there is a conflict when the same menu is twice on the page -once in the left column and once on the page, it only toggles in one place, random... same problem in admin menu options, whith the preview menu displayed. Is there a fix for that?
>
> I can't help you on the toggling question, but I am wondering if it's really necessary to have the menu in the page itself if it is already in the left column. If there is a particular need for a menu in the body of the home page, another idea is to make it different in some way from the menu in the column — a custom menu. This would both avoid the information redundancy and solve the random toggling problem since the new menu wouldn't have the same menu id.
>
> — Gary

Japan

>
> Hi Chibaguy,
>
> Indeed I wish to eliminate redundancy at all levels in the menus. And I would also like our home page - a different display of the menu- to be updated when our content admins change a menu. Right now, with a tiki html home page created to skip the left menu bar, and no way -from what I understand- to plugin a wiki menu in an html page, I update the homepage in hard code everytime the menus change, which is not what I strive for!
>
> Curently I can edit css files but cannot save them as such. I am entitled though to save them under another name. So how do I make a new theme and what are the "necessary associated template files" I need to change in order to implement an effective solution? I have not dared touch the css yet.

If you are using a recent version of Tiki, you only need to make a new CSS file — you don't need to do anything with templates. With earlier Tiki versions I got error messages about missing template files when trying to make a new theme with a CSS file only, but I just did a test in which I edited a theme's CSS file and uploaded it as a new theme (essentially doing what you want to do), and the theme works fine.

To make a theme without a left column, find these lines in the original CSS file:

Copy to clipboard
TD#leftcolumn { ...: ...; ...: ...; }

and replace them with these:

Copy to clipboard
TD#leftcolumn { display: none; }

The formatting may vary in the theme you're working with, maybe with all on one line, but the point is to replace everything between the curly brackets with "display:none;". Then save the CSS file with a new name, like originalname_noleftcol.css. Do not use a hyphen in the name or the theme won't work. Underbars are OK, though.

Then use Theme Manager to apply the new theme to the specific wiki page. Theme Manager has to be activated first on the Admin Features page, if you haven't done so already.

-- Gary

Japan

> Then use Theme Manager to apply the new theme to the specific wiki page. Theme Manager has to be activated first on the Admin Features page, if you haven't done so already.

Sorry, that should be Theme Control (in English site, anyway), not Theme Manager.

-- Gary

United States

Hi Chibaguy, and thanks for your time on this. It works... but...

  1. Neither of the expandable menus, plugged in through modules on the wiki central page, "toggle" or expand when page is loaded for the first time. On the first reload some of the menus expand, and they all do once the page has been reloaded several times. I haven't investigated what happens after restart...
  2. It seems some general comfig/layout gets lost in the process:
    • Some type of super bold ">" bullet displayed with the h2 tag, not specified in the css -and I don't know where it is specified, does not appear in the source either- disappears... but let's say I can do without it...
    • Our custom "root" top bar, image + browser title as specified in the Admin General page is replaced by the default tikiwiki topbar "This is Tiki v1.9 DR (Developer Release) 4 (CVS) -Sirius- © 2002–2005 by the Tiki community 09/12/05 01:16 // debug". Now I know which version we are on biggrin.
      I remember now though that when requiring a style change on our declination of the tiki a couple of months ago, I was told that the "path to the general layout", or whatever this is called, was lost when creating a "local" duplicate css, so end of story.


Any clue on how this can be overcome for me to forward to the right guys if I can't correct it myself?

Thanks in advance.
Helene

Japan

> Hi Chibaguy, and thanks for your time on this. It works... but...
>
> #Neither of the expandable menus, plugged in through modules on the wiki central page, "toggle" or expand when page is loaded for the first time. On the first reload some of the menus expand, and they all do once the page has been reloaded several times. I haven't investigated what happens after restart...

Sorry but I don't know enough about how javascript behaves to help on this. You might try putting a phplayers menu in a module, since it uses different code, etc.

> +
> #It seems some general comfig/layout gets lost in the process:
> **Some type of super bold ">" bullet displayed with the h2 tag, not specified in the css -and I don't know where it is specified, does not appear in the source either- disappears... but let's say I can do without it...

Sounds like maybe an html tag is broken somehow, causing the angle bracket to be displayed. That's the sort of thing I waste too much time looking for, some days.

> **Our custom "root" top bar, image + browser title as specified in the Admin General page is replaced by the default tikiwiki topbar "This is Tiki v1.9 DR (Developer Release) 4 (CVS) -Sirius- © 2002–2005 by the Tiki community 09/12/05 01:16 // debug". Now I know which version we are on biggrin.

Well, it's good to get some benefit from this turn of events. wink Sorry, my instructions were for a case in which no custom templates are used with the original theme, sorry. In your case, you'll have to duplicate the templates directory (and contents) of the original theme (that is, the theme your site is configured to use). In other words, in the tiki_root/templates/styles directory there's a directory with the same name as your default theme, which I'll call "originalname". You need to make a tiki_root/templates/styles/originalname_noleftcol directory (or whatever you named your no-left-column theme) and put into it all of the files that are in the originalname directory, which will be the modified topbar file, maybe among others. Themes look for the template files to use first in a directory with their name within the templates/styles directory and then, if none are found, in the default templates directory.

> ++I remember now though that when requiring a style change on our declination of the tiki a couple of months ago, I was told that the "path to the general layout", or whatever this is called, was lost when creating a "local" duplicate css, so end of story.

That might have been due to how your local software modified file paths when saving the file. As far as the CSS file is concerned, it specifies the graphic file paths it needs for backgrounds, etc. But the template files are located by Tiki looking for same-named directories within the templates/styles directory.

>
> Any clue on how this can be overcome for me to forward to the right guys if I can't correct it myself?

Just duplicate the directory and files used for your main theme, as I described. Heh, I was hoping for a CSS-only, no-templates solution here, but it's not to be. smile

-- Gary

United States

Thanks chibaguy.

I was hoping for a CSS-only cry. I'll try and get this done. May take a while...


One trick is to use a module that contains the phplayer menu in the wiki page
(but only 1.10 accepts multiple phplayers menus)


Upcoming Events

1)  18 Apr 2024 14:00 GMT-0000
Tiki Roundtable Meeting
2)  16 May 2024 14:00 GMT-0000
Tiki Roundtable Meeting
3)  20 Jun 2024 14:00 GMT-0000
Tiki Roundtable Meeting
4)  18 Jul 2024 14:00 GMT-0000
Tiki Roundtable Meeting
5)  15 Aug 2024 14:00 GMT-0000
Tiki Roundtable Meeting
6)  19 Sep 2024 14:00 GMT-0000
Tiki Roundtable Meeting
7) 
Tiki birthday
8)  17 Oct 2024 14:00 GMT-0000
Tiki Roundtable Meeting
9)  21 Nov 2024 14:00 GMT-0000
Tiki Roundtable Meeting
10)  19 Dec 2024 14:00 GMT-0000
Tiki Roundtable Meeting