if you don't have a
LocalLib.cfg (like you've just unziped a release) twiki's cgi scripts seem to run, evaluating and failing to find plugins etc.
surely its better to stop at the point where you know there is no configuration?
Index: bin/setlib.cfg
===================================================================
--- bin/setlib.cfg (revision 10630)
+++ bin/setlib.cfg (working copy)
@@ -23,6 +23,7 @@
use vars qw( $twikiLibPath @localPerlLibPath );
eval 'require "LocalLib.cfg"';
+die $@ if (defined($@)); #don't reveal to hackers what the problem is, but also don't continue blithly on
unless (( defined ($twikiLibPath) ) and (-e $twikiLibPath)) {
use Cwd qw( abs_path );
No way is this urgent. Normal at best.
The more I think about it, the lower it gets. Low.
CC
Changed from Waiting for feedback to New. Actionable report.
CC
done - SD
and undone again, seems to be way to agressive in hiding errors, making debugging a problem impossible. discard, TWiki stops earlier now anyway - SD