Question

Hi,

I'm using the TWikiVMDebianStable version of Twiki (4.0.4 on Debian on VMware player). The setup plays nicely out of the box.

I tried to install or installed several plugins, such as ProjectPlannerPlugin or QuickCalendarPlugin.

The plugins that I tried to install show up correctly in Preview mode but do not show after saving. The InstalledPlugins does not seem to show the plugins that are not fully functional.

Some of the plugins need to run a .pl script, which states that it should only be run from the 'TWiki root folder' which I believe to be /home/httpd/twiki. The .pl scripts run OK from that folder; generate no error messages & the OK result shows in preview. I'm just not 100% sure that this is the correct folder.

Maybe it is a rights issue, but I see no instructions on that with the plugins. I am NOT a Linux person. As root, I ran chmod +x *.* in the /home/httpd/twiki/lib/TWiki/Plugins folder and that added some x rights to all the .pm files in that folder, but it does not seem to help.

Help really appreciated.

Regards Bart

Environment

http://twiki-vm/twiki/bin/view/TWiki/InstalledPlugins

Plugin	Errors
SpreadSheetPlugin	none
CommentPlugin	none
EditTablePlugin	none
InterwikiPlugin	none
PreferencesPlugin	none
SlideShowPlugin	none
SmiliesPlugin	none
TablePlugin	none
WysiwygPlugin	none

-- BartLouwagie - 27 Sep 2006

Answer

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.

This behaviour is due to the way the TWiki configuration in the virtual machine is done, using a perl accellerator (SpeedyCGI).

This caches current TWiki configuration at first load; to load a new configuration you have to do one of these:

• Reboot the virtual machine or
• Issue a killall speedy_backend as root or
• Issue a touch /home/httpd/twiki/bin/* as root

Each of these actions will load the new configuration, making the new configuration changes become active.

If you please you can disable SpeedyCGI while testing (at some performance loss), and perhaps enable it again later when your configuration is stable.

-- SteffenPoulsen - 28 Sep 2006

Thank you !

I updated some sections to refer to your answer.

Bart

-- BartLouwagie - 28 Sep 2006

Thanks

It would probably make sense to add a little script in /bin that would touch the binaries when retrieved, so the "reset" could be done from the browser.

I will think of a way to do this for the next release.

-- SteffenPoulsen - 28 Sep 2006