NOTE: If you are a developer, please use a private wiki based on foswiki/trunk on a daily base ...or use
trunk.foswiki.org to view this page for some minimal testing.
Use
Item9693 for docu changes for 1.2 and 2.0.
Item885: bin/manage/Web goes BOOM
| Priority: |
CurrentState: |
AppliesTo: |
Component: |
WaitingFor: |
| Normal |
Closed |
Engine |
|
|
try
http://foswiki.org/bin/manage/Sandbox
or
http://foswiki.org/bin/manage/NonExistentWebName
Foswiki detected an internal error - please check your Foswiki logs and webserver logs for more information.
Undefined subroutine &Foswiki::UI::Manage::_action_ called
--
WillNorris - 28 Jan 2009
The change at
Foswikirev:2202 fixes this problem, but some warnings about use of initialized variables are present and should be fixed as well. I don't have the time now to check/fix this
--
GilmarSantosJr - 28 Jan 2009
I still get a failure. The only way I could debug it was to run the manage script from the command line; it was falling over in a really obscure way.
Turns out that rendering an Oops page requires web and topic to be specified. By defaulting them in the oops function, the problem goes away.
Gilmar, I couldn't find any warnings about uninitialised vars, so dropping this to Normal and marking for your attention.
--
CrawfordCurrie - 30 Jan 2009
Hi Crawford,
Probably you're using
{WarningsAreErrors} setting, so the "Use of uninitialized variable" causes an error in
Foswiki.pm. The variables were
$web and
$topic, so your change finished the fix
--
GilmarSantosJr - 30 Jan 2009