On Jun 1, 2014, at 2:34 PM, Rob Lingelbach <rob(a)colorist.org> wrote:
On Jun 1, 2014, at 2:19 PM, John <phoenixoverride(a)gmail.com> wrote:
I would have waited for 1.23. But your first step
is either upgrading the
extensions or removing them. Most broken extensions cause havoc trying to
debug. Once you remove all your extensions you can add them back one by one
until your wiki breaks. At that point you know where the problem is.
In removing them just now, I lost count at 50 or 60. thanks for the advice.
I may be out of sync with myself here. In trying to simplify things, I’ve done the
following
(after the appropriate backing up steps, db dump, etc.):
Loaded the files in my wiki directory from mw-1.22.7 . First, because I was having the
same
problems with a blank wiki *even after commenting out all extensions from
LocalSettings.php*
I decided to start fresh and have only the files from mw-1.22.7 in /var/www/wiki.
I then checked LocalSettings.php for structural naming (wiki root etc) and all looked ok.
I ran ‘php maintenance/update.php’. No errors returned. Yet still a blank wiki. Is it
possible that
I’ve outsmarted myself and the MySQL db from my legacy wiki is now out of sync with the
wiki
files (which I removed after backing up)?
I can reconvene the wiki as it was before; all the files exist as backups. My suspicion
is that at some
point my LocalSettings.php ran afoul of a MW update, even with extensions today commented
out, and if
I try to debug it, I might get to the heart of the matter. I must admit I’m not sure
what process to use
(logfiles) to follow for debugging.
--
Rob Lingelbach
http://rob.colorist.org
http://colorist.org rob(a)colorist.org