Hi.
I had exact the same behavior with an x-times updated version of
mediawiki. This could be solved by generating a fresh LocalSettings.php
file generated by the installer. This makes even more sense since there
have been some changes in declarations which won't make it in that file
when upgrading always. I did it like that:
- Install a fresh instance of current mediawiki somewhere in your web root.
- Take the generated/downloaded LocalSettings.php from the fresh install.
- Merge the individual settings of your old LocalSettings.php into the
fresh generated one using the new declaration style (i.e. for your
individual logo, allowed file types, rights, and so on).
- Put the merged file in your old updated installation.
- Run update.php
This will fix everything. No need for stylePath, extensionPath and all
those hacks.
When done and working throw away the installation and database you made
to generate your initial LocalSettings.php.
Hth,
Steffi
On 04.07.22 01:51, Jeffrey Walton wrote:
On Sun, Jul 3, 2022 at 6:57 PM Jeffrey T. Darlington
<[email protected]> wrote:
Each time I upgrade, I unzip the archive to a new directory and copy over the images and
extensions. So I've been using the "core" version of Vector for a while. That
said, commenting out the line with wfLoadSkin('Vector') still generates the following
error:
================
PHP Fatal error: Uncaught FatalError: $wgBaseDirectory must not be modified in
settings files! Use the MW_INSTALL_PATH environment variable to override the
installation root directory. in
/var/www/gpf/mediawiki-1.38.2/includes/Setup.php:237
Stack trace:
#0 /var/www/gpf/mediawiki-1.38.2/maintenance/doMaintenance.php(96):
require_once()
#1 /var/www/gpf/mediawiki-1.38.2/maintenance/update.php(264):
require_once('/var/www/gpf/me...')
#2 {main}
thrown in /var/www/gpf/mediawiki-1.38.2/includes/Setup.php on line 237
================
I'm not modifying $wgBaseDirectory anywhere in my LocalSettings.php, so I don't
see why it would be generating this error. (Note that all of the files in the
stack trace are MediaWiki internal files.)
One thing I noticed is, we did not have problems with Skins but you
did. (We had problems with Extensions).
Our LocalSettings.php has this, which may explain why we had no
problems with Skins:
$wgStylePath = "$wgScriptPath/skins";
$wgStyleDirectory = "$IP/skins";
According to the manual at
https://www.mediawiki.org/wiki/Manual:$wgStyleDirectory,
wgStyleDirectory is set to null in 1.38. This is new behavior for
1.38.
Maybe you need to set $wgStyleDirectory and that will fix the problems
with your skins.
(I still can't explain our problem with Extensions. Maybe I need to
set $wgExtensionDirectory. The manual says it is null in
1.38.Previously it was set to "$IP/extensions").
Jeff
_______________________________________________
MediaWiki-l mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://lists.wikimedia.org/postorius/lists/mediawiki-l.lists.wikimedia.org/
_______________________________________________
MediaWiki-l mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://lists.wikimedia.org/postorius/lists/mediawiki-l.lists.wikimedia.org/
