Loading...
 
Skip to main content

Themes


Application Menu broken using Blue/Green/Purplemetal skins with Tiki 1.10

I ran into a problem today after upgrading from 1.9.9 to 1.10.0b0 - the Application Menu completely collapsed to the Menu title box and would not expand regardless of whether the menu was configured to be expanded, collapsed, or fixed. I re-ran the upgrade four times and never got it to work.

It turns out that the *metal skins (Bluemetal, Greenmetal, Purpemetal) use a tiki-user_menu.tpl file in /tiki/templates/styles/(metal skin name)/ folder and there is something wrong with the file that breaks the menu. Changing the name of the file (I added .disabled extension) prevents if from compiling into the /tiki/templates.c folder and being used, and lets the menu work correctly. I won't pretend to know how to edit the file to fix it 'correctly', but if you like the Metal skins, this will let you use them with Tiki 1.10.0b0.

For the record, NothemeII crashed the wiki with an error in the stylesheet. The httpd log complains of an unexpected '.' on line 70. Of course this is likely not the problem, but that's what it reports. I had to juggle file names in the templates.c folder to get a page to load so I could change themes, but everything *seems* to be running fine... We'll see how it goes.

Les

There are sure to be problems trying to use older themes with Tiki 1.10. Those theme's files haven't been touched in a long time, while the core Tiki files have been changed.

Also, even if they don't cause errors, those themes don't impliment all the 1.10 features, such as the fullscreen view and ajax, so they should be updated to avoid having an only partially functioning Tiki 1.10.

-- Gary


Very good to know. Is there a listing of skins that are specifically for 1.10? I don't have any experience skinning Tiki, but I do have a bit of CSS experience, so I may work on updating them if I can get the pertinent info for the new features.

Thanks,
Les

With Tiki 1.10 still in development and not finalized, there aren't really any themes out yet that are specifically 1.10-ready, as far as I know. I'm working on updating the themes that I've done, but don't have them ready yet.

If a theme's only specific files are a stylesheet (and maybe background images), then updating for 1.10 is just a matter of adding the new selectors and styling them. But even this is more or less covered in terms of function if the admin option of using the transitional stylesheet is checked.

If a theme has its own template files, then there are bigger problems. The biggest potential showstopper is sidestepped by use of the admin option for permission syntax: the permission check syntax got revised for 1.10, but site admins can choose whether to use the 1.10 version or the earlier version, depending on what their theme templates use.

There are a lot of smaller details that won't stop the site from working (as far as I know) but might cause either semi-functionality of existing features or the nonappearance of new features, such as Ajax tabs. As far as I know, there's no list of changes and where they are and how to update on a file by file basis. I think basically the default 1.10 files should be used as much as possible, and if a theme has its own versions of files, then to be as up to date as possible, it would be best to start fresh with the 1.10 counterparts and modify them to produce the look of the old theme, if that's the goal. It's hard to bring the old theme templates up to date since if the person isn't familiar with what's unique to the 1.10 version, it'd be hard to retrofit things into the old files. You can see this page — 110_theme_upgrade_issuesQuestion — for some things I've come across, but it's pretty general. (Zukakakina.com just got a lot of files wiped by some vandalism, so things might not all be back in place yet.)

For my themes, I've used this approach of starting with new files and changing as needed to get the theme look and feel, rather than trying to add new code to the old files. This is also because I'm trying to improve the methods the themes used, and there's plenty of potential for improvement. 😉

-- Gary

Then that's how I'll approach the skin update, thanks for the tip.

On another note, I may have uncovered an issue with permissions, specifically when 'stacking' groups. Permissions do not seem to stack correctly, and certainly do not display correctly. Let me explain.

As a basic overview, I create 2-3 levels of permissions for each major feature (wiki, forum, blog...)
Basic Level would equate to someone who reads a newspaper.
Mid Level would be someone who would write a letter to the deitor of a paper (leave comments on blogs & articles)
Contributor Level access is for the people who will write the blogs, articles, and such.
-each level of access also has the permissions of the level below it, e.g.: a Wiki Contributor has Wiki User(can write comments) and Registered level access.

-The 'top level' access I'm working with right now is 'BSU Student' who's sole group membership is Student (so I can have several different Student groups who cannot necessarily access/edit other Student groups' work)
-The Student group belongs to the following group structure:
1. article readers
-a. Registered Users
2. blog readers
-a. Registered Users
3. forum user
-a. Registered Users
4. image gallery users
-a. Registered Users
5. wiki contributer
-a. wiki users
--1. Registered Users

There are two separate issues with permissions:
1. I have to set up two sets of permissions to access a Wiki Page
The Wiki tree and permissions:
--HomePage (default permissions)
----Students' Corner (Students, wiki edit; wiki users, view) - without adding Wiki User, a user who only belongs to the BSU Students does not have permission to view the page.
--Boise State University - (BSU Students, wiki edit; wiki users, view) same as above. On a weird note, the BSU Students cannot even view the site homepage or the wiki homepage even though it inherits permissions from groups that CAN view those pages.

2. In the Group Management pane, group membership does not display correctly:
A. BSU Students correctly displays the following memberships:
-Students
-article readers
-Registered
-blog readers
-forum user
-image gallery users
-wiki contributer
-wiki users
B. Students only shows the following memberships (remember that ALL of BSU Student's memberships are inherited directly from Students).
-article readers
-Registered
-blog readers

-forum user

-image gallery users

The lists are copied directly from the 'List of Existing Groups,' including the gaps, which should contain wiki contributor and wiki users.


If you'd like, I can set you up with a login for the site with the appropriate credentials to check out what's going on.

Thanks,
Les