I have Mediawiki installation went from 1.17 through 1.18 RC1 and to 1.18 - no problems.
But another Mediawiki has had some problems going direct from 1.17 to 1.18 - I took out Recaptcha and now see this:
*Fatal error*: Cannot redeclare wfprofilein() (previously declared in /xxxxxxxx/public_html/includes/profiler/Profiler.php:14) in */xxxxx/public_html/includes/ProfilerStub.php* on line *25*
Not sure why...
Gordo
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/29/2011 11:58 AM, Gordon Joly wrote:
*Fatal error*: Cannot redeclare wfprofilein() (previously declared in /xxxxxxxx/public_html/includes/profiler/Profiler.php:14) in */xxxxx/public_html/includes/ProfilerStub.php* on line *25*
I'm getting lots of similar errors about redeclaring wfprofilein():
[Tue Nov 29 11:49:01 2011] [error] [client {my-IP}] PHP Fatal error: Cannot redeclare wfprofilein() in {path-to-wiki}/includes/ProfilerStub.php on line 19, referer: {domain-name}/wiki/Special:SpecialPages [Tue Nov 29 11:49:04 2011] [error] [client {my-IP}] PHP Fatal error: Cannot redeclare wfprofilein() in {path-to-wiki}/includes/ProfilerStub.php on line 19, referer: {domain-name}/wiki/Special:SpecialPages [Tue Nov 29 11:49:10 2011] [error] [client {my-IP}] PHP Fatal error: Cannot redeclare wfprofilein() in {path-to-wiki}/includes/ProfilerStub.php on line 19
I had to roll back to 1.17.1; all my 1.18.0 wiki pages are 500-ing.
- --
Jeff Darlington General Protection Fault {domain-name}/
hello, i had the same problem if i rewrite the files. so i deleted all files und uploaded the new files separatly.
best regards s.net
-----Ursprüngliche Nachricht----- From: Gordon Joly Sent: Tuesday, November 29, 2011 5:58 PM To: MediaWiki announcements and site admin list Subject: [Mediawiki-l] Upgrade to 1.18
I have Mediawiki installation went from 1.17 through 1.18 RC1 and to 1.18 - no problems.
But another Mediawiki has had some problems going direct from 1.17 to 1.18 - I took out Recaptcha and now see this:
*Fatal error*: Cannot redeclare wfprofilein() (previously declared in /xxxxxxxx/public_html/includes/profiler/Profiler.php:14) in */xxxxx/public_html/includes/ProfilerStub.php* on line *25*
Not sure why...
Gordo
On Tue, 29 Nov 2011 08:58:09 -0800, Gordon Joly gordon.joly@pobox.com wrote:
I have Mediawiki installation went from 1.17 through 1.18 RC1 and to 1.18 - no problems.
But another Mediawiki has had some problems going direct from 1.17 to 1.18 - I took out Recaptcha and now see this:
*Fatal error*: Cannot redeclare wfprofilein() (previously declared in /xxxxxxxx/public_html/includes/profiler/Profiler.php:14) in */xxxxx/public_html/includes/ProfilerStub.php* on line *25*
Not sure why...
Gordo
Sounds like you upgraded MediaWiki by extracting 1.18 on top of 1.17 instead of extracting 1.18 to a new directory then moving the config and other stuff to the new directory. And have an old StartProfiler.php.
includes/ProfilerStub.php was moved to includes/profiler/Profiler.php and includes/profiler/ProfilerStub.php in 1.18
Basically what it looks like is happening is that you have a includes/ProfilerStub.php file from 1.17 and includes/profiler/ from 1.18. Because your StartProfiler.php likely uses the old method of a require_once (instead of autoloading as I believe we now do) MediaWiki is loading the 1.18 profiler code from includes/profiler/Profiler.php and then when it require your StartProfiler.php that old require_once is requiring the old 1.17 code from includes/ProfilerStub.php causing a fatal error as the old code tries to redefine the same method.
If you don't need the profiler I recommend you delete your StartProfiler.php. If you do you should probably delete the require_once line. You'd also probably be better off clearing out all the outdated files of 1.17 code that were left behind since you extracted 1.18 over top of 1.17. Though the easiest way to do that is to just re-untar 1.18 in another directory, and move your actual LocalSettings, extensions, images/, etc... to there.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/29/2011 12:31 PM, Daniel Friesen wrote:
Sounds like you upgraded MediaWiki by extracting 1.18 on top of 1.17 instead of extracting 1.18 to a new directory then moving the config and other stuff to the new directory. And have an old StartProfiler.php.
I can't speak for Gordon, but that is indeed what I did: I extracted the 1.18 tarball on top of the existing 1.17 directory. This has usually worked well enough for me in the past, so I tried to repeat what worked before.
Unfortunately, I'm still having terrible luck. I extracted 1.18 into a clean directory, copied over LocalSettings.php and my images folder (I have no extensions installed so I skipped that), and recreated my customized MonoBook skin. (For the skin, I copied the core MonoBook class file and made my tweaks to insert ads, AddThis, etc. For the monobook resource folder, I use symbolic links to all the files except the main.css, which I copied over and made one tweak to the background image.) However, my wiki is still white-screening with the following errors in the Apache log:
[Tue Nov 29 13:09:09 2011] [error] [client {my-ip}] "" is not a valid magic word for "canonicalurl", referer: {domain-name}/wiki/Special:SpecialPages [Tue Nov 29 13:09:09 2011] [error] [client {my-ip}] "" is not a valid magic word for "canonicalurle", referer: {domain-name}/wiki/Special:SpecialPages [Tue Nov 29 13:09:09 2011] [error] [client {my-ip}] PHP Fatal error: Call to a member function getGroup() on a non-object in {path-to-wiki}/includes/OutputPage.php on line 2958, referer: {domain-name}/wiki/Special:SpecialPages [Tue Nov 29 13:10:07 2011] [error] [client {my-ip}] "" is not a valid magic word for "canonicalurl" [Tue Nov 29 13:10:07 2011] [error] [client {my-ip}] "" is not a valid magic word for "canonicalurle" [Tue Nov 29 13:10:07 2011] [error] [client {my-ip}] PHP Fatal error: Call to a member function getGroup() on a non-object in {path-to-wiki}/includes/OutputPage.php on line 2958
I'm not sure if this is relevant, but I use the "short URLs" setup using Apache mod_rewrite. The relative URL /wiki/Special:SpecialPages worked well enough under 1.17.1 and below.
I have *NEVER* had this much trouble upgrading MediaWiki. At this point, I'm probably going to throw in the towel. I can get 1.17.1 to work fine, so I'm reverting back to that. As much as I'd like to have the latest version installed, I can't afford this much down-time, or the time I've spent on this upgrade that I really need to be working on other projects.
- --
Jeff Darlington General Protection Fault http://www.gpf-comics.com/
It should be noted that the MediaWiki docs recommend doing the following for an upgrade (after your backups):
tar xvzf mediawiki-1.18.0.tar.gz -C /path/to/your/wiki/ --strip-components=1
https://www.mediawiki.org/wiki/Manual:Upgrading#Unpack_the_new_files
If this is out of date or will cause problems for 1.18, it should definitely be changed to reflect that. The users posting about profiler errors followed our instructions.
On Tue, Nov 29, 2011 at 1:25 PM, Jeffrey T. Darlington jeff@gpf-comics.comwrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/29/2011 12:31 PM, Daniel Friesen wrote:
Sounds like you upgraded MediaWiki by extracting 1.18 on top of 1.17 instead of extracting 1.18 to a new directory then moving the config and other stuff to the new directory. And have an old StartProfiler.php.
I can't speak for Gordon, but that is indeed what I did: I extracted the 1.18 tarball on top of the existing 1.17 directory. This has usually worked well enough for me in the past, so I tried to repeat what worked before.
Unfortunately, I'm still having terrible luck. I extracted 1.18 into a clean directory, copied over LocalSettings.php and my images folder (I have no extensions installed so I skipped that), and recreated my customized MonoBook skin. (For the skin, I copied the core MonoBook class file and made my tweaks to insert ads, AddThis, etc. For the monobook resource folder, I use symbolic links to all the files except the main.css, which I copied over and made one tweak to the background image.) However, my wiki is still white-screening with the following errors in the Apache log:
[Tue Nov 29 13:09:09 2011] [error] [client {my-ip}] "" is not a valid magic word for "canonicalurl", referer: {domain-name}/wiki/Special:SpecialPages [Tue Nov 29 13:09:09 2011] [error] [client {my-ip}] "" is not a valid magic word for "canonicalurle", referer: {domain-name}/wiki/Special:SpecialPages [Tue Nov 29 13:09:09 2011] [error] [client {my-ip}] PHP Fatal error: Call to a member function getGroup() on a non-object in {path-to-wiki}/includes/OutputPage.php on line 2958, referer: {domain-name}/wiki/Special:SpecialPages [Tue Nov 29 13:10:07 2011] [error] [client {my-ip}] "" is not a valid magic word for "canonicalurl" [Tue Nov 29 13:10:07 2011] [error] [client {my-ip}] "" is not a valid magic word for "canonicalurle" [Tue Nov 29 13:10:07 2011] [error] [client {my-ip}] PHP Fatal error: Call to a member function getGroup() on a non-object in {path-to-wiki}/includes/OutputPage.php on line 2958
I'm not sure if this is relevant, but I use the "short URLs" setup using Apache mod_rewrite. The relative URL /wiki/Special:SpecialPages worked well enough under 1.17.1 and below.
I have *NEVER* had this much trouble upgrading MediaWiki. At this point, I'm probably going to throw in the towel. I can get 1.17.1 to work fine, so I'm reverting back to that. As much as I'd like to have the latest version installed, I can't afford this much down-time, or the time I've spent on this upgrade that I really need to be working on other projects.
Jeff Darlington General Protection Fault http://www.gpf-comics.com/
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk7VI6oACgkQVNMIBILmfwEirQCggQinqu40zcyckpMEV/Xq82Yh GpUAoJkMxX3YG6SFJHyAw/m3h8ySIlTa =oNgA -----END PGP SIGNATURE-----
MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/29/2011 5:08 PM, Olivier Beaton wrote:
It should be noted that the MediaWiki docs recommend doing the following for an upgrade (after your backups):
tar xvzf mediawiki-1.18.0.tar.gz -C /path/to/your/wiki/ --strip-components=1
https://www.mediawiki.org/wiki/Manual:Upgrading#Unpack_the_new_files
If this is out of date or will cause problems for 1.18, it should definitely be changed to reflect that. The users posting about profiler errors followed our instructions.
In defense of the existing instructions, there's this:
https://www.mediawiki.org/wiki/Manual:Upgrading#Can_my_wiki_stay_online_whil...
"If you are upgrading between major releases of MediaWiki, the preferred procedure is... Unpack the new version of MediaWiki into a new directory. Prepare that new directory: copy your current LocalSettings.php from the old directory, copy any installed extensions and custom skins (if any)."
This, however, is buried way down at the bottom and easy to miss. It also didn't help things in my case, but that's beside the point. Perhaps there should be a separate list of instructions for upgrading between "major" versions and "minor" versions.
It might also be helpful to define "major" and "minor". When I read about a "major" release, I think of moving from, say, version 1.x to 2.x; this seems to be the conventional wisdom when it comes to software versioning. Moving from 1.17.x to 1.18.x implies a minor release in many cases. That varies from project to project, of course, and could be a source of much political debate, but when you define these terms differently than common conventions it helps to share that definition with your users.
- --
Jeff Darlington General Protection Fault http://www.gpf-comics.com/
On 30/11/2011 17:17, Jeffrey T. Darlington wrote:
In defense of the existing instructions, there's this:
https://www.mediawiki.org/wiki/Manual:Upgrading#Can_my_wiki_stay_online_whil...
Point taken. But.... I have established way of updating the six Mediaiwikis that I run, so I have a way of working that suits me.
Happy to change. If somebody changes the instructions.
Gordo
On 04/12/2011 21:21, Gordon Joly wrote:
On 30/11/2011 17:17, Jeffrey T. Darlington wrote:
In defense of the existing instructions, there's this:
https://www.mediawiki.org/wiki/Manual:Upgrading#Can_my_wiki_stay_online_whil...
Point taken. But.... I have established way of updating the six Mediaiwikis that I run, so I have a way of working that suits me.
Happy to change. If somebody changes the instructions.
Gordo
OK. I now accept that instructions suggest a clean directory....
http://www.mediawiki.org/wiki/Manual:Upgrading#Unpack_the_new_files
I shall do this for the next upgrade!
Gordon
On 29/11/2011 22:08, Olivier Beaton wrote:
It should be noted that the MediaWiki docs recommend doing the following for an upgrade (after your backups):
tar xvzf mediawiki-1.18.0.tar.gz -C/path/to/your/wiki/ --strip-components=1
https://www.mediawiki.org/wiki/Manual:Upgrading#Unpack_the_new_files
If this is out of date or will cause problems for 1.18, it should definitely be changed to reflect that. The users posting about profiler errors followed our instructions.
Yes, correct. I was following those instructions, and have done so for years...
Gordo
On 29/11/2011 18:25, Jeffrey T. Darlington wrote:
I can't speak for Gordon, but that is indeed what I did: I extracted the 1.18 tarball on top of the existing 1.17 directory. This has usually worked well enough for me in the past, so I tried to repeat what worked before.
Yes, and perhaps somebody should change the instructions here......
http://www.mediawiki.org/wiki/Manual:Upgrading
That is make some suggestions about (re)moving file....
Gordo
"Jeffrey T. Darlington" jeff@gpf-comics.com writes:
[Tue Nov 29 13:09:09 2011] [error] [client {my-ip}] "" is not a valid magic word for "canonicalurl", referer:
Have you filed a bug for this? I haven't seen one if you have. Please file one at http://bugzilla.wikimedia.org/ or, if you have already filed one, please point me to it.
Mark.
mhershberger@wikimedia.org (Mark A. Hershberger) writes:
"Jeffrey T. Darlington" jeff@gpf-comics.com writes:
[Tue Nov 29 13:09:09 2011] [error] [client {my-ip}] "" is not a valid magic word for "canonicalurl", referer:
Have you filed a bug for this?
I filed one for you now: https://bugzilla.wikimedia.org/32762
Please join us in Friday's bug triage if you can: http://thread.gmane.org/gmane.science.linguistics.wikipedia.technical/57017
Thanks!
Mark.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
mhershberger@wikimedia.org wrote:
Have you filed a bug for this?
I filed one for you now: https://bugzilla.wikimedia.org/32762
Thanks for filing the bug. I hadn't done so mostly because I didn't know about the Bugzilla site. (That's why I joined here.)
- --
Jeff Darlington General Protection Fault http://www.gpf-comics.com/
hallo, after upgrade 1.17.0 to 1.18.0 float doesn't work. http://simpsonspedia.net/index.php?title=Simpsonspedia
<code>
[[Datei:Startseitenbild.png|left|link=Simpsonspedia:Galerie]]„[[The Simpsons]]” bzw. im Deutschen „<strong>Die Simpsons</strong>” ist mehr als nur eine Zeichentrickserie. Die '''Simpsonspedia''' wurde ins Leben gerufen, um Wissenswertes über die Kult-Fernsehsendung der gelbe Familie zusammenzutragen. Sie soll dem suchenden Simpsons-Fan alle möglichen Informationen bereithalten.
Wie auch eine Episode der Simpsons nicht von einer Person erstellt wird, so wächst das Simpsons-Wiki nur durch die Gemeinschaft der Simpsons-Begeisterten. An dieser Stelle geht der Appell an alle Fans der Simpsons, aktiv an dem Projekt mitzuarbeiten, damit sich der Simpsons-Wissensspeicher füllt. Nur zusammen ist es möglich, die Simpsonspedia zu vervollständigen, um so sehr viele Fragen von Fans und Interessierten beantworten zu können. Auf diese Art und Weise sind so bisher '''[[Spezial:Alle_Seiten|{{NUMBEROFARTICLES}} Artikel]]''' entstanden, welche durch '''[[Spezial:Aktive_Benutzer|{{NUMBEROFACTIVEUSERS}} aktive User]]''' betreut werden.
</code>
1.17.0 = image left, text right 1.18.0 = image top, text bottom
what’s going wrong?
best regards s.net
after upgrade 1.17.0 to 1.18.0 float doesn't work. http://simpsonspedia.net/index.php?title=Simpsonspedia
1.17.0 = image left, text right 1.18.0 = image top, text bottom
whats going wrong?
Actually the "float: left;" is missing from the .float-left class in the CSS. You should be able to add it to your monobook CSS.
hth Frank
i think i fixed all float values
but now i see, that the new id "mw-normal-catlinks" also doesn't exist. http://simpsonspedia.net/index.php?title=Stefane_August look at category
f***ing new faulty main.css
-----Ursprüngliche Nachricht----- From: Frank Ralf Sent: Tuesday, November 29, 2011 7:47 PM To: mediawiki-l@lists.wikimedia.org Subject: Re: [Mediawiki-l] Upgrade to 1.18 + float
after upgrade 1.17.0 to 1.18.0 float doesn't work. http://simpsonspedia.net/index.php?title=Simpsonspedia
1.17.0 = image left, text right 1.18.0 = image top, text bottom
what’s going wrong?
Actually the "float: left;" is missing from the .float-left class in the CSS. You should be able to add it to your monobook CSS.
hth Frank
_______________________________________________ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
f***ing new faulty main.css
+1
On 29 November 2011 23:21, Support Simpsonspedia support@simpsonspedia.netwrote:
i think i fixed all float values
but now i see, that the new id "mw-normal-catlinks" also doesn't exist. http://simpsonspedia.net/index.php?title=Stefane_August look at category
f***ing new faulty main.css
-----Ursprüngliche Nachricht----- From: Frank Ralf Sent: Tuesday, November 29, 2011 7:47 PM To: mediawiki-l@lists.wikimedia.org Subject: Re: [Mediawiki-l] Upgrade to 1.18 + float
after upgrade 1.17.0 to 1.18.0 float doesn't work. http://simpsonspedia.net/index.php?title=Simpsonspedia
1.17.0 = image left, text right 1.18.0 = image top, text bottom
what’s going wrong?
Actually the "float: left;" is missing from the .float-left class in the CSS. You should be able to add it to your monobook CSS.
hth Frank
MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
On Tue, Nov 29, 2011 at 4:28 PM, Dave butlerdi butlerdi@gmail.com wrote:
f***ing new faulty main.css
+1
Compare your skins/common/shared.css with what you should have:
http://simpsonspedia.net/skins/common/shared.css
http://svn.wikimedia.org/viewvc/mediawiki/tags/REL1_18_0/phase3/skins/common...
You're missing all kinds of stuff from it. I'd double check to make sure you upgraded properly.
On 29/11/2011 17:31, Daniel Friesen wrote:
On Tue, 29 Nov 2011 08:58:09 -0800, Gordon Jolygordon.joly@pobox.com wrote:
I have Mediawiki installation went from 1.17 through 1.18 RC1 and to 1.18 - no problems.
But another Mediawiki has had some problems going direct from 1.17 to 1.18 - I took out Recaptcha and now see this:
*Fatal error*: Cannot redeclare wfprofilein() (previously declared in /xxxxxxxx/public_html/includes/profiler/Profiler.php:14) in */xxxxx/public_html/includes/ProfilerStub.php* on line *25*
Not sure why...
Gordo
Sounds like you upgraded MediaWiki by extracting 1.18 on top of 1.17 instead of extracting 1.18 to a new directory then moving the config and other stuff to the new directory. And have an old StartProfiler.php.
includes/ProfilerStub.php was moved to includes/profiler/Profiler.php and includes/profiler/ProfilerStub.php in 1.18
Basically what it looks like is happening is that you have a includes/ProfilerStub.php file from 1.17 and includes/profiler/ from 1.18. Because your StartProfiler.php likely uses the old method of a require_once (instead of autoloading as I believe we now do) MediaWiki is loading the 1.18 profiler code from includes/profiler/Profiler.php and then when it require your StartProfiler.php that old require_once is requiring the old 1.17 code from includes/ProfilerStub.php causing a fatal error as the old code tries to redefine the same method.
If you don't need the profiler I recommend you delete your StartProfiler.php. If you do you should probably delete the require_once line. You'd also probably be better off clearing out all the outdated files of 1.17 code that were left behind since you extracted 1.18 over top of 1.17. Though the easiest way to do that is to just re-untar 1.18 in another directory, and move your actual LocalSettings, extensions, images/, etc... to there.
Yes, exactly. I could do that. But I follow the instructions below........
Trick - remove *Profile*.php in includes and the top level file....
rm StartProfiler.php rm ./includes/*Profile*.php <<<
I extract the tar files over the old version (in fact I extract them and make some minor changes and create a new tar). It is the method given on the Mediawiki.org webiste:
****
http://www.mediawiki.org/wiki/Manual:Upgrading
Using a tarball package If you are using a tarball package http://www.mediawiki.org/wiki/Download, decompress the file on the server where the old version of mediawiki is running. You may need to run the command as sudo if you don't have full write permissions to the wiki install directories under your current user. When untarring a tarball package normally a new directory for the new wiki version will be created and you will have to copy the new files and directories to your current wiki directory. Instead, to replace the existing files while decompressing and do this in one step, use this command: $ tar xvzf mediawiki-1.18.0.tar.gz -C /path/to/your/wiki/ --strip-components=1
****
YMMV,
Gordo
Gordon Joly gordon.joly@pobox.com writes:
*Fatal error*: Cannot redeclare wfprofilein() (previously declared in /xxxxxxxx/public_html/includes/profiler/Profiler.php:14) in */xxxxx/public_html/includes/ProfilerStub.php* on line *25*
I filed a bug (https://bugzilla.wikimedia.org/32760) and CC'd you and Jeff Darlington on it. We'll cover it in the triage tomorrow (see http://thread.gmane.org/gmane.science.linguistics.wikipedia.technical/57017).
Please join us.
Mark.
Gordon Joly <gordon.joly <at> pobox.com> writes:
I have Mediawiki installation went from 1.17 through 1.18 RC1 and to 1.18 - no problems.
But another Mediawiki has had some problems going direct from 1.17 to 1.18 - I took out Recaptcha and now see this:
*Fatal error*: Cannot redeclare wfprofilein() (previously declared in /xxxxxxxx/public_html/includes/profiler/Profiler.php:14) in */xxxxx/public_html/includes/ProfilerStub.php* on line *25*
Not sure why...
Gordo
This a feature of the standard upgrade process, as recommended by the maintainers. That is to unpack a tar image over the working directory.
But since some code has moved, older versions of the code remain and are executed. It appears that this is the "profiler" code, which has moved into /includes/profiler/ from /includes/
Deleting the old versions, and the file StartProfiler.php at the top level fixes this.
Other files in /includes/ in 1.17 (which have to be deleted) are
Profiler.php ProfilerSimpleText.php ProfilerSimpleUDP.php ProtectionForm.php UserRightsProxy.php ProfilerSimple.php ProfilerSimpleTrace.php ProfilerStub.php ProxyTools.php
Gordo
mediawiki-l@lists.wikimedia.org