No apology necessary. :) Considering that my install carries with it a
decade of "settings cruft", it's probably a miracle it works at all. I
will readily admit that I rarely take a look at the release notes unless
something breaks, and even then tracking something like this down through
the sea of changes isn't easy. I chalk this up to MediaWiki's complexity
and rapid development cycle, as well as perhaps unclear documentation
that's rather hard to sort through. Just about every other CMS has its
share of pitfalls as well. (I'm looking at you, WordPress.)
--
Jeffrey T. Darlington
General Protection Fault
https://www.gpf-comics.com/
On Fri, Sep 21, 2018 at 11:20 AM Brian Wolff
bawolff@gmail.com wrote:
> Glad to hear its resolved. I think I owe you an apology for not
> believing MediaWiki was at fault, where this is something I would
> consider a MediaWiki fault.
>
> --
> Brian
>
> On Fri, Sep 21, 2018 at 3:04 PM, Jeff Darlington
>
jeff.darlington@gmail.com wrote:
> > That seemed to do the trick. Removing $wgDBmwschema allowed the update
> to
> > proceed. I'm now getting a different error with my extension (which is
> > unrelated and on my own plate to fix), but at least the core wiki is
> > working just fine.
> >
> > Thanks for the input, especially David D., who hit the nail on the head.
> >
> > --
> >
> > Jeffrey T. Darlington
> > General Protection Fault
> >
https://www.gpf-comics.com/
> >
> >
> > On Fri, Sep 21, 2018 at 10:55 AM Jeff Darlington <
> jeff.darlington@gmail.com>
> > wrote:
> >
> >> Actually, that looks suspiciously familiar, and looking at my
> >> LocalSettings.php, $wgDBmwschema *is* present. I never set it; it's a
> >> default under the "Postgres specific settings" block and has been
> carried
> >> over from install to install for years. (I have no idea how old that
> is; I
> >> probably first installed MediaWiki back in 2008, maybe?) I'll try
> removing
> >> that and see if that works.
> >>
> >> --
> >>
> >> Jeffrey T. Darlington
> >> General Protection Fault
> >>
https://www.gpf-comics.com/
> >>
> >>
> >> On Fri, Sep 21, 2018 at 10:49 AM David Daw
daw1cb2@gmail.com wrote:
> >>
> >>> Hey Jeff,
> >>>
> >>> Take a look at this and see if this helps
> >>>
https://www.mediawiki.org/wiki/Topic:Uf63mplrzzuxz0it
> >>>
> >>> $wgDBmwschema may need to be removed from or corrected in
> >>> LocalSettings.php
> >>>
> >>> It's also mentioned here :
> >>>
https://www.mediawiki.org/wiki/MediaWiki_1.31#Configuration_changes
> >>>
> >>>
> >>> - $wgDBmwschema
> >>> <
> >>>
https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:$wgDBmwschema
> >
> >>> now
> >>> affects all database types. Old MediaWiki versions were setting
> this to
> >>> 'mediawiki' during the installer, which may cause errors during the
> >>> upgrade
> >>> when your database is not PostgreSQL or MSSQL. In that case, remove
> >>> this
> >>> setting from LocalSettings.php.
> >>>
> >>>
> >>> On Fri, Sep 21, 2018 at 9:47 AM Jeff Darlington <
> >>> jeff.darlington@gmail.com>
> >>> wrote:
> >>>
> >>> > I only run one wiki, and the database has been "wikidb" since I first
> >>> > installed it years ago. The definition of $wgDBname appears only
> once
> >>> in
> >>> > LocalSettings.php.
> >>> >
> >>> > When I upgrade I always extract the tarball into a pristine new
> folder,
> >>> > then copy over LocalSettings.php and my one extension. I use
> symlinks to
> >>> > point to a common external image folder (which has worked better for
> me
> >>> > than copying the image folder back and forth all the time) and for
> the
> >>> > site's definition in Apache (i.e., Apache points to the symlink
> "wiki",
> >>> > which then points to the currently active MediaWiki code base).
> When I
> >>> run
> >>> > update.php, I always use the raw path rather than the symlink so I
> know
> >>> I'm
> >>> > pointing to the right code.
> >>> >
> >>> > My guess is that update.php or some script it depends on isn't
> honoring
> >>> > $wgDBname. That said, I can't believe I'm the only person who's
> using a
> >>> > custom DB name and thus the only person who is having this problem.
> >>> >
> >>> > On Fri, Sep 21, 2018 at 10:35 AM [[kgh]]
mediawiki@kghoffmeyer.de
> >>> wrote:
> >>> >
> >>> > > This may sound stupid, but are you sure that you are mapping the
> >>> update
> >>> > > script to the correct "LocalSettings.php" file? Perhaps you moved
> >>> around
> >>> > > folders at some time. Another thing may be that you have the
> parameter
> >>> > > twice in your "LocalSettings.php" file and that one value overrides
> >>> the
> >>> > > other. Apart from that, I do not know what could be the issue.
> >>> > >
> >>> > > Cheers
> >>> > >
> >>> > > Am 21.09.2018 um 16:28 schrieb Jeff Darlington:
> >>> > > > As I stated several months ago, the updater isn't honoring
> >>> $wgDBname,
> >>> > > which
> >>> > > > I have explicitly set in LocalSettings.php to "wikidb":
> >>> > > >
> >>> > > > $wgDBname = "wikidb";
> >>> > > >
> >>> > >
> >>> > >
> >>> > > _______________________________________________
> >>> > > MediaWiki-l mailing list
> >>> > > To unsubscribe, go to:
> >>> > >
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
> >>> > >
> >>> > _______________________________________________
> >>> > MediaWiki-l mailing list
> >>> > To unsubscribe, go to:
> >>> >
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
> >>> >
> >>> _______________________________________________
> >>> MediaWiki-l mailing list
> >>> To unsubscribe, go to:
> >>>
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
> >>>
> >>
> > _______________________________________________
> > MediaWiki-l mailing list
> > To unsubscribe, go to:
> >
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
> _______________________________________________
> MediaWiki-l mailing list
> To unsubscribe, go to:
>
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>