Loading...
 
Skip to main content

New Themes

Forum List Topic List

Forums » New Themes » Twist Theme -> Disappearing Menu Modules
 
Thread actions

    • Twist Theme -> Disappearing Menu Modules

    Posted by Maxfield Stewart on Sat 12 of Jan, 2008 02:10 GMT-0000 posts: 17 United States

    This might just be a continuation of a problem I previously posted about. Mainly here's the deal (TikiWiki 1.10)

    For any user created menu I make in Twist, the menu does not appear in a module unless I save a menu option. Then it shows up and stays up, unless I change any permissions in the groups section, then the menu dissappears again.

    What's worse, is it ONLY shows up for users in the same group as the user who saved the option. I.E. shows up for all admins, but won't for say, registered users. However if I grant edit menu ability to registered users, then edit the menu and save a menu option, it'll show u p. But then when an admin logs in it won't show up.

    However if the theme is switched to another theme, the menu appears as it should. It's as if the Twist theme is very picky about menu settings. What is strange is the readme info says it is "strict" about headers but I wonder if it's strict about other things too?

    This only occurs in the Twist theme so far. I'm trying to go through the user-menu.tpl file but this is all new to me at the moment. Clearly the style sheet works for the menu (it shows up with a bit of cajooling above) but for whatever reason the twist theme seems to get something that tells it not to display the menu when group permissions are changed or the previously logged in group type doesn't log in (I tested this on different machines and browsers as well).

    Reads: 13729
    Posted by Maxfield Stewart on Sat 12 of Jan, 2008 02:51 GMT-0000 posts: 17 United States

    Workaround:

    Much like mnu_application_menu in TikiWiki 1.10 you have to remove the tiki-user_menu.tpl file for Twist. Located in:

    tiki_root/templates/styles/twist/tiki-user_menu.tpl

    Removing it (I suggesting renaming it) uses the default menu template which does not perform amazing disappearing acts. I need to know smarty templates more but I'd love a fix for this.

    Back to work for me!

    Posted by Gary Cunningham-Lee on Sat 12 of Jan, 2008 17:54 GMT-0000 posts: 254 Japan

    The challenge with themes that have their own template files is that the default files (and files they interact with one way or another) get modified from time to time as part of the core code, but the custom files don't unless the author or some other maintainer makes the effort. The Twist files haven't been touched for quite a few months, and there has been a lot of change in the core files, and even more taking into account the differences between 1.9 and 1.10 versions.

    I guess one approach to updating the custom files is to compare the 1.8 or whatever files that they were derived from to the current 1.10 files, and then see what customization was done to the 1.8 files to make the Twist versions and try to reimplement that in the 1.10 default versions. Or just go with the 1.10 files as a start and see how to make the change for Twist based on a kind of visual comparison (special icons in the menus, for example).

    I'm kind of in a pragmatic mode these days, so am tempted to forego most customization and just use the 1.10 files as much as possible, because they have a lot of changes from before and also because they are still in flux, so any customization for a theme might well break unless changes are kept in synch.

    -- Gary

    Posted by Maxfield Stewart on Sat 12 of Jan, 2008 21:01 GMT-0000 posts: 17 United States

    Yup. I'm deploying Tiki Wiki for my business intranet for a small game development company. I'm pretty early in the deploy, learning how to make the changes I know this wild and crazy group will ask for. Which always lean towards the visual side, not the functional.

    Futzing with stuff like this helps me get a feel for where I have to make changes. I know the default templates won't cut it with this group. So for certain folks I'm using the Tikipedia template (which works pretty well with 1.10 I must say) and for a lot of others I'm trying to center on something a little less "techie" looking. Believe it or not I have some users who are terrified of anything that actually "looks" like a wiki.

    Twist has a nice tight layout, one of the best in the set. I'm expirimenting with it and Fluid Index right, Kubrik for blogs, and Tikipedia for dev team areas. It's a real challenge ramping up.

    I'm taking notes on things that I'll have to work on, and making adjustments to Twist to work with 1.10 is on the list. If i get some effort into it, I'll submit the changes. For now, most of the adjustments have been to FCKEditor and css files to make things look/behave a little cleaner for my audience.

    As for why 1.10 over a stable 1.9? That's easy, 1.10 has significantly better FCKEditor integration than 1.9 and WYSIWYG was a "make or break" deal for several teams who think Wiki Code is too hard.