Personal tools

Transformers Wiki talk:Community Portal/Arriving2

From Transformers Wiki

Jump to: navigation, search

Contents

Many Happy Returns

Heeeeey, this is pretty good. --RosicrucianTalk 17:15, 26 May 2009 (EDT)

It's speedier than the old server, but there's still some wonkiness. For instance, every time I tried editing just this section I got a blank page, but editing the whole page seems to have worked. Also, I keep getting logged out. --Jeysie 18:00, 26 May 2009 (EDT)
I can't even log in. What's going on? -- SFH (cannot log in) 18:01, 26 May 2009 (EDT)
I'm thinking there may be some wonkiness related to cookies made before, or even during the transition. I did get some "session data lost" messages, but after a log out and a log back in, that seems to be resolved.--RosicrucianTalk 18:06, 26 May 2009 (EDT)
So what exactly do I have to do to be able to log in? -- SFH (desperately trying to log in) 18:19, 26 May 2009 (EDT)
You could try clearing your cache and deleting your cookies and see if that helps. Other than that, I'm not sure what to suggest. --Jeysie 18:23, 26 May 2009 (EDT)--Jeysie 18:23, 26 May 2009 (EDT)
What are you getting when you try to log in? A blank page? An error message? --abates 18:32, 26 May 2009 (EDT)
"Internet Explorer cannot display the webpage". Does that help? -- SFH (unable to log in) 19:00, 26 May 2009 (EDT)
Welp, I'm on firefox, and I'm logged in, and I'm only editing this section and it's displaying right, so... I'm happy! /:) - Chris McFeely 19:08, 26 May 2009 (EDT)
Well, I tried Firefox, and it's working, but still not on Internet explorer. -- SFH 19:19, 26 May 2009 (EDT)
Tried here with IE6. No problems logging in, but when I attempted to log out, I got a "Cannot find server or DNS Error" error. The second logout attempt worked, but then when I went to log in again, I got the same error.
Deleting the tfwiki cookie fixed the problem and I was able to log in. In fact now I'm not having any problem at all logging in and out on IE6. The sidebar on the login pages appears messed up in IE though (tis cutting off in the middle of the navigation menu). --abates 19:39, 26 May 2009 (EDT)
What is this "Internet Explorer" you speak of? Is it a 3rd party browser? -Derik 19:37, 26 May 2009 (EDT)
I'm getting a lot of "The requested URL could not be retrieved" messages, and the occasional blank page or "loss of session data", myself. - Magnus Maximus 19:47, 26 May 2009 (EDT)
I occasionally get the message: Sorry! We could not process your edit due to a loss of session data. Please try again. If it still doesn't work, try logging out and logging back in. - Starfield 20:13, 26 May 2009 (EDT)
So do I. And I did delete my tfwiki cookie, but I still get internet explorer cannot display the webpage. This is getting rediculous. -- SFH 20:18, 26 May 2009 (EDT)
I have problems logging in, logging out and displaying the lefthand navigation and the user controls on top for the Recent Changes page: [1] --Detour 20:36, 26 May 2009 (EDT)
That happens on other pages too, as it turns out. Like the new Nexus Maximus image, or Cryotek (TransTech). --Detour 20:41, 26 May 2009 (EDT)

