Dear Group. Last night, I spoke with my webhosting technical support (iPower.com) and was told that their servers are running php5.2.17, and they have no plans to upgrade to php5.2.9, which is what mediawiki requires. So I presumed that there was not way to make it work on iPower servers and so I uninstalled it.
The wiki that is current up is PmWiki, which seems to run perfectly fine but without some features of mediawiki which I like a lot better. I thought about installing legacy version of mediawiki 1.6.5? but the warnings of insecurity scared me out of that.
Thanks for looking into it but without the proper modules, I guess having mediawiki hosted at my account is not possible and I just paid for 2yrs too so no chance of moving. :(
Norm T.
=====================
On Thu, Oct 20, 2011 at 6:12 AM, mediawiki-l-request@lists.wikimedia.org wrote:
Send MediaWiki-l mailing list submissions to mediawiki-l@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@lists.wikimedia.org
You can reach the person managing the list at mediawiki-l-owner@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: PostgreSQL error (John W. Foster) 2. Re: Upgrading to 1.17 (Brion Vibber) 3. Re: Upgrading to 1.17 (Eric Armstrong) 4. Re: MW seems to get confused when IP address of client machine changes while user is logged in (Brion Vibber) 5. Problem with user page, talk page, other pages, not displaying (Norman) 6. Re: Problem with user page, talk page, other pages, not displaying (Daniel Barrett) 7. Re: Problem with user page, talk page, other pages, not displaying (Steve VanSlyck) 8. Re: Problem with user page, talk page, other pages, not displaying (Daniel Barrett)
Message: 1 Date: Wed, 19 Oct 2011 09:49:47 -0500 From: "John W. Foster" jfoster81747@gmail.com Subject: Re: [Mediawiki-l] PostgreSQL error To: MediaWiki announcements and site admin list mediawiki-l@lists.wikimedia.org Message-ID: 1319035787.3926.12.camel@beast.home Content-Type: text/plain; charset=UTF-8
On Mon, 2011-10-17 at 16:47 -0400, Bret Bailey wrote:
I changed my media wiki configuration. I am now trying to install it with mysql database. I have the everything installed, but when I go to the main page, I get the following error:
A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was:
(SQL query hidden)
from within function "IndexPager::reallyDoQuery (LogPager)". Database returned error "1146: Table 'my_wiki.tag_summary' doesn't exist (localhost)".
When I query the mysql database, the tag_summary table is not there. How do I go about getting this data?
Thanks.
-------------------snip------------------------ Did you do a complete new installation? With a new database created in MySQL; Or did you use the postgres database & export it to an .sql backup??? If you used an exported data base, did you run update.php command from /yourwikiname/maintenance/?? If not do so. If you used an exported data base, MY Experience is that you need to use PhpMyAdmin or some other interface to 'import the backup into your newly created MySQL database. If you are starting from a fresh install with a new basically empty database. then check to see if this is an Extension error message. You may have installed an extension that is not working properly. Disable it by commenting it out in LocalSettings.php then restart apache or what ever web server your using & check it again. Good Luck frosty
Message: 2 Date: Wed, 19 Oct 2011 10:30:33 -0700 From: Brion Vibber brion@pobox.com Subject: Re: [Mediawiki-l] Upgrading to 1.17 To: eric@longjump.com, MediaWiki announcements and site admin list mediawiki-l@lists.wikimedia.org Message-ID: CAFnWYTkAXTLFKFmEQ4dbWnNxv8cHWfVQG_XBx-kfi8_=o_aBbw@mail.gmail.com Content-Type: text/plain; charset=UTF-8
On Tue, Oct 18, 2011 at 6:56 PM, Eric Armstrong eric@longjump.com wrote:
The download page for 1.17 has the (somewhat scary) comment:
If your MediaWiki installation is heavily modified, it may be difficult to incorporate the latest official changes/updates. (So here's version 1.6.5. It's good for maybe a year.)
I accept the need to do whatever integration is necessary-especially since the one-year clock has been ticking for a while now--but I need to know:
a) What constitutes "heavy" modification? --We have a installed a number of plugins, have defined some variables, have created several customized skins. Is that heavy or light?
It's not clear from the above whether you've modified MediaWiki at all, or if you've just dropped in extensions and skins with no modification whatsoever.
If you changed files that were distributed with MediaWiki, then you've modified it and it's up to you to figure out how to perform those modifications on the new version.
Extensions, skins etc can still be problematic, for instance if they make assumptions about internal interfaces which have changed. Skins are particularly fragile, as it's a poor interface to begin with and has never been very stable.
You're also more likely to see errors related to extensions exacerbated at upgrade time; for instance if you also upgrade PHP you may encounter new problems related to changes in PHP's handling of references in function parameters. You may also find that updates in core that clean up old incorrect use of references cause extensions that have not been similarly cleaned up to require modification.
b) What, in general, should be the migration process? I'm guessing there are other kinds of modifications that could be done. So ideally the upgrade notes would include a taxonomy of cases: - If you've done "X", you'll need to do "Y".
- Make a testing/staging copy of your site -- if you are not already doing
this you are in trouble :)
- Upgrade the testing/staging copy following standard procedures in the
instructions (pull in updated code, run the updater script)
- Test that everything works.
If anything doesn't work as expected, debug and fix it. Follow normal debugging procedures that all software developers and system administrators are familiar with, such as testing small changes, turning individual pieces on and off to localize the source of a problem, etc. Make use of error messages produced directly in output and in system logs. Check the source code when you see line numbers or backtraces. Google your error messages to see if people have seen them before. If you are not familiar with how to find error and system logs from PHP, please check the documentation on php.net, the documentation for your operating system, or contact your system administrator for information.
-- brion
Message: 3 Date: Wed, 19 Oct 2011 11:11:41 -0700 From: "Eric Armstrong" eric@longjump.com Subject: Re: [Mediawiki-l] Upgrading to 1.17 To: "'Brion Vibber'" brion@pobox.com, "'MediaWiki announcements and site admin list'" mediawiki-l@lists.wikimedia.org Message-ID: 038401cc8e8a$8dc96980$a95c3c80$@com Content-Type: text/plain; charset="UTF-8"
Really good advice, Brion. Much appreciated.
(And yes, we are for sure doing the upgrade in a sandbox!)
:__)
From: brion.vibber@gmail.com [mailto:brion.vibber@gmail.com] On Behalf Of Brion Vibber Sent: Wednesday, October 19, 2011 10:31 AM To: eric@longjump.com; MediaWiki announcements and site admin list Subject: Re: [Mediawiki-l] Upgrading to 1.17
On Tue, Oct 18, 2011 at 6:56 PM, Eric Armstrong eric@longjump.com wrote:
The download page for 1.17 has the (somewhat scary) comment:
If your MediaWiki installation is heavily modified, it may be difficult to incorporate the latest official changes/updates. (So here's version 1.6.5. It's good for maybe a year.)
I accept the need to do whatever integration is necessary-especially since the one-year clock has been ticking for a while now--but I need to know:
a) What constitutes "heavy" modification? --We have a installed a number of plugins, have defined some variables, have created several customized skins. Is that heavy or light?
It's not clear from the above whether you've modified MediaWiki at all, or if you've just dropped in extensions and skins with no modification whatsoever.
If you changed files that were distributed with MediaWiki, then you've modified it and it's up to you to figure out how to perform those modifications on the new version.
Extensions, skins etc can still be problematic, for instance if they make assumptions about internal interfaces which have changed. Skins are particularly fragile, as it's a poor interface to begin with and has never been very stable.
You're also more likely to see errors related to extensions exacerbated at upgrade time; for instance if you also upgrade PHP you may encounter new problems related to changes in PHP's handling of references in function parameters. You may also find that updates in core that clean up old incorrect use of references cause extensions that have not been similarly cleaned up to require modification.
b) What, in general, should be the migration process? I'm guessing there are other kinds of modifications that could be done. So ideally the upgrade notes would include a taxonomy of cases: - If you've done "X", you'll need to do "Y".
Make a testing/staging copy of your site -- if you are not already doing this you are in trouble :)
Upgrade the testing/staging copy following standard procedures in the instructions (pull in updated code, run the updater script)
Test that everything works.
If anything doesn't work as expected, debug and fix it. Follow normal debugging procedures that all software developers and system administrators are familiar with, such as testing small changes, turning individual pieces on and off to localize the source of a problem, etc. Make use of error messages produced directly in output and in system logs. Check the source code when you see line numbers or backtraces. Google your error messages to see if people have seen them before. If you are not familiar with how to find error and system logs from PHP, please check the documentation on php.net, the documentation for your operating system, or contact your system administrator for information.
-- brion
Message: 4 Date: Wed, 19 Oct 2011 12:14:00 -0700 From: Brion Vibber brion@pobox.com Subject: Re: [Mediawiki-l] MW seems to get confused when IP address of client machine changes while user is logged in To: MediaWiki announcements and site admin list mediawiki-l@lists.wikimedia.org Message-ID: CAFnWYTkXDbsi9fE29Mv0sDzO2SXNz8qur1WZDBapwGRnOw6riA@mail.gmail.com Content-Type: text/plain; charset=UTF-8
On Tue, Oct 18, 2011 at 11:36 AM, Dan Nessett dnessett@yahoo.com wrote:
From what I have read, I thought this would fire up the session garbage collector on each access and timeout sessions after 60 seconds. It appears the latter is true, since if I log in (not setting "remember me"), edit a page, wait 60 seconds and try once again to edit the page, the latter is disallowed and the resulting response shows me logged off.
However, when I look at the sessions directory, the session created by my login is still there. Maybe I don't understand what the garbage collector does, but I assumed it would destroy the session record if its lifetime exceeded maxlifetime.
I know this is a PHP question, not a MW question, but I was hoping someone might fill me in. By the way, I am running PHP 5.3.4.
Off the top of my head I'd guess this:
- around login time, a session is started:
** ID is generated: 123456789abcdef ** session cookie is sent to browser ** /path/to/sessions/123456789abcdef file is stored with the fresh data
- after a while, some other request comes in
** session GC runs, removing the file /path/to/sessions/123456789abcdef
- your first browser reconnects, providing a session ID key in its cookie
** server sees no session with that id, so establishes a new one ** /path/to/sessions/123456789abcdef file is stored with the fresh data
Possibly the request to trigger GC was also your own second request.
-- brion
Message: 5 Date: Wed, 19 Oct 2011 21:09:33 -0700 From: Norman analogalley@gmail.com Subject: [Mediawiki-l] Problem with user page, talk page, other pages, not displaying To: mediawiki-l@lists.wikimedia.org Message-ID: CAPdC62qFYJUaJ0Hn+qoDaEQBhdGcz3ZZE_B8CY0Tzd1eH9_PuA@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1
Dear Mediawiki support folks;
Hello. Please, I need help. I installed and have mediawiki up and running. Problem is that the admin (or user) and My Talk links at the top of the page result in an error message via both IE and FF. So I guess that means there is a problem accessing or creating my pages. This happens whether I am logged in as admin or as another reader/user that I created. I also notice that a few links on the sidebar have the same issue; namely community portal and current events (those links were installed in the default installation).
On IE, I get a "page cannot be displayed error"
On FF, I get the following error: "Corrupted Content Error The page you are trying to view cannot be shown because an error in the data transmission was detected. The page you are trying to view cannot be shown because an error in the data transmission was detected.Please contact the website owners to inform them of this problem."
Can someone help or shed light on this? I really would like to get this operating right and am at a loss, struggling big time. :-(
If you would like to see this issue in action, the URL is www.analogalley.com/wiki
Thank you in advance, N. Tang.
Message: 6 Date: Thu, 20 Oct 2011 11:26:31 +0000 From: Daniel Barrett danb@VistaPrint.com Subject: Re: [Mediawiki-l] Problem with user page, talk page, other pages, not displaying To: "analogalley@gmail.com" analogalley@gmail.com, MediaWiki announcements and site admin list mediawiki-l@lists.wikimedia.org Message-ID: 68CF225601ADF74BA1F8A2511535F85D0A7CC18D@WNDMAIL02.vistaprint.net Content-Type: text/plain; charset="us-ascii"
When I visit Talk:Foo, your webserver is rewriting this to TalkFoo without the colon (:). On Windows, colon is a special character for file paths. So either your webserver configuration is intentionally stripping out colons (say, by a rewrite rule), or your webserver cannot handle colons and is having errors (check your webserver logs for error messages).
DanB
Message: 7 Date: Thu, 20 Oct 2011 08:55:50 -0400 From: "Steve VanSlyck" s.vanslyck@spamcop.net Subject: Re: [Mediawiki-l] Problem with user page, talk page, other pages, not displaying To: "MediaWiki announcements and site admin list" mediawiki-l@lists.wikimedia.org Message-ID: 20111020.125550.984.1@LEGAL Content-Type: text/plain
**Who's** webserver?
----- Original Message ----- From: Daniel Barrett danb@VistaPrint.com To: "analogalley@gmail.com" analogalley@gmail.com, MediaWiki announcements and site admin list mediawiki-l@lists.wikimedia.org Date: Thu, 20 Oct 2011 11:26:31 +0000 Subject: Re: [Mediawiki-l] Problem with user page, talk page, other pages, not displaying
When I visit Talk:Foo, your webserver is rewriting this to TalkFoo without the colon (:). On Windows, colon is a special character for file paths. So either your webserver configuration is intentionally stripping out colons (say, by a rewrite rule), or your webserver cannot handle colons and is having errors (check your webserver logs for error messages).
DanB
MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Message: 8 Date: Thu, 20 Oct 2011 13:11:58 +0000 From: Daniel Barrett danb@VistaPrint.com Subject: Re: [Mediawiki-l] Problem with user page, talk page, other pages, not displaying To: MediaWiki announcements and site admin list mediawiki-l@lists.wikimedia.org Message-ID: 68CF225601ADF74BA1F8A2511535F85D0A7CC1CC@WNDMAIL02.vistaprint.net Content-Type: text/plain; charset="us-ascii"
Steve VanSlyck
**Who's** webserver?
The webserver running MediaWiki, in this case, www.analogalley.com.
DanB
MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
End of MediaWiki-l Digest, Vol 97, Issue 9