Is ActionTrackerPlugin supported by Foswiki?

Can anybody tell me what happened to the ActionTracker Plugin?

It doesn't appear in the repository, nor is it in the plugin list on the site.

Due to a system upgrade I have moved to FosWiki.

Congratulations, everything went smooth, but ... no Actiontrackerplugin

I will have to move back to Twiki if it's not supported on FosWiki anymore....

Answered partially myself:

It's in the works and the old one should work using the TwikiCompatibilityPlugin.

I wonder, why it doesn't appear on the extension list, though...

Answer

By default, configure only lists extensions uploaded to foswiki.org - and we're not yet up to date - many of us are doing work on our plugins before we upload them.

If you hit the 'EXPERT' mode button at the top of configure, you will then see (in the Extensions section) a configuration item (with documentation) to which you can add TWiki.org's Plugins - and thus ATP should be listed too.

If you use the documented value, configure will show you foswiki.org extensions in preference to same named twiki.org ones.

-- SvenDowideit - 13 Jan 2009

Thank you very much, Sven.

I do have a new problem, though with the permissions

(I am running the foswiki from the repository version on an ubuntu server). The configure script seems to try to move a script into the cgi-bin directory, which it is obviously not allowed. Configuration ends with a:

Error: Failed to move file 'ActionTrackerPlugin_installer' to /usr/lib/cgi-bin/ActionTrackerPlugin_installer: Permission denied

I guess it makes sense not to let anybody write into /usr/lib/cgi-bin. Correct? I guess this has to do with the way foswiki is installed in the debian package? Any simple way of changing this in the configuration (instead of just letting everybody write to /usr/lib/cgi-bin)?

Yogi, sorry for the delay, but due to other pressing constraints I haven't had time to release a new version of the ATP. It's on the stocks, waiting for launch when I have completed testing.

w.r.t permissions, the 'configure' based extensions installer has the known problem that it requires the webserver user to have write permission in the bin (and other) dirs. This is definitely not good practice, but no-one has been able to suggest another way for it to work.

-- CrawfordCurrie - 15 Jan 2009