mediawiki install fails..

guthrie's picture

Forums: 

I installed mediawiki in the standard apt-get manner, but it fails.

I had a working previous install, but it stopped working, so I removed and re-installed.

I now get an error on web access: 403 forbidden
You don't have permission to access /mediawiki/ on this server.

and the apache2 logs show:
Directory index forbidden by Options directive: /var/lib/mediawiki1.7/

I see several complaints about this same situation and error from 3-4 years ago, and a PHP version incompatibility at that time.

Any suggestions what may have broken - and what to do?

Re: mediawiki install fails..

guthrie's picture

I noticed that although I removed both mediawiki, and mediawiki1.7, after a re-install of mediawiki, both are still there - is there some version confusion?

Re: mediawiki install fails..

IntnsRed's picture

I doubt it's confusion. Though I haven't/don't use mediawiki, in the case of 2 different versions of Debian packages it's typical that they'll either "conflict" so you cannot install both, or they'll reside in different subdirectories and/or with different filenames so that you can install both. This is due to Debian policy. The package maintainer probably didn't want to "force" the users of the older mediawiki to upgrade immediately and wanted to give users some time to migrate, and thus didn't want to have the two packages conflict.

Re: mediawiki install fails..

guthrie's picture

I had done a "remove" on both, and the newer one looks like a shell over the old one (it lacks most setup files, which reside in the old directories.)

Re: mediawiki install fails..

guthrie's picture

I had to do a manual:
ln -s /var/lib/mediawiki /var/www/mediawiki
and it then all worked.
Why the installer did not do this I do not know.

Re: mediawiki install fails..

guthrie's picture

HM,
I needed to do :
ls -s /var/lib/mediawiki /var/www/mediawiki

Why the install script did not do this I do not know.

Now fighting with MySql logins and permissions! Smile

Re: mediawiki install fails..

IntnsRed's picture

This is actually semi-common in *.deb-packaged web apps; there's usually a step or two you have to manually do after an install. I believe the basic mindset of this is Debian's core concept of security, that a package should not open security holes or potential security holes. So the packager forces you to open the hole (even if it's a basic feature of the package).

You probably should file a bug report about this. The package maintainer could have overlooked this, and if it was planned this way, he'll just close your bug.