SID-01626: TWiki-5.1.3 - post upgrade issues

Status:	Answered	TWiki version:	5.1.3	Perl version:	v5.10.1
Category:	CategorySkin	Server OS:	Oracle Linux 5.8	Last update:	12 years ago

Hello,

I just installed 5.1.3 to migrate from:

TWiki version TWiki-4.2.4, Sat, 06 Dec 2008, build 17773, Plugin API version 1.2

to

TWiki version TWiki-5.1.3, Sun, 16 Dec 2012, build 24504, Plugin API version 1.4

to prepare for migration to a new system. The installation and upgrade (copying old wikis, users, preferences etc.) was mostly smooth. Thank you all!

Few issues:

1. I ran into TWikibug:Item7109 with configure. The available patch resolved it.

2. Upgrading / installing new plugins is giving " Insecure dependency' error as described in TWikibug:Item6965. Is that expected in 5.1.3? I know 5.1.2 lists it as an ignorable known issue. What I am seeing is that even after installing plugin upgrade, it keeps showing up as an old version on "Installed Plugins" and as upgradeable via configure.

3. With the upgrade I got the beautiful TopMenuSkin. However, the pulldown menus are not showing up either on hovering or clicking. If I hover, I see tool tip. If I click, the shown items is actioned. I don't get to see any pulldown menus. I tried latest versions of Chrome, Firefox, and IE. Still no pulldown menus. Do I need to do some setup before the TopMenuSkin can be used? I already have the following in my TWikiPreferences.

• Set SKIN = tagme, topmenu, pattern
• Set FIXEDTOPMENU = on

Thanks. Rahul

-- Rahul Pandey - 2013-01-20

Discussion and Answer

Regarding #3 above, one thing we noticed is that in the twTopMenuTab section of the Main.WebHome, I only have <ul >. Whereas the similar twTopMenuTab section on twiki.org has <ul style="visibility: hidden;">. Could this be causing the issue? I tried with a fresh installation of 5.1.3 on a new server, and I still see the same issue with TopMenuSkin.

-- Rahul Pandey - 2013-01-21

The problem with TopMenuSkin is resolved now. The fix was to enable {AllowInlineScript} in configure. I had disabled it during installation and configuration phase. Enabling it again, fixed the TopMenuSkin problem that I had reported.

-- Rahul Pandey - 2013-01-25

Thanks for reporting back Rahul. I updated the configure script to warn of the TopMenuSkin issue if the {AllowInlineScript} flag is turned off.

-- Peter Thoeny - 2013-01-26

If you answer a question - or someone answered one of your questions - please remember to edit the page and set the status to answered. The status selector is below the edit box.