[MediaWiki-l] Re: Unable to upgrade to 1.38.x from 1.37.x

2022-07-04 Thread Jonathan MW
> On 4 Jul 2022, at 18:06, Jeffrey Walton wrote: > > It would be helpful if Mediawiki put a new LocalSettings.php in the > tarball so we can see what a modern one looks like. I agree with this. A couple of years ago I ran into the same (or at least a very similar) problem:

[MediaWiki-l] Re: Unable to upgrade to 1.38.x from 1.37.x

2022-07-04 Thread Jeffrey Walton
On Mon, Jul 4, 2022 at 12:45 PM Jeffrey T. Darlington wrote: > > ... > Most often when I get bit by a MediaWiki issue, it's situations like this, > where some ancient setting installed 14 years ago falls out of scope. It's > not exactly reasonable to ask users to go digging through 21 major(?)

[MediaWiki-l] Re: Unable to upgrade to 1.38.x from 1.37.x

2022-07-04 Thread Jeffrey T. Darlington
No. Once I commented that out, the update script ran successfully. My wiki is now at 1.38.2. I will look into trying to generate a new LocalSettings.php file during the next upgrade, if I can remember to. That said, I run a smallish site and I'm a one-man shop, juggling several third-party

[MediaWiki-l] Re: Unable to upgrade to 1.38.x from 1.37.x

2022-07-04 Thread Benjamin Lees
Very good catch. That line was added by the installer before a rework in MediaWiki 1.17 (2011). It has been causing DefaultSettings.php to be loaded twice since then, but that was harmless until 1.38. This explains why this problem didn't emerge before release, and why using a new

[MediaWiki-l] Re: Unable to upgrade to 1.38.x from 1.37.x

2022-07-04 Thread Jeffrey T. Darlington
It never gets to this point. The error is apparently thrown before this. Mind you, this is only if I keep this line in LocalSettings.php: require_once( "$IP/includes/DefaultSettings.php" ); If I remove that, $wgBaseDirectory and MW_INSTALL_PATH are the same value. So perhaps it has something to

[MediaWiki-l] Re: Unable to upgrade to 1.38.x from 1.37.x

2022-07-04 Thread Paul Williams
This is my second request to be removed from the email list as I no longer use MediaWiki. I have sent two emails to mediawiki-l-le...@lists.wikimedia.org and now the second reply into this Distro. Thanks and have a great, safe 4th! Thank you! On Mon, Jul 4, 2022 at 2:07 AM Benjamin Lees wrote:

[MediaWiki-l] Re: Unable to upgrade to 1.38.x from 1.37.x

2022-07-04 Thread Stefanie Leisestreichler
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

[MediaWiki-l] Re: Unable to upgrade to 1.38.x from 1.37.x

2022-07-04 Thread Benjamin Lees
Pretty strange, since the error in question literally checks "$wgBaseDirectory !== MW_INSTALL_PATH". Maybe there's something weird going on because of the order in which the files are initialized. What does it output if you add debugging checks for $wgBaseDirectory and MW_INSTALL_PATH after line

[MediaWiki-l] Re: Unable to upgrade to 1.38.x from 1.37.x

2022-07-03 Thread Jeffrey Walton
On Sun, Jul 3, 2022 at 7:09 PM Jeffrey Walton wrote: > > On Sun, Jul 3, 2022 at 6:57 PM Jeffrey T. Darlington > 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

[MediaWiki-l] Re: Unable to upgrade to 1.38.x from 1.37.x

2022-07-03 Thread Jeffrey Walton
On Sun, Jul 3, 2022 at 6:57 PM Jeffrey T. Darlington 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')

[MediaWiki-l] Re: Unable to upgrade to 1.38.x from 1.37.x

2022-07-03 Thread Jeffrey Walton
On Sun, Jul 3, 2022 at 6:57 PM Jeffrey T. Darlington 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')

[MediaWiki-l] Re: Unable to upgrade to 1.38.x from 1.37.x

2022-07-03 Thread Jeffrey T. Darlington
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:

[MediaWiki-l] Re: Unable to upgrade to 1.38.x from 1.37.x

2022-07-03 Thread Jeffrey Walton
On Sun, Jul 3, 2022 at 6:19 PM Jeffrey T. Darlington wrote: > > Thanks for the suggestions, but no luck here. I did indeed have the old "$IP > = MW_INSTALL_PATH" block. But if I comment that out, I still get the same > "Unable to open file /Vector/skin.json" error. Same goes for the >

[MediaWiki-l] Re: Unable to upgrade to 1.38.x from 1.37.x

2022-07-03 Thread Jeffrey T. Darlington
Thanks for the suggestions, but no luck here. I did indeed have the old "$IP = MW_INSTALL_PATH" block. But if I comment that out, I still get the same "Unable to open file /Vector/skin.json" error. Same goes for the "$wgBaseDirectory = MW_INSTALL_PATH" suggestion; that gives me the

[MediaWiki-l] Re: Unable to upgrade to 1.38.x from 1.37.x

2022-07-03 Thread Benjamin Lees
Hi Jeffrey, I think this is indeed the same issue as in the previous thread: https://lists.wikimedia.org/hyperkitty/list/mediawiki-l@lists.wikimedia.org/thread/5YKDMFRHANRXKFDLWGLHXTGWSOW7V676/ Of course, you have reached the point where I didn't have a way forward. :-) A bit of background