See report in
TWiki:Support/ConfigurePageNextButtonSubmitIsnotWo
:
I have installed new twiki Release 4.1.0. when i am running bin/configure it is opening the page and clicking Next button , it is not working,(the submission is not happening)
in the server log it showing the error message like this
"Subroutine TWiki::Configure::Checker::tmpfile redefined at /usr/lib/perl5/5.8/Exporter.pm line 65.\n
at /usr/lib/perl5/5.8/cygwin/POSIX.pm line 19\n
Subroutine TWiki::Configure::Checker::tmpnam redefined at /usr/lib/perl5/5.8/Exporter.pm line 65.\n
at /usr/lib/perl5/5.8/cygwin/POSIX.pm line 19\n"
I am having exactly the same problem. I have a working 4.0.5 installation. I renamed the TWiki directory and did a clean install of TWiki_4.1.0 into a new twiki directory. I get no response when I click on Next in the Configuration page with IE7. With Firefox I get an error message stating, "Firefox doesn't know how to open this address, because the protocol (c) isn't accociated with any program." I get the exact same error message as Prathap in the server log.
I use the same version of Apache, running on Windows XP. One difference is that I use CYGWIN and the version of Perl that comes with it, which is 5.8.7.
--
PTh
If would be nice if the reporter would run configure and save the html page and upload it so we can see what is missing
--
TWiki:Main.KennethLavrsen
- 29 Jan 2007
That message "the protocol (c) isn't..." suggests strongly that there is an issue with a path somewhere; for example, c:/ instead of c:\, or something like that. If a string like this: c:/windows is set as the default URL host, for example, I might expect to see an error like this.
--
TWiki:Main.CrawfordCurrie
- 29 Jan 2007
I asked the two reporters to send the html output of the configure screen. What is puzzling is the the form action seems to be a hard coded
<form method="post" action="configure" enctype="multipart/form-data" name="update">
, so where does a protocol other than http come into play?
--
TWiki:Main.PeterThoeny
- 30 Jan 2007
I got the html file from one of the reporters. It has this form tag:
<FORM name=update action=d:\twiki\bin\CONFIG~2 method=post
encType=multipart/form-data>
The action is
d:\twiki\bin\CONFIG~2
instead of
configure
.
To debug, I asked the reporter to replace line 524 ff of configure:
print CGI::start_form({ name=>'update',
action=>$scriptName,
method=>"post" });
with this:
print "<form name='update' action='$scriptName' method='post'>";
Why so much reliance on the cgi module? I find it much safer to generate XHTML code directly.
--
TWiki:Main.PeterThoeny
- 30 Jan 2007
Reply from reporter:
I have replaced the line 524 as you suggested but still it is not
working.
Finally I have replaced the line 147
my $scriptName = pop(@script
); with my $scriptName='Configure'; then it
is working even without changing the line 524.
Let me know is it good approach or not.
This looks like a good solution to me. No need for full path name, just the name of the tool is fine, so it can be hard-coded.
--
TWiki:Main.PeterThoeny
- 31 Jan 2007
I fixed it by filtering out the path from the script name. This is safer (such as perserving case).
Fix:
pop(@root);
my @script = File::Spec->splitdir($0);
my $scriptName = pop(@script);
+$scriptName =~ s/.*[\/\\]//; # Fix for Item3511, on Win XP
# Try to load the LocalLib.cfg optional overload
Waiting for reporter to verify before closing this.
--
TWiki:Main.PeterThoeny
- 31 Jan 2007
Marking you as working on it, so we know.
--
CC
Closing this item, I got the confirmation that this fixes the issue.
--
PTh
Thanks for the fix. Already merged to Patch04x01.
KJL