Thank you for your responses.
The way I upgraded (to date) from the original 1.16 version to 1.25 was to
1. Upgrade the server which was running an outdated version of Debian. So,
I created a new server with the current stable distro of Debian and copied
the MySQL db to the new version of MySQL on the new server. I copied the
mediawiki (v 1.16) to the new server as well. This resulted in a few minor
issues due to incompatibilities w/ the updated PHP which I fixed. This new
server is now running
http://www.hindupedia.com
2. Created a backup image of the VM running
http://www.hindupedia.com (on
Rackspace Cloud) and created a new server with that image (which is now
http://www.hindupedia.org)
I don't think that this is due to collisions as the updated MySQL and old
mediawiki running on a new version of PHP didn't have any problems (this is
hindupedia.com).
I also didn't export/import the database between
hindupedia.com (running
updated OS/PHP but v1.16 of mediawiki) and
hindupedia.org (running new
mediawiki). So, don't think that this i the problem.
Since
hindupedia.com is live and doesn't have any issues with the
multi-byte characters (and was where I migrated the data from the old mysql
to the new mysql), I think issue is happening due to something the
update.php script does (or doesn't do).
Any other ideas?
Thanks!
Krishna
--------------------------------------------------------------------------------
Krishna Maheshwari
Hindupedia, the Hindu Encyclopedia (
www.hindupedia.com)
--------------------------------------------------------------------------------
On Sat, Nov 14, 2015 at 7:00 AM, <mediawiki-l-request(a)lists.wikimedia.org>
wrote:
Send MediaWiki-l mailing list submissions to
mediawiki-l(a)lists.wikimedia.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
or, via email, send a message with subject or body 'help' to
mediawiki-l-request(a)lists.wikimedia.org
You can reach the person managing the list at
mediawiki-l-owner(a)lists.wikimedia.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of MediaWiki-l digest..."
Today's Topics:
1. Re: Upgrading from v1.16.5 to 1.25.3 resulting in corruption
of multi-byte article titles & articles (Ray Paseur)
2. Re: Upgrading from v1.16.5 to 1.25.3 resulting in corruption
of multi-byte article titles & articles (Bartosz Dziewoński)
3. [External_Data] Selection of language, country, cities, etc
(Ed Hoo)
4. Email problem following 1.16 to 1.25 conversion (Cal Frye)
5. Re: Email problem following 1.16 to 1.25 conversion
(Thomas Mulhall)
----------------------------------------------------------------------
Message: 1
Date: Fri, 13 Nov 2015 14:25:15 +0000
From: Ray Paseur <ray.paseur(a)armedia.com>
To: "mediawiki-l(a)lists.wikimedia.org"
<mediawiki-l(a)lists.wikimedia.org>
Subject: Re: [MediaWiki-l] Upgrading from v1.16.5 to 1.25.3 resulting
in corruption of multi-byte article titles & articles
Message-ID:
<
DM2PR0101MB10882712EF8FB3408991C9BC86110(a)DM2PR0101MB1088.prod.exchangelabs.com
Content-Type: text/plain; charset="iso-8859-1"
KKM: Sorry that I do not have a direct solution to the issue, but I have
seen and researched similar issues in other sites. This article should
help explain what may be happening and offer some pointers. The version
level of PHP may be in play.
http://iconoun.com/articles/collisions/
------------------------------
Message: 2
Date: Fri, 13 Nov 2015 16:21:19 +0100
From: Bartosz Dziewoński <matma.rex(a)gmail.com>
To: MediaWiki announcements and site admin list
<mediawiki-l(a)lists.wikimedia.org>
Subject: Re: [MediaWiki-l] Upgrading from v1.16.5 to 1.25.3 resulting
in corruption of multi-byte article titles & articles
Message-ID: <5645FFEF.6070500(a)gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
I think something went wrong when you exported and imported the
database. (I assume that's how you got the two sites up at the same
time?) MediaWiki always stores all text in the UTF-8 encoding,
and in the database, the encoding of the fields is marker as either
"binary" or "utf8" (the former is recommended due to problems with
older
MySQL versions).
My guess is that in the `page` table, the `page_title` field was marked
as being in some different encoding. This does not normally cause
problems (MediaWiki doesn't use any of MySQL encoding conversion
functions), but when you exported it, MySQL tried to interpret the UTF-8
bytes as whatever-encoding bytes and converted that to UTF-8. When you
imported, the data was already damaged.
If that's indeed the case (I'm just guessing), change the encoding of
the field in the original table (do not convert or re-encode the data,
it's correct, just marked wrong) and try to re-export and re-import that
table.
--
Bartosz Dziewoński
------------------------------
Message: 3
Date: Fri, 13 Nov 2015 16:11:21 -0500
From: Ed Hoo <edward.hoo(a)gmail.com>
To: MediaWiki announcements and site admin list
<mediawiki-l(a)lists.wikimedia.org>
Subject: [MediaWiki-l] [External_Data] Selection of language, country,
cities, etc
Message-ID: <A9821DC2-8F0D-412C-B1B2-569B7027A452(a)gmail.com>
Content-Type: text/plain; charset=us-ascii
Hi everyone,
When using cargo and semantic forms, what is the best way to keep large
lists of valid values.
https://www.mediawiki.org/wiki/Extension:External_Data seems like a
reasonable option. Am I overlooking a simpler option for relatively large
lists?
As a separate question is there a way that allows for pick-lists to be
organized in a hierarchical manner? In the past, instead of using a
dropdown listbox or combo box I used a popup menu with a submenu and that
made selecting a value from a list with 100-200 choices very easy and very
fast for the user. Short of using 2 fields (one conditional on the other)
what are the options in the wiki universe?!!
PS. Thanks for the tip on the data import extension!!
Thanks again!
-Ed
------------------------------
Message: 4
Date: Fri, 13 Nov 2015 17:14:12 -0500
From: Cal Frye <cal.frye(a)oberlin.edu>
To: mediawiki-l(a)lists.wikimedia.org
Subject: [MediaWiki-l] Email problem following 1.16 to 1.25 conversion
Message-ID: <564660B4.9050000(a)oberlin.edu>
Content-Type: text/plain; charset=ISO-8859-1
Hi,
We did a migration and conversion from v.1.16 to 1.25.3 on a new server,
using XAMPP as our base. Generally, it worked well, thanks for that!
We have a lingering problem, however, in sending email, including
confirmation messages, password resets, etc. No mail is sent, and the
error, "Unknown error in PHP's mail() function." is returned.
Google suggests two small changes in the UserMailer.php file, both
having to do with the $headers variable. Neither fix works, however, in
our case. I've scanned the archives of this list back to January, and
didn't see anything there that seemed like this problem.
Can anyone point me in the right direction? Many thanks!
Cal Frye
------------------------------
Message: 5
Date: Fri, 13 Nov 2015 23:23:16 +0000
From: Thomas Mulhall <thomasmulhall410(a)yahoo.com>
To: mediawiki-l(a)lists.wikimedia.org
Subject: Re: [MediaWiki-l] Email problem following 1.16 to 1.25
conversion
Message-ID:
<1447456996.86974.YahooMailMobile(a)web172705.mail.ir2.yahoo.com>
Content-Type: text/plain; charset=utf-8
Hi quick questions did you also update xampp since updating that may fix
problem. Also what php version are you using. MediaWiki 1.25 supports php
5.3 or higher. And also in your local settings.php file you may need to
either regenerate it so that it is much easier to update meaning you re
generate the local settings file then copying it over to the
localsettings.php file. Also removed when regenerating it by going to the
sub folder w-config that localsettings.php should be temporary renamed so
localsettings.php can be regenerated. Then rename file back and copy over
from the new file to the old.
------------------------------
Subject: Digest Footer
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
------------------------------
End of MediaWiki-l Digest, Vol 146, Issue 14
********************************************