Topic: Error in MediaWiki with Apache 2.2.X and PHP 5.1.X

[lektu]

Hi.

I've got a MediaWiki setup based on the following configuration:

[James Blond]

Normaly it should work like in 2.0.x . I had programmed something in PHP that is like that URL. On my server it works (2.2.x and 2.0.x)

Maybe you used mod_rewrite in 2.0.x ?

There is something you can try. If you installed the 2.2.x in the same directority as the 2.0.x make a backup from the 2.2.x httpd.conf and use the old one from 2.0.x (if nessary change the pathes in the old httpd.conf)

Maybe you need to comment out some include files in the httpd.conf The configs had changed a bit. There are some file in the conf/extra folder now.

[lektu]

I'm not using mod_rewrite. I use a few aliases, but I don't think that's the problem.

I can try to compare the old httpd.conf file with the 2.2.0 one (though the horrible breaking of httpd.conf into extra/* makes it a bit more difficult), but I don't think it is a setup issue. As I've said, people with similar setups on Apache 2.2.0 running on GNU/Linux do not experience the problem.

[lektu]

I've been reading an old (c. 2003) thread on the Apache developer's list that talks about this very problem.

The APR lib (on Windows) thinks that colon is not valid in a filename, which is correct. However, the module generating the path should inform Apache that it takes care of the path and that it shouldn't need to be mapped to the filesystem.

I've done the following tests ("n/t" meaning "not tested"):

[James Blond]

[lektu]

James, does "works" in your test results matrix mean that MediaWiki works, or that you don't get the 20024 error from Apache about invalid characters when accessing Special pages?

If the latter, could you please post the setup of Apache 2.2.X you used on the tests?

Thanks,
Juanma

[James Blond]

I did not use an installer. I downloaded it and installed it manually.
------
edit:
Now I got the same error. But the wiki runs. I think you can ignore the error. The error is caused by the url, cause it contains the dobblepoint :
Apache knows that no file can have this name. But that is for the Database.
I think, but haven't testet yet, with mod_rewrite it should work without any error.

the new apache does not work with namespaces

[lektu]

Yes, I know that I the wiki runs. However, this shouldn't happen. There's no point in Apache detecting that it cannot map the path to the filesystem; it should be informed that the path is being processed elsewhere.

And yes, I can ignore it, but I would rather not. I run that Apache on a USB stick, and I don't want unnecessary writes, so I've set it up to log only the most critical errors. Accessing Special pages in MediaWiki is hardly critical

All in all, the thing didn't happen in Apache 2.0 and doesn't happen on non-Windows environments, so it is a bug somewhere.

[MikeSchinkel]

I'm having this bug on my Windows machine that I've set up for Mediawiki development. As it is, I'm dead in the water.

Am I going to have to revert to using IIS because Apache 2.2 can't work with PHP and Mediawiki? This is embarassing for Apache.

[tdonovan]

You are having this same bug (in Spanish)?

[MikeSchinkel]

[tdonovan]

Those are MediaWiki-generated URLs - not mine. Portada is "Main Page" in Spanish, not a topic.
That is also why the original poster's incorrect URL was /wiki/Especial:SpecialPages rather than /wiki/Special:SpecialPages.

Like the original poster, lektu, I was not using mod_rewrite. I used the default MediaWiki configuration to test - not the "better ideas from welldesignedurls.org" config. The instructions do not appear to be appropriate to WikiMedia 1.11.0. There is no reference to $wgArticlePath in LocalSettings.php for version 1.11.0.

re:"Am I going to have to revert to using IIS" - That would be my recommendation.

-tom-

[MikeSchinkel]