Trying to search for (not "Go" to) splinter or terms containing it such as splinter timeline gives a white screen of death. Also had trouble saving this post due to "a loss of session data". Trying hitting "Show preview" before "Save page" to see if that works... [And shouldn't this be @ Transformers Wiki talk:Community Portal/Arriving2? - SanityOrMadness

Ask and ye shall etc. etc.--RosicrucianTalk 21:36, 26 May 2009 (EDT)
Searching for "splinter" works for me! --abates 21:42, 26 May 2009 (EDT)
Still not working for me, and no number of Shift-F5 or Ctrl-F5 forced refreshes is making it so. - SanityOrMadness 21:47, 26 May 2009 (EDT)

So, I'm getting no top or side bars (including the discussion/edit/history part up top), and there's incomplete wikicode showing up at the bottom of this specific page. --Detour 21:50, 26 May 2009 (EDT)

Yeah, I'm getting that too - that means the page isn't fully loading, since they're at the bottom of the HTML. I can't get Unicron to fully load even the text for love nor money, and Optimus Prime (G1) is even worse. And I'm getting those "loss of session data" messages about a fifth of the time, meaning I have to (re-)preview or show changes, then save. - SanityOrMadness 22:34, 26 May 2009 (EDT)
Unicron works for me, but not Optimus. I'm wondering if these problems are caused not by MediaWiki, but by Squid, which we're using for caching. --abates 00:05, 27 May 2009 (EDT)
It definitely IS problems with Squid, not MediaWiki itself; right now I'm really uncertain as to what's causing them. Unfortunately I can't just disable Squid, since the wiki buckles massively under the pressure without it. I'm trying to look into it, it's baffling, because the issues are seemingly at random. --Suki Brits 00:34, 27 May 2009 (EDT)
This, while old, may be relevant as it seems to be about blank pages getting stuck in the Squid cache and a workaround. --abates 03:41, 27 May 2009 (EDT)
Oh my god, I love you, that does seem to fix the problem. Thank you so much! Apparently I spoke too soon. I guess this will need more work. --Suki Brits 04:17, 27 May 2009 (EDT)
I was just able to log in on Internet Explorer just now. -- SFH 21:41, 27 May 2009 (EDT)
Which version of IE are you using? --abates 21:58, 27 May 2009 (EDT)
IE7. -- SFH 22:06, 27 May 2009 (EDT)

So, many bugs stemmed from crappy session handling. To fix it, I went from a memory-based (fast) handler that apparently didn't work right, to a file-based (slow) one that does. To fix the minor performance dip from THAT, I've installed and enabled Memcached, which basically stores common and unchanging DB queries in RAM under a key. (Basically, I've decided to Insert Magic Here.) Between Squid and Memcached, we're basically running Wikipedia In A Box. Since said box is on a virtual server, we're actually running Wikipedia In A Box In A Box. This is now the Matryoshka Doll of wikis.

(Now, if anyone has any questions as to *why* we went with a VPS, keep in mind that we've done two RAM upgrades already by clicking a button and waiting for the reboot to finish, and our provider is NOT overselling.)--McFly 17:43, 4 June 2009 (EDT)

So the server should be ironclad now, and is also within our budget?--RosicrucianTalk 18:21, 4 June 2009 (EDT)
I thought you said you work for an ISP? Nothing's ironclad. I've got rolling daily/weekly snapshots (WHICH HAVE BEEN TESTED,) and that's that. You want ironclad, start paying me, and triple the budget. For now, it's good, it's protected (though not as well as we'd all like,) and the next few days will tell us if it's stable. Any more than that will require a massive leap in ad revenues. --McFly 18:30, 4 June 2009 (EDT)
Fair enough. The backups take a load off my mind, and really I'm hearing a lot of encouraging stuff out of you so far. I mean yeah, I'll admit that nothing is absolutely ironclad, but in relative terms what you're saying seems to be that we have taken the model of someone far bigger than us (Wikipedia) and made it work for us. If we can do that within the bounds of our hardware and budget, that's fantastic. However if you say it's not time to exhale just yet I'll take you at your word. You've been far more open with us than our prior experiences, so I'm just trying to feel it out.--RosicrucianTalk 18:36, 4 June 2009 (EDT)
Much appreciated. I'm not trying to scare anyone, or tell them to hold their breath. I just want to make sure that no one expects perfection from a volunteer effort. Best effort, sure. If the ad revenues go up, and we need to spend the money on upgrades? We'll scale up. For now, I'll settle for the Best Damned Server We Can Get With Our Ad Money. (Step two involves yet another server move that I've been eyeing, but we'd end up forklifting the entire system image at that point. Can you say Cloud Hosting?) --McFly 19:00, 4 June 2009 (EDT)
Hi, I'd like to thank you for all your help, especially since you are doing this on your own time. The site seems to be much more stable now. --FFN 18:55, 4 June 2009 (EDT)
So far so good! Someone should post a positive update on the status blog. - Starfield 20:14, 4 June 2009 (EDT)

Bugs still remaining

I've been doing a lot of behind the scenes work for the past few days. For all the currently remaining bugs logged here, could I have confirmation for every one that's still outstanding, that it hasn't been fixed? Obviously the long pages are still causing issues, but for the others, I need to know if there really is still a major problem, and if so, how I can replicate it. --Suki Brits 16:59, 1 June 2009 (EDT)

Well, I get a lot of blank pages, including the login page. The weird part, though, is that when I access the wiki through the web proxy anonymouse.org (like I am right now), the wiki works just fine. No blank pages, no long pages not loading fully, just a wiki that works. Can't log in or use anything involving CAPTCHA, though, but that's because of the use of the proxy, not any of the wiki's problems. --193.200.150.152 17:17, 1 June 2009 (EDT) (Detour)
There's still a problem with the "loss of session data" message, although not as frequent as it was at its' peak, and an edit to Jazz (G1)/toys still gave me the old page until I Ctrl-F5ed it. The problem with replicating the errors is that most of them are transient and intermittent- they can happen on almost any page, and may or may not happen on any given load, with no obvious reason why it happens one time vs. another. - SanityOrMadness 17:33, 1 June 2009 (EDT)
Paradron Medic is an example of a page which is currently coming up completely blank for me (on two different computers on different connections). If I log out, it works fine, log back in again, it's blank. Also still getting the "loss of session data" message when trying to save edits like right now. --abates 17:33, 1 June 2009 (EDT)
I can see both that page and its' edit page while logged in. And got MANY "loss of session data" errors while trying to make this post. So much for "not as frequent"... - SanityOrMadness 17:39, 1 June 2009 (EDT)
Soundwave (Shattered Glass) is now coming up blank for me as well. I have more information this time! The first time I loaded the page, the left-hand column was cut off before the goicon with the error message "Fatal error: Call to a member function children() on a non-object in /var/lib/mediawiki/skins/MonacoBook.php on line 165". When I hit reload, I got a completely blank page which no amount of reloading seems to change. --abates 19:59, 1 June 2009 (EDT)


Internet Explorer 7 is still not working so far as being able to log in to the site goes. I'll add some more information under the bug report re some testing I've just done. --abates 01:47, 2 June 2009 (EDT)

We seem to be making little headway here. :( I noticed mentions while googling that a while back Wikia switched their caching software from Squid to Varnish (there's a relevant configuration file here) and wondered if it might be worth a try here. --abates 09:13, 2 June 2009 (EDT)


Does "the site was just down for two solid hours" count as a "bug", I wonder... - SanityOrMadness 15:47, 2 June 2009 (EDT)

Not just that 2 hours, but it's been on and off for an hour or more at intervals over the past 10 hours. --FFN 16:42, 2 June 2009 (EDT)
And three more hours in a row after you posted that... - SanityOrMadness 20:10, 2 June 2009 (EDT)
I got sick and tired of waiting so I logged off. I've been able to make an hour's worth of editing work in 12 hours. That is not acceptable. --FFN 06:31, 3 June 2009 (EDT)
So are these outages going to be a fact of life on the TF Wiki? Because I still have people from various timezones telling me that the site is down at all manner of hours of the day. Meanwhile, the TF Wikia is pretty much always reliably online. --FFN 12:56, 4 June 2009 (EDT)
McFly and Suki are working on it. As McFly stated, they need specifics. Times. Error messages if applicable. I know you're frustrated, but that's what will help the most here.--RosicrucianTalk 13:48, 4 June 2009 (EDT)
C'mon, everyone knows posting nothing but "fuckity fuck fuck fuck fuck and fuck!" whenever a problem shows up is TOTALLY USEFUL and you should do it OVER AND OVER to the exclusion of EVERYTHING ELSE. --ItsWalky 15:13, 4 June 2009 (EDT)
What can I say? The site doesn't load 70% of the time I attempt to visit the wiki. Most of the time it doesn't say anything, or I get tired of waiting for an error message to eventually pop up. Sometimes it says there's some sort of database error or the server cannot be found.
As for logging time and date, my pedantry only goes so far. That, and when I find the site is down, I usually find something else to do, so I tend to forget about this place for a few hours, and thus forget exactly what time I found that things stopped working. Hmm, I just got a loss of session data and a blank white screen as I was saving this edit. --FFN 15:56, 4 June 2009 (EDT)

PLEASE RECHECK ALL BUGS ASAP. I have fixed a session handling problem (at the expense of performance) which was causing errors from the search box, adding an error on the RAW output/XML exports, AND has apparently fixed the G1 Prime page for me WHEN LOGGED IN. --McFly 16:30, 4 June 2009 (EDT)

"At the expense of performance" in what sense?--RosicrucianTalk 16:33, 4 June 2009 (EDT)
I changed out the PHP session handler to a slower, more stable counterpart. Why this improved things that only manifested themselves while both logged in *and* using Squid instead of bypassing the Squid cache, I'll never know. I suspect that it's a side-effect of load delays and MediaWiki not properly registering session status (and as such, not telling Squid to back the hell off.) Suffice it to say, I out-technobabbled the server. --McFly 16:47, 4 June 2009 (EDT)
Ah okay, cool. Yeah, I'll take stability over slightly slower rendering. It doesn't seem to be too heinous of a performance hit so far, and I'm at work for an ISP so believe me I'd notice.--RosicrucianTalk 16:50, 4 June 2009 (EDT)
Well, hold onto your hats, kids. I'm going to drop in one more quick optimization. Sessions may drop due to the necessary apache restart. --McFly 17:36, 4 June 2009 (EDT)
Sweet Holy Jebus, it actually worked. DB query delays should be minimized at this point.--McFly 17:50, 4 June 2009 (EDT)
I just successfully logged in and wrote this in IE6 with no problems at all. --abates 16:43, 4 June 2009 (EDT)
Same here! Good job, McFly! --Detour 17:01, 4 June 2009 (EDT)
I don't use IE, but I hope this solves problems for IE users and whatever else related. Thanks! --FFN 17:11, 4 June 2009 (EDT)


The site just crashed for me, and I got this:

ERROR The requested URL could not be retrieved

The following error was encountered:

   * Unable to forward this request at this time. 

This request could not be forwarded to the origin server or to any parent caches. The most likely cause for this error is that:

   * The cache administrator does not allow this cache to make direct connections to origin servers, and
   * All configured parent caches are currently unreachable. 

Your cache administrator is webmaster. Generated Fri, 19 Jun 2009 19:55:26 GMT by 174-143-26-81.slicehost.net (squid/2.7.STABLE3)

I've seen this sort of message occasionally pop up, though usually back before McFly fixed our problems. Hope it's not a bad sign. --FFN 16:33, 19 June 2009 (EDT)

Bug reports

Database error when saving article

Bug Name Database error when saving article
Reported-by abates Date May 29, 2009 Status open
Description I don't know how widespread this problem is, as I've only gotten it while editing User_talk:Magnus_Maximus. When saving the page, I get:
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 "EmailNotification::actuallyNotifyOnPageChange". MySQL returned error "2006: MySQL server has gone away (localhost)".

After a couple of attempts, I was able to save the edit. Haven't had any problems with any other pages - could be because the page has a watch or something set on it?

Resolution
I've encountered this issue quite often myself. I am increasingly turned off from editing this site. --FFN 06:18, 2 June 2009 (EDT)
This should be the last remaining bug. Pretty much everything else goes back to a misconfigured session handler, which is why the problems largely manifested themselves when logging in. I *think* we've fixed it, but you'll have to set a watch on a page and edit it to make sure. IF you don't see the error again, AND you get a notification email from your test, then we can close EVERY. LAST. BUG. --McFly 01:28, 6 June 2009 (EDT)

Can't edit some pages when logged in

Bug Name Can't edit some pages when logged in
Reported-by Derik Date May 27, 2009 Status open
Description Some pages (or even sections of pages) will always come up as white screens when I attempt to edit them-- but if I log out, they are editable.
  • This does not appear browser of cookie-cache thing... the behavior repeats in Firefox, Safari, Opera and Chrome. (Did not bother testing IE.)
  • Are other users able to edit these pages when logged in/out (use the Franklin-section link above to check.) Are the same pages whitescreening for all users experiencing this problem?

Current Workaround: Log out as needed. (Not ideal, may create problems for semi-protected pages.)
More elaborate workaround: use the "revert" feature on the history page, this gets you into edit mode while bypassing the white-page. (Credit to Rosicrucian.)

Resolution
I haven't explored any of these extensively, but I can give my experience of the past few hours, at least. All examples are from when I've been logged in on Firefox. Apologies in advance if this isn't the proper format for responding. Please feel free to rework as necessary.
My attempt to review just the difference made by Derik's last edit to the Community record page generated a white screen. To see the actual change he made, I had to link directly to the article, then its history page, then the "last" link for his edit.--Apcog 06:25, 27 May 2009 (EDT)
I can no longer duplicate this. Has it been fixed? Also Optimus Prime (G1) is now loading fully every time... --abates 21:24, 27 May 2009 (EDT)
I believe I've fixed it. I need to know if anyone can replicate the issue or not. --Suki Brits 22:37, 27 May 2009 (EDT)
This just cropped up again when I tried to edit some images. :( --abates 03:10, 28 May 2009 (EDT)
Which images? I need to know what I'm testing with. --Suki Brits 03:13, 28 May 2009 (EDT)
Image:Moonracer vehicle.jpg and Image:Moonracerg1.jpg are both currently giving me a blank page when I hit edit. --abates 04:29, 28 May 2009 (EDT)
I'm currently having this problem editing talk pages -- User:Tupka8682.72.66.241 06:04, 28 May 2009 (EDT)
I ran into this again today, after not seeing it for a few days over Botcon. Has anyone else been running into it? (Has it always been here, or is it just appearing again?)
Obnoxiously, the page in question is now editable for me, but it wasn't 30 minutes ago. -Derik 12:08, 1 June 2009 (EDT)

The sneakiest way I've found around this one is to do a revert, and while doing so paste all the text you're "reverting" back in so that you're not really reverting, then make your edits. It seems to work.--RosicrucianTalk 12:10, 1 June 2009 (EDT)

That's even weirder... so there's nothing fundamentally wrong with the edit function, even for that user of that page... just the edit mode for this user, for this page? -Derik 12:19, 1 June 2009 (EDT)
Like nearly everything we've had lately, it's caching. Squid treats the two of them as requests for different pages, because they're generated by (marginally) different URLs.--RosicrucianTalk 13:59, 1 June 2009 (EDT)
...why are calls to the "edit" page being cached?
There are some dynamic pages where I guess you COULD sorta justify caching them... mode=edit is not one of them. -Derik 17:02, 1 June 2009 (EDT)
There's a special "Cache-Control" header which MediaWiki is sending and Squid should be honouring to avoid such pages being cached. --abates 18:28, 1 June 2009 (EDT)
Actually, Squid will pass-through anything with a question-mark in the URL at this point. Since any action (edit, purge, etc.,) does so, any "action" should bypass Squid entirely, with minimal header-futzing. --64.206.123.1 11:50, 4 June 2009 (EDT)
I got a whitepage on Dropshot (Universe) earlier today. Not editing the page... just trying to view it. I had to log out to view the page. -Derik 16:54, 2 June 2009 (EDT)

Persistent "loss of session data" error when saving edits.

Bug Name Persistent "loss of session data" error when saving edits.
Reported-by Derik Date May 27, 2009 Status open
Description Normally if you try to save a page and your session has "Done Something Funky" since you began editing it, Mediawiki gives you a preview instead an an edit, and prompts you to re-save again, whereupon the problem has repaired itself.

Now it simply gives you Session Error after Session Error-- the page remains impossible to save. Workaround: Copy the text of your edit, go back to the page and click 'edit' again. You will now be able to save. (This error seems to hinge on the 'time you began editing' timestamp not re-setting itself if there was a problem.)

Resolution (Low priority)
I had a problem like that a few hours ago with editing the Ruckus (Shattered Glass) page. I was able to open and edit the page, but once I was done and clicked "save", it returned a blank white page, ignoring several attempts to refresh. When I checked the Recent Changes list, though, I saw my edit listed, so I didn't bother to mess with it further.--Apcog 06:25, 27 May 2009 (EDT)
Whitepage with the edit going through would be a slightly different sort of error. -Derik 10:08, 27 May 2009 (EDT)
Actually, the easiest workaround for this is to hit "Show preview" or "Show changes", THEN save. - SanityOrMadness 10:02, 27 May 2009 (EDT)

This is getting worse. When I was reverting Derik's dicking around there, it was taking five or six attempts to get the page to actually save. (May take the same here. 2...) - SanityOrMadness 22:29, 27 May 2009 (EDT)

Same here. I keep getting loss of session data errors even when I click "show preview" and then "save page". --FFN 03:00, 28 May 2009 (EDT)
It happens to me now when using FireFox. --TX55TALK 11:34, 28 May 2009 (EDT)
I am getting very angry about this. I can hardly ever save any edit without a session error coming up. --FFN 06:20, 2 June 2009 (EDT)

Some pages not loading fully

Bug Name Some pages not loading fully
Reported-by abates Date May 27, 2009 Status open
Description Large pages (Optimus Prime (G1), Unicron) may not load fully, losing the bottom part of the page and the website kibble. The location of the cut-out point varies if the page is reloading, suggesting that Squid isn't caching the partial page and is possibly timing out when trying to retrieve the article.
Resolution
Definitely getting this problem. Repeated refreshes of Optimus Prime (G1)'s page got the browser to cycle through several different cut-off versions of the page, some more complete than others, but none past about halfway through the IDW Comics Continuity section.--Apcog 06:25, 27 May 2009 (EDT)
This does not seem to represent a hard limit-- running action=purge on the OP page kept giving me slightly different 'lengths.'
Is this caused by the condom on our clownfish? -Derik 10:08, 27 May 2009 (EDT)
I have trouble loading the full 500 changes on the Recent Changes page. Takes several reloads for the entire page to load. --FFN 05:51, 28 May 2009 (EDT)
This is getting intolerable. Now when I click "edit" at the top pages, half of the time I get a blank white screen. This is especially annoying when I want to edit several sections in an article at once, or I want to edit the top section of an article. --FFN 10:35, 31 May 2009 (EDT)
I'm with you. I far too often either get blank screens or incomplete page loads. --Detour 11:17, 31 May 2009 (EDT)
I'm also getting all of these problems a LOT. (using Firefox, FWIW.) -- Repowers 02:17, 2 June 2009 (EDT)
This is completely unacceptable. Not only are our friends Database Error and Server Not Bloody Working coming to visit, we can't even load the pages properly when the server is working. What the hell? What in the fucking hell? --FFN 06:16, 2 June 2009 (EDT)

Problems logging in/browsing while logged in with IE7

Bug Name Problems logging in/browsing while logged in with IE7
Reported-by abates Date May 27, 2009 Status open
Description In Internet Explorer 7, when loading the login page/after logging in/browsing while logged in, pages would load and display then abruptly switch to a screen saying "Internet Explorer cannot display the webpage". Problem appears to be related to Google analytics, as the one time this didn't happen was when a page didn't load fully and was broken off partway through the Google Analytics code. Problem does not seem to occur while logged out however. Purged cache and cookie files, but problem recurred after logging in.

Current workaround: Use an alternate browser,

Resolution
Looks like this is now fixed. I'm not having any problems with the site in IE7 (other than the layout problems which were there before!) --abates 01:50, 28 May 2009 (EDT)
Not fixed for me. I can look at any page on the Wiki...so long as I don't try to log in. Then I get the above error and NONE of the pages will load until I exit out and then re-enter the Wiki. (Xaaron) --70.185.107.140 10:40, 31 May 2009 (EDT)

More interesting facts about this bug!

  • The problem (trying to load a page in IE7 and getting a "Internet Explorer cannot display the webpage" error) does not start occurring until you do one of the following:
  • Once you trigger the problem by doing one of those, some pages will load, a few will partially load but stop halfway through the HTML, and many will give the error. Pages in the Special: namespace seem to particularly reliably give the error.
  • If you exit out of IE7 and restart it, the problem goes away (until you do one of the triggers above).
  • Meanwhile, in IE6, the login page refuses to load fully (as does the logout page). This may well be related to the IE7 problem.

So, something to do with the sessions, but I know not what. Equally, why no other browser has any problem with this is a mystery. --abates 02:24, 2 June 2009 (EDT)

In IE6, the above all applies, however instead of getting the "cannot display" error, you get a page which is cut off right after the title. And sometimes it gets into an infinite loop of reloading the page by itself, as though it's infinitely redirecting to the page it's already on. --abates 21:25, 2 June 2009 (EDT)
For the IE6 problem, I don't want to get *too* smug, but it's a dead browser, it's chock full of bugs, and even Microsoft is trying their hardest to go back in time and kill it with a shovel. As for IE7, well, here's the real fun part: Try reloading the login page, and then hit the Back button. Somehow, THAT magically gets us back to the proper page, and you *do* see it flicker before dumping to error. Something must be breaking the rendering on IE7, and Browser Holy Wars aside, that IS a showstopping bug. My money's on the Squid cache, so that's where I'm going to start looking. --McFly 10:32, 4 June 2009 (EDT)
What bugs? Before the Wiki moved, I never had any problems with any website using IE6. --193.200.150.82Detour
Too many for me to list, they're Microsoft's problem, not ours. I'm not trying to say that the bugs have always affected this wiki on any server (they didn't,) just that IE6 bugs are at the bottom of the barrel compared to a) Global bugs like partial page loads (and that's a frakking doozy,) b) Bugs in current browsers. Since IE8 is out, focusing on anything specific to IE6 is like focusing on a glitch native to Windows 2000. We've got bigger fires to put out. (Though, for the record, IE6 doesn't support PNG alpha channels properly, and developers are constantly putting in workarounds to IE6's fundamentally broken/outdated CSS handling. I don't care if you run IE/Firefox/Opera/Chrome/Safari, just so long as it's relatively up-to-date. --McFly 12:26, 4 June 2009 (EDT)
Well, you tell me if there's any way to get the navigation buttons and address bar to be arranged practically like they are on IE6 and I'll give consideration to IE7, otherwise I'm sticking to the interface I know works best. --193.200.150.152 12:52, 4 June 2009 (EDT) Detour
I'm of the belief that the IE6 problems have the same cause as the IE7 problems, and that fixing one will fix both. As a piece of additional information someone noted on AllSpark, the problems apparently don't occur on IE8, even when you put it in IE7 compatibility mode. --abates 16:39, 4 June 2009 (EDT)
Can verify that I can log in and edit using IE6, as evidenced by this post.--RosicrucianTalk 17:03, 4 June 2009 (EDT)

Database Error

Bug Name Database Error
Reported-by SanityOrMadness Date May 27, 2009 Status open
Description Some pages are randomly showing as "Database Error"s rather than the pages (with full Wiki skin, plus the page categories. This shows as:
Database error [as page header, in place of the title]

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 "MediaWikiBagOStuff::_doinsert". MySQL returned error "1213: Deadlock found when trying to get lock; try restarting transaction (localhost)".
This appears to resolve itself for that specific page within a few minutes, but then recurs elsewhere.

Current workaround: Wait a few minutes, then refresh the page

Resolution
Most of the google results for this seem to be for MediaWiki version 1.13.0. I haven't found any talking about it with 1.12.0 which offered a resolution, other than the suggestion of turning on memcached. --abates 16:40, 27 May 2009 (EDT)
I'm getting these fucking errors every time I try to make a large edit. What the hell does this server want? --FFN 06:15, 2 June 2009 (EDT)
Please reserve additions to bug reports to actual information, and not swear-laden complaints. This bug doesn't really require any browser/OS info, but *dates and times* are incredibly helpful. --McFly 10:35, 4 June 2009 (EDT)

Pages not changing after save

Bug Name Pages not changing after save
Reported-by SanityOrMadness Date May 27, 2009 Status open
Description I've had several cases now where a page has saved after an edit, but I get the original/unmodified page back on the post-save load. I have to force-reload it to see the edited page

Current workaround: Shift-F5/Ctrl-F5 the page

Resolution
That sounds like a problem with the new caching module to me. -Derik 17:27, 27 May 2009 (EDT)


Top and side areas don't show up on the Recent Changes page, as well as some others.

Bug Name Top and side areas don't show up on the Recent Changes page, as well as some others.
Reported-by Detour Date May 28, 2009 Status open
Description I haven't tested this on other browsers, but on IE6 when I go to the Recent Changes page neither the side bar with the GoBox and the Search or the top bar with the user ops and the "Special page" header load. Here's how it looks. It was actually working from... around the end of the afternoon/start of the evening. Stopped working again some time past midnight (the same as other recurring problems such as blank pages). On occasion it doesn't show up on other pages, which means I can't use the Edit and Discussion tabs on there.
Resolution
Gah! Looks like the IE7 problem and the Optimus Prime (G1) problem have come back as well! WTF?! --abates 04:27, 28 May 2009 (EDT)
Sometimes also happens on Safari. User:Tupka8682.72.66.241 06:04, 28 May 2009 (EDT)
This is definitely caused by the page not loading entirely. It cuts off while loading the article/recent changes list, and doesn't even get to the side and top bars. --Detour 17:50, 28 May 2009 (EDT)


Resolved issues

Faction icons invisible for me

Bug Name Faction icons invisible for me
Reported-by Starfield Date May 27, 2009 Status fixed
Description Self explanatory
Resolution FIXED
The template is actually rendering correctly, the problem appears to be on the javascript-end. Either the code didn't get ported, or was deactivated while Scout was testing stuff or one of the MW Javascript-functions it depends on changed slightly witht he MegiaWiki version upgrade, and the code now needs tweaking.
Other Javascript (like the search-suggest) is working. And... KiredTools is not?
Did the name of the default skin change when we moved servers? Or maybe it's the post-body error output that's screwing up KiredTools loading... -Derik 01:28, 28 May 2009 (EDT)
I very distinctly remember that they were working before. I'll put good money on it being the latter. --Suki Brits 02:54, 28 May 2009 (EDT)
There. --Suki Brits 03:12, 28 May 2009 (EDT)
Awesome. That fixes the other Javascript problems I was having too, they're all running now! -10:04, 28 May 2009 (EDT)


Error messages in search-suggest

Bug Name Error messages in search-suggest
Reported-by Derik Date May 27, 2009 Status open
Description When typing in the search box, the following error message appears below the suggestions: Fatal error: Unknown: Cannot find save handler mm in Unknown on line 0
Resolution Resolved: see below.

"Line 0" error in action=raw output

Bug Name "Line 0" error in action=raw output
Reported-by Derik Date May 27, 2009 Status open
Description When viewing a page's content in RAW mode, the error

Fatal error: Unknown: Cannot find save handler mm in Unknown on line 0 is appended.
Example: Content of Image_talk:Animated_carerra.jpg in raw mode, and in normal editmode.
(The text of the error is suggestive of caching, which makes me think this might be important.)

Resolution Fixed. Overarching PHP session handler misconfiguration.
Egads, a google suggests that's a PHP problem [2] [3] [4] Also I presume this is what's causing the error on the search suggestions, so the two bugs are essentially one. --abates 19:13, 27 May 2009 (EDT)
Actually, Derik, that's there on all pages, not just action=raw mode - look at the very bottom left of any page (you may have to highlight to see it, since it comes out as black text). - SanityOrMadness 19:28, 27 May 2009 (EDT)
It appears at the bottom of the stylesheet/javascript files as well, which I'm sure isn't helping things. --abates 20:56, 27 May 2009 (EDT)
Fixed ~May 28th. -Derik 11:58, 1 June 2009 (EDT)
This does actually still occur in a few places (e.g. if you use Special:Export, the resulting xml file has the error at the bottom) but I haven't seen anywhere where it causes a major problem. --abates 17:28, 1 June 2009 (EDT)
Nope, this is dead dead dead dead DEAD.--McFly 18:18, 4 June 2009 (EDT)

ISBN 13's not rendering as links

Bug Name ISBN 13's broken
Reported-by User:Derik Date June 21, 2009 Status fixed
Description 10-digit ISBN's are renering as links, bit 13-digit ISBN's are not... and I'm fairly sure they used to. Example link for non-rendering ISBN 13
Resolution FIXED See below

The ISBN 13 was incorrect. You had it as 9720756651725; the correct form is 978-0756651725. --Lonegamer78 20:20, 21 June 2009 (EDT)

...that's retarded. It breaks if you leave the dashes in... except the first one, which is required?
Retarded I say! -Derik 20:34, 21 June 2009 (EDT)
Technically it still works, with or without the dash (some book stores' search engines don't like the dash). It's because you had it as "972" on the prefix; ISBN-13 prefixes uses "978" and "979". --Lonegamer78 21:01, 21 June 2009 (EDT)
Advertisement
TFsource.com - Your Source for Everything Transformers!